How to Prepare a Website for a Domain Change

Plan the switch with a rollback decision before changing public DNS. Lowering a DNS time-to-live may help some resolvers notice the change sooner, but it does not control every cache. Keep the old site and certificate available while redirects and email are checked. Test canonical URLs, feeds, structured data, images, forms, analytics, translated routes, and important links. Monitor server errors and certificate warnings after the change. Tell partners that use callbacks or allowlisted domains. A domain move is complete when visitors, search systems, integrations, and people who saved old links all reach the intended resource.

Prepare a complete URL inventory before changing the domain. Include pages, images, feeds, canonical links, structured data, redirects, analytics settings, email addresses, third-party callbacks, and documentation. Register the new domain through a trusted provider and configure certificates before the public switch. Keep redirects from every important old URL to the closest matching new URL, not only to the home page. Update internal links, sitemap, robots rules, social previews, and search-console properties where relevant. Test a staging copy and a sample of old URLs from different devices. Keep the old domain active long enough to catch missed references and monitor errors after launch.

Inventory the current address

A domain change affects more than the home page. List important pages, subdomains, images, scripts, feeds, APIs, email addresses, downloads, dashboards, redirects, certificates, and third-party references. Record owners and providers. Search source code, documentation, analytics configuration, account settings, social profiles, and printed material for the old address.

Confirm the reason, timing, ownership, renewal, DNS access, hosting, email, and rollback plan. Keep the old domain under control for an appropriate transition period. Do not let a domain expire while old links, account recovery, or email delivery still depend on it.

Prepare the new domain

Register the correct name through a trusted provider and secure the registrar account with unique credentials and multi-factor authentication. Configure DNS, hosting, certificates, email authentication, redirects, and security headers in a testable order. Check that the new site serves the correct content over secure transport and that canonical and alternate-language references point to the intended domain.

Use a staging or controlled test where possible. Test the home page, articles, forms, search, account flows, files, images, APIs, and error pages. Check mobile layout, accessibility, language versions, and time-sensitive content. Do not expose private staging data or allow search systems to index a test environment unintentionally.

Redirect and update references

Map each important old URL to its closest current destination. Use server-side permanent redirects when the move is permanent and avoid sending every page to a generic home page. Update internal links, structured content, sitemap, robots rules, feed links, metadata, analytics, advertising, support documents, and external services. Keep URLs readable and stable.

Change email addresses carefully. Create forwarding or aliases where appropriate, notify people through trusted channels, and protect the new mailbox. Check password resets, receipts, contact forms, and automated notifications. A website move can become an account recovery problem if email ownership is not treated as part of the project.

• Keep a complete redirect map and test sample URLs.
• Check certificate coverage for every required host.
• Monitor errors, traffic, forms, and mail after launch.
• Keep rollback files and provider contacts available.

Monitor the transition

Publish at a quiet time with a clear owner watching the change. Check both old and new addresses, redirects, status codes, logs, search tools, feeds, and important user journeys. Fix broken paths quickly and record each change. Tell users what they need to know without exposing internal infrastructure details.

A domain change is a coordinated identity and navigation project. Complete URL inventory, secure ownership, precise redirects, updated references, and post-launch monitoring protect access and reduce confusion for readers, customers, and search systems.

Keep the old domain active long enough for established links and caches to update according to your risk and provider guidance. Review external links you control and ask important partners to update them directly. When the transition is stable, remove temporary rules carefully and keep the final mapping in the maintenance archive. A clean end is as important as a careful launch.