Search Console needs specific handling during a domain change, and the steps are easy to get wrong in ways that cost you data rather than rankings. The rankings are handled by redirects; Search Console is about visibility into whether those redirects are working.
Before the move
- Verify the new domain as its own property, ideally as a domain property so all variants are covered.
- Export everything from the old property. Performance data, index coverage and link reports. Search Console retains sixteen months and the old property becomes progressively less useful.
- Record a baseline of queries, pages and impressions so the comparison afterwards is real.
- Export the indexed URL list, which is a critical input to redirect mapping and frequently contains pages no crawl finds.
That last export is the one people regret skipping. Reconstructing it afterwards is far harder than downloading it beforehand. See pre-migration audit.
At the move
- Use the Change of Address tool in the old property. It requires site-wide redirects to already be in place and both properties verified.
- Keep the old property verified. Do not remove it, since it reports how the old URLs are being processed.
- Submit the new sitemap in the new property.
- Do not delete the old sitemap abruptly. It helps Google find the old URLs that need recrawling to discover the redirects.
The Change of Address tool
It signals a site move and speeds processing. It does not replace redirects and it does not transfer anything by itself.
- Redirects must be in place first, or it will not accept the request.
- It applies to a full domain move, not a partial one or a path change within a domain.
- It does not work for moves between subdirectories on the same domain.
- Its effect is a signal, not a transfer. The redirects do the actual work.
After the move
- Monitor both properties. The old one shows old URLs dropping; the new one shows new URLs appearing.
- Watch index coverage on the new property for unexpected exclusions.
- Check for old URLs still indexed, which usually indicates a missing redirect. See old URLs still indexed.
- Compare performance against the exported baseline rather than against the previous month.
- Expect the old property’s data to decline as URLs are reprocessed. That is the migration working, not failing.
What people get wrong
- Removing the old property immediately, losing visibility into whether the move is being processed.
- Using Change of Address before redirects are live, which fails.
- Expecting it to move rankings, when it only signals the move.
- Failing to export historical data before it ages out.
- Deleting the old sitemap on launch day, slowing discovery of the redirects.
Frequently asked questions
Is the Change of Address tool essential?
Not essential; redirects do the substantive work. It speeds processing and is worth using where eligible, which is a full domain move with site-wide redirects in place.
How long should I keep the old property?
At least a year. It is your only view of how old URLs are being processed, and that visibility matters most when something goes wrong.
Can I use it for a subdirectory move?
No. It covers domain and subdomain moves. Path changes within a domain rely on redirects alone.
Will my historical data transfer?
No. The new property starts fresh. Export from the old property beforehand or that history is lost when it ages out.
Consulting CTA
If you are planning a domain change, book an SEO consultation early enough to capture the exports and baseline before anything moves.