Study first
Review the ideas behind the questions
Review the migration checks that protect search visibility when URLs, domains, redirects, hosting, and Search Console settings change. Focus on sequencing, mapping, launch controls, and post-launch monitoring.
Separate the move from other changes
A migration gets harder to debug when the team changes the domain, platform, templates, and content at the same time. Keep the search-critical change clear before launch.
- Plan major changes one after another when possible, so ranking and indexing effects are easier to diagnose.
- Prepare a URL mapping from old URLs to new destinations before redirects are turned on.
- Include important embedded asset URLs, such as images, videos, JavaScript, and CSS, in migration planning.
In Practice
A cleaner test section helps
For a large site, a stable section can make a phased test easier to read. A section that changes constantly can hide migration effects behind normal volatility.
Development blocks need a removal list
If staging uses robots.txt blocks or noindex rules, the launch plan needs a clear list of what must be removed before the move starts.
Common mistakes
Combining a redesign, CMS change, and domain move in one launch to save time.
Separate major changes when possible, or document the extra diagnosis risk before the migration starts.
Q&A
Why should important old URLs be inventoried before a migration?
They become the redirect map, sitemap review set, and monitoring group for the pages that most need a clean move.
What makes a migration section safer to test first?
Pick a section that is relatively stable and not heavily affected by seasonal or unpredictable events.
Make redirects and signals agree
The migration launch should send users and crawlers to the final destination clearly. Redirects, canonicals, robots rules, internal links, and sitemaps need to point in the same direction.
- Use server-side permanent redirects when a URL has a durable new location and the server can support them.
- Point old URLs directly to the final destination when possible, and keep redirect chains low when a direct redirect cannot be done.
- After redirects are live, check that canonical links and robots meta rules on the new site use the launch-ready URLs and indexing choices.
In Practice
Irrelevant redirects can look like soft 404s
A mass redirect to the homepage is not a clean migration map. Deleted or merged content needs a relevant destination or an appropriate unavailable response.
Sitemaps should shift to new URLs
Once the move is live, the sitemap work should help discovery of the new URLs. Old sitemap warnings about redirects can be normal during the transition.
Common mistakes
Launching permanent redirects while the new pages still carry staging noindex rules.
Remove launch-blocking noindex rules before the moved URLs are meant to be indexed.
Q&A
When is a temporary redirect a poor fit for a migration?
It is a poor fit when the old URL has permanently moved and the new URL should replace it in search results.
Use Search Console after launch
Search Console does not replace redirects or mapping, but it helps Google understand some moves and helps the team monitor old and new URL behavior.
- Use the Change of Address tool for supported domain or subdomain moves after redirects and pre-work are complete.
- Do not use the Change of Address tool for HTTP-to-HTTPS moves or moves only within a site path.
- Monitor both old and new properties so the old URL counts trend down and new URL counts trend up.
In Practice
Ownership matters
Change of Address needs the same account to own the old and new Search Console properties. Missing variants can leave parts of the move unmanaged.
Hosting changes are a different workflow
A CDN or hosting provider change with the same public URLs is monitored differently from a URL migration. The work centers on testing access, changing DNS, and watching traffic.
Common mistakes
Removing migration redirects as soon as the new domain starts ranking.
Keep redirects in place long enough for recrawling and signal transfer, and update high-value links where possible.
Q&A
What should be submitted after the moved URLs are ready?
Submit the new sitemap in Search Console so Google can learn the new URL set.