Domain Migration with 301 Redirects: Preventing Signal Loss
Key takeawayThe biggest dangers in a domain migration are not the redirects themselves but redirect chains and incomplete mappings. Multi-hop redirects, bulk mapping mistakes, and landing pages that do not correspond all cause signals to decay or break during transfer.
When this applies
- Changing the primary domain or rebranding
- Moving from .com to another TLD or back
- Full migration when changing hosting/CDN but keeping the domain
- Merging an acquired domain into an existing site
| Migration issue | Consequence | Severity | How to avoid |
|---|---|---|---|
| Multi-hop redirect chains | Signals decay with every hop | High | Ensure single-hop redirects to the final destination |
| Bulk mapping mistakes | Landing on irrelevant pages | High | Verify mappings one by one |
| Redirecting 404 pages too | Crawlers get bounced through repeated redirects | Medium | Return 410 where no new page corresponds |
| Old and new domains live simultaneously | Duplicate content gets crawled | High | Full 301 coverage on the old domain, then shut it down |
| Homepage redirected but inner pages not | Signals concentrate on the homepage only | High | Full URL mapping |
| GSC not submitted after migration | New domain indexing starts from zero | Medium | Submit and verify the domain property |
Step-by-step diagnosis
- Export every URL of the old site (from the sitemap and from logs) and build a migration mapping table.
- Validate in a staging environment first: request each old URL and check the redirect chain length, whether the target corresponds, and whether the status is 301.
- Map URL by URL for one-hop redirects; chains like A→B→C are not allowed.
- Old URLs with no corresponding new page: 301 if substitute content exists, otherwise return 410.
- Deploy redirect rules before launching the new site's content, avoiding a window where the new site is empty while the old one already redirects.
- Submit GSC's Change of Address tool only after the new site runs stably and is confirmed crawlable.
- Keep the old domain's 301s for at least 12 months; do not shut it down.
Common mistakes
- Using 302 or meta refresh for migration redirects — temporary redirects do not pass signals.
- Redirecting with JavaScript — crawlers do not execute JS.
- Assuming migration is done while the old site is still live — two domains being crawled simultaneously keeps producing duplicate content.
- Migrating only the navigation links instead of doing a full URL mapping.
- Deleting the old domain immediately after migration — rediscovery by search engines takes months.
- Not exporting a complete URL list before the migration — whatever is missed becomes 404s.
FAQ
How much signal does a domain migration lose?
With single-hop 301s, complete mappings, and identical content, transfer is usually fairly stable. But ranking volatility in the first 2-3 months is common — monitor the recovery curve in GSC.
Should both domains stay live during migration?
Not recommended. The old domain should keep serving 301s but no content; both being simultaneously accessible produces duplicate content.
Does a redesign on the same domain need 301s?
Only if the URL structure changed. If URLs are completely unchanged, focus on checking whether canonicals, titles, and internal links were broken.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.
Related reading
Shopify's Built-in SEO Defects and How to Work Around ThemHow WordPress Plugins End Up Blocking CrawlersAdvanced robots.txt Rules: Blocking Parameters, Pagination, and Useless DirectoriesIndexing Collapsed After a Redesign: How to RecoverMultiple Subdomains Under One Domain: The Dilution Risk ExplainedNote: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.