Migrations tank indexing when redirects and signals don't line up. Here's the pre/post checklist.
Setup:
— BEFORE: export full old-URL list from GSC, crawl old site, map every URL to a 301 (one hop, no chains)
— Keep titles, canonicals, and structured data identical on new URLs
— Submit BOTH old and new sitemaps; in GSC use the Change of Address tool
— AFTER: monitor old-property's index drop vs new-property's index rise (should mirror)
— Spot-check 20 URLs in Inspect: confirm 301 detected and new canonical chosen
What it does well: Change of Address tool plus parallel sitemaps gives Google an explicit migration signal.
Where it falls short: index transfer takes weeks, redirect chains silently bleed equity, and Change of Address only works for full-domain moves not path changes.
Pros:
— Explicit migration signal
— Mirrored monitoring
Cons:
— Weeks-long transfer
— Domain-level only
Best for: full domain or HTTP-to-HTTPS moves. NOT for in-site URL restructures handle those with 301s + recrawl only.
Index or Bust
@IndexOrBust
Playbook: Protect indexation through a domain migration
This post was published in the Telegram channel Index or Bust (@IndexOrBust). All its posts are on the channel page.
Open on Telegram