Domain Change SEO Checklist: Preserving Rankings During a Site Migration

Domain Change SEO Checklist: Preserving Rankings During a Site Migration

A domain change is one of the most technically complex SEO operations your site will ever undergo. Unlike a simple redesign or content refresh, switching domains involves rebuilding your entire search footprint from scratch—crawl budget reallocation, link equity transfer, and indexation re-establishment. Even a minor oversight in redirect mapping or canonical tag implementation can result in significant traffic losses that may take months to recover. This checklist, grounded in technical SEO audit principles, walks you through every critical step to execute a domain migration without destroying your organic visibility.

Pre-Migration Audit: Establish Your Baseline

Before touching any DNS settings or server configurations, you must document your current site's performance metrics. This baseline serves as your recovery target and your proof-of-correctness when something goes wrong.

Step 1: Capture your existing ranking data. Export all keyword positions from your tracking tool (e.g., Google Search Console, Ahrefs, Semrush). Record not just top-20 terms but also long-tail queries where you hold page-2 or page-3 positions—these are often the first casualties of a broken migration.

Step 2: Document your backlink profile. Run a full backlink audit using your preferred tool. Record your site's authority metrics (such as Domain Authority from Moz or Trust Flow from Majestic) and the total number of referring domains. Pay special attention to links pointing to your highest-traffic pages; these are the ones you cannot afford to lose. Note that these metrics are third-party estimates and not official Google signals.

Step 3: Audit your current technical health. Run a comprehensive technical SEO audit covering:

  • Crawl budget utilization (how many pages Googlebot crawls daily)
  • Core Web Vitals scores (LCP, CLS, FID/INP)
  • Indexation status (how many pages are indexed vs. submitted)
  • Existing redirect chains or loops
This data tells you whether your current domain has underlying issues that might complicate the migration or that you should fix before moving.

Mapping the Migration: URL Structure and Redirect Strategy

The single most common cause of domain-change failure is a poorly planned redirect map. You cannot simply redirect the old domain's homepage to the new one and hope for the best.

Step 4: Create a complete URL inventory. Crawl your entire existing site using a tool like Screaming Frog or Sitebulb. Export every URL, its status code, its page title, and its approximate traffic value (from Google Analytics or Search Console). Group URLs by content type (blog posts, product pages, category pages, landing pages).

Step 5: Decide on URL structure for the new domain. You have two options:

  • Preserve the exact path structure (e.g., olddomain.com/blog/post → newdomain.com/blog/post). This is the safest approach because it minimizes redirect complexity.
  • Restructure URLs (e.g., olddomain.com/blog/post → newdomain.com/resources/post). This is riskier but sometimes necessary for rebranding or site reorganization.
If you choose to restructure, you must create a one-to-one mapping for every URL. Never use wildcard redirects or regex patterns unless you have tested them exhaustively.

Step 6: Implement 301 redirects with no chain. Every old URL must redirect directly to its corresponding new URL. No intermediate hops. A single redirect chain (old → intermediate → new) dilutes link equity and increases page load time. Use the table below to validate your redirect logic:

Old URLNew URLRedirect TypeChain Length
example.com/page-anewexample.com/page-a3011
example.com/page-bnewexample.com/page-b3011
example.com/old-categorynewexample.com/new-category3011

Step 7: Update your XML sitemap and robots.txt. Generate a fresh XML sitemap containing only URLs from the new domain. Submit it to Google Search Console as soon as the new site is live. Update your robots.txt file to point to the new sitemap location and ensure no critical pages are accidentally blocked.

Technical Implementation: On-Page and Server-Level Changes

Once your redirect map is ready, you need to execute the technical changes that tell search engines your new domain is the canonical source of truth.

Step 8: Implement canonical tags correctly. Every page on the new domain must include a self-referencing canonical tag pointing to its own URL. For example, `rel="canonical" href="https://newdomain.com/page-a"`. This prevents duplicate content issues if both domains remain accessible for any period.

Step 9: Update all internal links. Crawl the new site and check for any internal links that still point to the old domain. These are often found in:

  • Navigation menus
  • Footer links
  • Content body links
  • Image source URLs
  • JavaScript files
Use a find-and-replace tool or a database query to update all internal references. Any internal link to the old domain creates a redirect loop and wastes crawl budget.

Step 10: Update external references where possible. While you cannot control third-party sites, you should update:

  • Social media profiles (bio links, pinned posts)
  • Business directory listings (Google Business Profile, Yelp, etc.)
  • Email signatures
  • Paid ad campaign landing pages
  • Any backlinks you control (e.g., guest posts, partner sites)

Post-Launch Monitoring: Verify the Migration Worked

The migration is not complete when the new domain goes live. You must monitor performance for at least 4–8 weeks to ensure everything settled correctly.

Step 11: Check indexation within 72 hours. Use Google Search Console's URL Inspection tool to manually request indexing for your most important pages (homepage, top 20 traffic pages, key category pages). Within a week, you should see the new domain's pages appearing in search results.

Step 12: Monitor for duplicate content issues. Run a duplicate content check comparing the old domain (if still accessible) and the new domain. If Google indexes both, you may see ranking fluctuations or traffic splitting. If possible, set the old domain to return a 410 (Gone) status after confirming the migration has propagated.

Step 13: Watch your Core Web Vitals. A domain change often involves a server migration or platform change. Monitor LCP, CLS, and INP scores daily for the first two weeks. A sudden drop in Core Web Vitals can offset any gains from the migration itself.

Step 14: Track ranking recovery weekly. Compare your new domain's keyword positions against your pre-migration baseline. Expect a temporary dip in rankings in the first few weeks as Google re-evaluates your site. If rankings drop substantially below baseline after four weeks, investigate redirect issues or duplicate content problems.

Risk Awareness: What Can Go Wrong

Even with perfect execution, domain changes carry inherent risks. Here are the most common failure modes and how to mitigate them:

Redirect chains and loops. A single misconfigured redirect can create a chain that wastes crawl budget and dilutes link equity. Use a redirect checker tool to validate every path before going live.

Black-hat link building. Some agencies or SEOs might suggest buying expired domains or using PBNs to "boost" your new domain's authority. This is a fast track to a manual penalty. Your new domain's backlink profile should consist entirely of legitimate, earned links from the migration and ongoing content strategy.

Crawl budget starvation. If your new domain has thousands of low-value pages (thin content, duplicate product variants, paginated archives), Googlebot may waste its limited crawl budget on those instead of your high-priority pages. Conduct a technical SEO audit post-migration to ensure crawl budget is allocated efficiently.

Conclusion: The Checklist Is Your Safety Net

A domain change is not a set-and-forget operation. It requires meticulous planning, precise execution, and ongoing monitoring. Use the checklist above as your operational blueprint, but remember that every site has unique quirks. Run a full technical SEO audit before you start, test your redirect map exhaustively, and monitor Core Web Vitals and indexation status for at least two months after launch.

For further reading on related migration scenarios, see our guides on migrating sites SEO, protocol change SEO, and URL structure changes. If you are planning a full site relaunch, the site relaunch SEO checklist covers additional considerations like design changes and content consolidation. Finally, be aware of redirect chain risks and how to identify them before they damage your rankings.

Russell Le

Russell Le

Senior SEO Analyst

Marcus specializes in data-driven SEO strategy and competitive analysis. He helps businesses align search performance with business goals.

Reader Comments (0)

Leave a comment