mikejones Hi Mike,
Great to hear from you again 😀
Here's my thoughts below
mikejones Should I risk it? I am worried about. my Google SEO….
Provided this is handled correctly with SEO friendly redirects (302), then this shouldn't be an issue
mikejones With NGINX can I keep both seekAdventure.net and TenDigitGrid for a bit and just easily map every SeekAdventure.net page to redirect to TenDigitGrid without having to specify each page individually?
Yes, although you should consider using something like Virtualmin as an administration / panel, as virtually all of what you will need is built into a GUI which is very reliable, well supported, and easy to use
mikejones An AWS EC2 things that could make this easier?
This will be infrastructure independent, so where it is based makes no difference - this mostly depends on your audience. My recommendation would be to spin up another instance (which I'll help you build under the new domain), so we would create a replica vanilla server, install Virtualmin with NGINX, and then use that as the base. You'll quickly realise the benefits of doing so.
mikejones HTTPS Certificate through letsencrypt would probably have to be updated…
Again, very easily handled by Virtualmin as support for Let's Encrypt is built in
Only for permissions to access files etc.
mikejones Google Workspace Email addresses change…
Easily done. You'd keep seekadenture.net for legacy purposes, and create a new space for the new domain. Mail can also be handled by Virtualmin using Postfix
To start with, 302 is better as it's SEO friendly. Are you using GA ? If this is the case, we can "move" the seekadventure.net domain into the new one at GA level, which requires a redirect to be in place before it'll work. This then over a couple of weeks (depending on size) seamlessly migrates all of your search entries to the new domain using a 302 redirect. It's nice and clean, and will automatically "rewrite" in Google.
mikejones Do I have to specify each re-direct individually or is there a redirect * that would just change the root domain?
We'll apply it at root. The idea is that the new server will also house the seekadventure.net domain, and we'll create a wildcard redirect there meaning you get to manage everything in one place
mikejones Any steps or anything that I may be missing? Any thoughts on if this is a good or bad idea? Right now if SEO does bounce back after the 301 redirects the only real loss would be my facebook page followers. I need to check if I can change the name or if I have to create a whole new page.
No. You've already got a good idea of what you need to do, but my suggestions will enhance the experience and make it seamless. The only "issue" as such is having to pay for two instances in the short term whilst the migration is completed. We have the luxury of the new server meaning the infrastructure can be made ready before we execute. No need to create a new page - just use the old one, and explain the branding change. Create a new one to ensure you have the name (Twitter, LinkedIn, Instagram, Facebook etc)
Both metabullet.com and phenomlab.com use Virtualmin as the back-end management platform, and it's a product I am very well versed in having used it for years. It's extremely powerful and after using it for a week, you'll wonder how the hell you managed without it.