Quick summary
A hosting note about staging a custom-domain cutover, documenting the DNS records, and preserving the old hostname for redirects once ownership changes were ready.
The problem
A deployed static site needed to move to a new primary domain without losing traffic or breaking the still-active domain before the required DNS records were available.
What I checked
- Current hosting and custom-domain configuration
- DNS records required for verification
- Existing-domain preservation and redirect path
- Header and footer social-profile links
- Staging deployment after the supporting site changes
What I changed
- Prepared the hosting project for new-domain verification
- Documented the exact DNS work needed before cutover
- Staged the old-domain redirect plan without activating it prematurely
- Added supplied social links and verified the staged deployment
Result
The migration was ready for the external DNS step, while the current domain and live traffic remained intact until the cutover could be completed safely.
Where this fix usually leads next
This kind of work usually connects back to Technical SEO and Production Debugging so the fix note can lead into a clearer support path instead of staying as an isolated one-off task.
What I'd watch next
- Whether DNS records are added exactly as documented
- Whether TLS certificates finish provisioning before redirect activation
- Whether canonical URLs, sitemap, analytics, and Search Console need final domain updates