What Domain Migration Actually Risks

Search engines have spent years learning that oldsite.com is associated with certain queries, has earned certain backlinks, and serves certain content. When you move to newsite.com, you are asking Google to transfer all of that signal to a new entity.

It can be done with minimal loss. Most well-executed migrations recover within 4–8 weeks and lose less than 5% of organic traffic. Most poorly-executed migrations lose 30–60% and never fully recover.

The difference is not magic. It is a checklist.

The Pre-Migration Audit (2–4 Weeks Before)

1. Baseline Your Current Performance

  • Export all organic landing pages from Google Search Console (last 90 days).
  • Export all queries you rank for, with their current positions.
  • Export all backlinks (from Search Console + Ahrefs/Semrush if you have them).
  • Save analytics traffic data for the last 12 months.

You need this baseline to (a) know what you are protecting and (b) measure recovery later.

2. Crawl the Old Site

Use Screaming Frog or a similar crawler to enumerate every URL on the existing site. You need:

  • Every page that returns a 200 status.
  • Every URL that has incoming traffic, even if it is not in your sitemap.
  • Every URL with backlinks pointing to it.

The combined list is your redirect map source. Every URL on this list needs a destination on the new domain.

3. Build the URL Mapping

For each old URL, decide its new URL on the new domain. Three patterns:

  • One-to-one mirror: /about → /about. Easiest, lowest-risk. The default for straight rebrands.
  • Restructured paths: /blog/post-name → /articles/post-name. Higher risk; only do this when the new structure is materially better.
  • Consolidation: 5 old pages → 1 new page. Highest risk. Only when you genuinely have redundant content.

Document the mapping in a spreadsheet. Every old URL gets a redirect target.

The Pre-Launch Setup (1 Week Before)

4. Set Up the New Domain

  • The new domain is registered and resolving.
  • Content is fully migrated (not partial).
  • HTTPS works. SSL cert is valid.
  • Canonical tags on every page point to the new domain.
  • The new sitemap is generated and references the new domain only.
  • The new robots.txt is correct.

5. Verify the Redirect Plan

  • 301 redirects (permanent, search-engine friendly) — NOT 302 (temporary).
  • Redirects go directly from old URL to final new URL — NO intermediate hops. Each chain hop loses signal.
  • Redirect targets are 200-status pages on the new domain. Test a sample.
  • HTTPS-to-HTTPS direct, not via HTTP intermediate.

6. Prepare Both Search Console Properties

  • Both old and new domains verified in Google Search Console.
  • Both verified in Bing Webmaster Tools.
  • You can submit Change of Address from the old to the new in GSC.

Migration Day

7. Switch DNS

The new site goes live. Or, if both are already live, the redirect rules activate.

8. Activate the 301 Redirects

Every old URL now 301-redirects to its new counterpart. Verify with a sample:

  • Pick 20 old URLs (homepage, top blog posts, top product pages, deep pages).
  • Use curl -I oldsite.com/path or a redirect-checker tool.
  • Confirm: 301 status, correct destination, single hop.

9. Submit Change of Address in Google Search Console

In the old domain's GSC property: Settings → Change of Address. Specify the new domain. This explicitly tells Google about the move.

10. Submit New Sitemap

In the new domain's GSC property, submit the new sitemap. Resubmit even if you submitted it before launch.

11. Update External References

Where you can:

  • Social media bio links.
  • Google Business Profile.
  • Apple Business Connect, Bing Places.
  • Top backlinks (the ones driving real referral traffic — reach out to the 10–20 most important and ask them to update).
  • Email signatures across your team.
  • Anywhere your URL appears in marketing materials.

The First 4 Weeks Post-Migration

12. Monitor Daily for Week 1

  • Check GSC indexing status on the new domain.
  • Check rankings for top queries — expect some volatility.
  • Check that the old domain is showing decreasing impressions and the new domain showing increasing impressions.
  • Check redirects still work (sometimes hosting changes break them).
  • Watch for unexpected 404s or 5xx errors in server logs.

13. Expect a Temporary Dip

Almost every migration sees a 10–30% temporary traffic drop in weeks 1–3. This is normal — Google is reindexing, learning the new patterns, and updating the link graph. Do not panic. Do not start changing things mid-migration; that introduces new variables.

14. Continue Monitoring for 8 Weeks

By week 4–6, traffic should be approaching pre-migration levels. By week 8, recovery should be 95%+. If not:

  • Check that redirects are still in place (one of the most common mid-migration regressions).
  • Recrawl the new site and check for technical issues (missing canonical tags, broken internal links, robots.txt blocks).
  • Review GSC's Coverage report for indexing problems.

Common Mistakes

  • Using 302 instead of 301. 302 is temporary and signals "this is not a permanent move." Search engines treat it differently. Always 301.
  • Redirect chains. Old URL → intermediate URL → final URL loses signal at each hop. Map directly.
  • Removing the redirects after a few months. Keep them indefinitely. Old links from external sites do not stop being clicked.
  • Migrating content and structure simultaneously. One change at a time. Move the domain first; restructure URLs months later if needed.
  • Letting the old domain expire. Renew it for at least 5 more years even after the migration. Losing the old domain means losing all the redirects.
  • Forgetting to update sitemap and robots.txt on the new domain. Easy to miss, breaks indexing.
  • Disallowing robots on the old domain to "force" Google to focus on the new one. This blocks Google from seeing the redirects. Do not do it.

The Redirect Map Persistence Question

How long do you keep the 301 redirects active? Forever. The marginal cost is essentially zero. The marginal value of catching a click from a 5-year-old blog post that linked to your old domain is real. Plan to maintain the redirects (and renew the old domain) indefinitely.

The Migration Calculator

Realistic outcomes for well-executed migrations:

  • Week 1–2: 70–85% of pre-migration traffic.
  • Week 3–4: 80–90%.
  • Week 5–8: 90–98%.
  • Month 3+: approximately back to baseline, often slightly above due to fresh indexing.

If you are still 30%+ down at week 8, something is structurally wrong with the migration. Audit the redirects, the sitemap, the canonical tags, and the indexing in GSC.

The Honest Takeaway

Domain migration is not magic, but it is unforgiving of shortcuts. The checklist exists because every item on it has, somewhere, been the cause of a botched migration. Following it carefully gives you a 95%+ recovery rate. Skipping items gives you a story to tell about why traffic never came back.