Why Domain Migrations Go Wrong
A domain migration is one of the few technical SEO events that can undo years of accumulated rankings in a single afternoon — not because moving domains is inherently risky, but because most migrations skip steps that seem optional and aren't. Google has to rediscover every URL on your new domain, match it to the equivalent old URL, and transfer trust signals across. If that mapping is incomplete, sloppy, or missing entirely, rankings don't transfer — they reset.
Done properly, a migration can be close to seamless, with most sites recovering original ranking levels within 4–12 weeks. Done carelessly, recovery can take six months or never fully happen. The difference is almost entirely in the preparation.
Step 1: Audit Your Current Site Before You Touch Anything
Before registering anything new, get a complete picture of what you're migrating:
- ›Full list of indexed URLs (export from Google Search Console's Page Indexing report)
- ›Current top-performing pages by organic traffic
- ›Current backlink profile — which pages are earning external links
- ›Current keyword rankings as a baseline to measure recovery against
Skipping this step means you won't know if the migration worked until traffic has already dropped, with no way to diagnose what specifically broke.
Step 2: Register and Prepare the New Domain
Register your new domain and get hosting fully configured — HTTPS, DNS, and a staging version of the site — before redirecting a single URL from the old domain. Use our domain availability checker to confirm the new name is open across the extension you want, and see our domain extensions guide if you're reconsidering your TLD as part of the move.
Step 3: Build a Complete URL Redirect Map
This is the step most migrations get wrong. You need a 1:1 map from every old URL to its exact new equivalent — not a blanket redirect of everything to the new homepage. A homepage-only redirect discards the accumulated authority of every individual page and is one of the fastest ways to lose rankings during a migration.
Build the map as a spreadsheet: old URL in one column, new URL in the other. For a small site this might be 20 rows; for a large site, it can be thousands. There's no shortcut here — incomplete mapping is the single biggest cause of failed migrations.
Step 4: 301 vs 302 — Use the Right One
This distinction matters more than most site owners realize:
- ›301 (permanent redirect) tells search engines the move is permanent and to transfer ranking signals to the new URL. This is what you want for a domain migration.
- ›302 (temporary redirect) tells search engines the old URL might come back, so they hold onto the original URL in the index and don't fully transfer signals.
Using 302s for a permanent migration is a common mistake that quietly stalls signal transfer for months. Confirm every redirect in your map is configured as a 301, not the framework or CDN's default.
Step 5: Update Internal Links, Not Just Redirects
Redirects handle external traffic and existing backlinks, but your own site's internal links should point directly to the final new URLs — not rely on hopping through a redirect chain. Every redirect hop adds latency and dilutes a small amount of link equity. Update navigation, footer links, and any hardcoded internal links across your codebase before or immediately after launch.
Step 6: Migrate in Google Search Console
Once redirects are live and verified working, use Search Console's Change of Address tool (available when both old and new domains are verified properties) to formally tell Google about the move. This doesn't replace redirects — it supplements them by speeding up how quickly Google processes the change across your entire site rather than discovering it URL by URL.
Step 7: Update Your Sitemap and Robots.txt
Generate a fresh sitemap for the new domain reflecting its actual live URLs, submit it in Search Console, and make sure robots.txt on the new domain isn't accidentally blocking crawlers (a shockingly common launch-day mistake when staging environment configs get carried over to production). Leave the old domain's sitemap and redirects live — don't cancel the old domain's hosting or DNS until the migration is fully settled.
Step 8: Monitor Traffic and Rankings for 90 Days
Expect a temporary dip in the first two to four weeks even with a perfect migration — this is Google reprocessing your URLs, not a sign of failure. Watch Search Console's Page Indexing and Performance reports weekly. If rankings haven't started recovering by week six, check for broken redirects, missed URLs in your map, or accidental 302s before assuming something bigger is wrong.
Timeline: What to Expect Week by Week
- ›Weeks 1–2: Traffic dips as Google discovers and processes redirects; this is expected
- ›Weeks 3–6: Indexed pages on the new domain climb; rankings begin partially recovering
- ›Weeks 6–12: Most well-executed migrations reach 80–100% of prior ranking levels
- ›Beyond 12 weeks without recovery: Something in the redirect map, internal linking, or technical setup needs auditing
Keep the old domain registered and pointed via 301 redirects indefinitely if possible — letting it expire later can orphan any backlinks that still point directly to old URLs instead of being routed through your redirect chain.