Domain migrations — moving a website from one domain to another — represent one of the highest-risk SEO operations a site can undergo. Unlike most technical changes that affect individual pages or sections, a domain migration affects every URL on the site simultaneously. Done correctly, rankings recover within a few Google crawl cycles (weeks). Done poorly, traffic losses can persist for months.
Why Domain Migrations Cause Ranking Drops
When a site moves domains, Google must:
- Discover the new domain exists
- Crawl and index pages on the new domain
- Verify that the 301 redirects connect old URLs to new URLs
- Transfer ranking signals (PageRank, link equity) from old URLs to new URLs
- Remove old URLs from the index and consolidate to new URLs
This process takes time — typically 2–8 weeks for a well-executed migration. During this window, rankings may fluctuate as Google is in transition. The goal of pre-migration preparation is to minimize this window and ensure Google has everything it needs to execute the transition quickly.
Additionally, external backlinks point to the old domain. 301 redirects pass link equity, but the equity transfer isn’t instant and some equity is lost in the redirect hop. Sites with strong backlink profiles have more to preserve — and more to lose — in a migration.
Pre-Migration Preparation
Export the complete URL inventory. Every indexed URL must be accounted for in the redirect map. Sources: GSC Coverage report, XML sitemap, crawl tool output. Don’t rely on just one source — they may each miss some URLs.
Build the redirect map before migration. For each old URL, define the exact destination URL on the new domain. One-to-one redirects (same-path) are cleanest. When URLs change structure, match old pages to the most semantically equivalent new pages.
Update internal links pre-launch. Plan to update all internal links to use the new domain — both to avoid redirect chains and to signal to Google that the new domain is authoritative.
Notify link partners. For significant backlinks you have relationships with, request direct link updates to the new domain after migration. This eliminates the redirect chain for those links.
Verify the new domain in GSC. Set up Google Search Console property for the new domain before migration. You’ll need it immediately after launch.
The Migration Launch Checklist
Implement 301 redirects at the server level. Not meta refresh, not JavaScript — server-side 301s. All old URLs must redirect to their exact equivalent on the new domain.
Update the XML sitemap. The sitemap should reference new domain URLs only. Remove old domain URLs.
Update canonical tags. All canonical <link> tags must reference the new domain.
Update structured data URLs. JSON-LD url, sameAs, and other URL fields should use the new domain.
Update robots.txt. Ensure it doesn’t accidentally block crawling of the new domain.
Set up the new domain in GSC. After launch, verify the new domain and submit the updated sitemap.
Use GSC’s Change of Address tool. Google Search Console has a “Change of Address” feature under Settings that officially notifies Google of a domain migration. This accelerates the transition.
GSC Change of Address
The Change of Address tool in GSC (Settings → Change of Address) is specifically designed for domain migrations. It:
- Notifies Google of the domain change
- Helps Google speed up the ranking signal transfer
- Allows you to specify the old and new GSC properties
To use it:
- Both old and new domain must be verified properties in GSC
- Navigate to the old property’s Settings → Change of Address
- Enter the new domain property
- Verify 301 redirects are in place
- Submit
GSC Change of Address doesn’t replace proper redirect implementation — it supplements it.
Post-Migration Monitoring
First 72 hours: Check that redirects are working at the URL level. Crawl the old domain with Screaming Frog to confirm 301s are returning and pointing to correct new domain URLs. Spot-check in browser.
First 2 weeks: Monitor GSC for the new domain. Watch for:
- Indexation rate of new domain URLs (Coverage report)
- Old domain URLs appearing as errors (they should be redirected and removed)
- Traffic transition from old to new domain in analytics
Weeks 3–8: Rankings may fluctuate. Some pages may temporarily lose rankings as Google recrawls and reindexes. This is normal during migration. The trajectory should be toward recovery, not continued decline.
Long-term: Monitor for stray old domain URLs still indexed, redirect chain issues as the site evolves, and any backlinks that still point to old domain URLs.
Common Domain Migration Mistakes
302 redirects instead of 301: 302 (temporary) signals the old URL is still the canonical. Use 301 (permanent) for all domain migration redirects.
Redirecting everything to the homepage: When you can’t match old URLs to specific new pages, redirecting to the homepage is the worst fallback. Google sees it as a soft 404 — the page was redirected but doesn’t answer the original URL’s implied content. A 410 (Gone) is cleaner than a redirect to an unrelated page.
Missing the Change of Address notification: Not using GSC’s Change of Address tool leaves Google to discover the migration organically, slowing signal transfer.
Changing too much simultaneously: A domain migration plus site redesign plus URL restructure plus CMS change happening simultaneously is extremely difficult to debug if rankings don’t recover. If possible, isolate the domain change and make other changes before or after, not simultaneously.
Not monitoring old domain traffic post-migration: Old domain rankings disappear, but traffic to old domain URLs via direct links, bookmarks, and cached results should redirect successfully. Monitor old domain logs for 404s that indicate gaps in the redirect map.
A clean migration with comprehensive redirects, GSC Change of Address, and immediate sitemap submission typically sees ranking recovery within 4–6 weeks for established sites with strong link profiles.