Domain Migration SEO Checklist

Domain migrations need technical and editorial planning

Moving a website to a new domain is one of the riskier SEO changes a team can make. Search engines need to understand that old URLs have moved to new URLs. Users need to land on the right pages. Analytics needs to continue tracking. Backlinks should pass signals through clean redirects. A migration can go smoothly, but only when the details are planned before launch.

The biggest mistake is treating a domain migration like a normal deploy. It is not just a DNS change. It affects URLs, canonical tags, redirects, sitemaps, internal links, structured data, email links, social profiles, Search Console properties, and sometimes brand trust. A checklist keeps the move from becoming a pile of small missed tasks.

Map every important old URL to a new URL

Before launch, export the current URL list from the sitemap, crawl data, analytics, Search Console, and backlink tools if available. Map each important old URL to the most relevant new URL. Avoid redirecting everything to the homepage. That creates a poor user experience and weakens topical signals. Article pages should redirect to their matching article pages, not a generic blog index.

Use 301 redirects for permanent moves. Keep redirects one hop whenever possible. A chain from old URL to intermediate URL to final URL slows users and creates more room for failure. Test redirects in bulk and manually inspect high-value pages.

Update signals on the new domain

The new site should use canonical tags pointing to the new URLs, not the old domain. Internal links should point directly to the new domain. XML sitemaps should list the new canonical URLs. Structured data should use new page URLs where relevant. Open Graph and social metadata should also reflect the new domain.

Analytics and tag manager settings may need updates. Referral exclusions, cross-domain tracking, conversion settings, and consent behavior should be checked. A migration that preserves rankings but breaks reporting still creates business confusion.

• Create a URL redirect map before launch.
• Use one-hop 301 redirects from old URLs to equivalent new URLs.
• Update canonicals, internal links, sitemaps, structured data, and analytics.
• Monitor Search Console, logs, rankings, and 404s after launch.

Search Console needs both domains

Verify both the old and new domains in Search Console. Submit the new sitemap. Use the change-of-address tool when appropriate. Monitor indexing, crawl errors, coverage, and search performance. Expect some fluctuation after migration. The goal is to catch preventable problems early, not panic over every short-term movement.

Server logs are useful after launch because they reveal whether search crawlers are hitting old URLs, following redirects, and discovering new pages. If important old URLs return 404 instead of redirecting, fix them quickly.

Keep redirects long-term

Do not remove redirects after a few weeks. Backlinks, bookmarks, old emails, documentation, and search results can keep old URLs alive for a long time. Redirects should remain for at least many months, and often much longer for important content. Removing them too soon can waste the value of old links and frustrate users.

A domain migration is successful when users, crawlers, analytics, and links all arrive at the right new pages. With a careful redirect map, consistent canonical signals, updated sitemaps, and post-launch monitoring, the move can preserve trust while giving the new domain a clean start.