Migrations are where good sites lose traffic. A new CMS, a redesign, a domain change or an HTTPS switch can each change thousands of URLs, and small mistakes multiply: one wrong redirect rule, one template that adds noindex, one environment setting copied from staging.
The fix isn’t a longer checklist. It’s measuring the site before and after, so every change is visible. This guide builds a migration plan around three crawls, and links to a detailed guide for each kind of migration.
Which kind of migration is it?
The process below applies to all of them, but each type has its own risks:
| Migration | What changes | Main risk | Guide |
|---|---|---|---|
| Domain change | Every URL’s host | Signals not transferred; Change of Address needed | Changing your domain |
| Merge two websites | Two URL inventories become one site | Overlapping pages mapped to irrelevant destinations | Merging two websites |
| Regional ccTLD consolidation | Country domains move to locale paths or hosts | Lost regional signals and broken hreflang pairs | ccTLD SEO migration |
| Subdomain to subfolder | Host and path for the moved section | Incomplete URL mapping or old-host signals | Subdomain to subfolder migration |
| CMS or platform change | Templates, often URLs and rendering | Lost titles, content, links or structured data | CMS migration SEO |
| URL structure change | Paths on the same domain | Missing or wrong redirects | Redirect mapping |
| HTTP to HTTPS | Protocol | Missing redirects, mixed content | HTTP to HTTPS migration |
| Hosting or CDN change | Infrastructure only, same URLs | Server errors, blocked crawlers | Hosting migration SEO checklist |
| Redesign on the same URLs | Templates and content | Lost content and internal links | CMS migration SEO (same comparison method) |
For infrastructure-only moves, Google’s moves without URL changes guidance is the baseline; the hosting checklist turns it into pre- and post-launch checks.
When several languages or markets move at once, use the technical international SEO guide for the locale architecture and the international URL mapping guide to pair old and new pages, redirects, canonicals and hreflang.
What can go wrong in a migration?
- Old URLs that don’t redirect, or redirect to the homepage
- Redirect chains and loops from stacked rules
noindexor a staging robots.txt left on the live site- Canonicals, hreflang and sitemaps still pointing at old URLs
- Internal links still pointing at old URLs, adding a redirect hop to every visit
- Content, titles or structured data lost in templates
- Pages with search traffic left out of the redirect map
Google’s guide to site moves with URL changes covers the essentials; the checklist below turns it into crawls you can run.
Before launch: benchmark the old site
Crawl the entire old site and keep that crawl. It’s your record of every URL, its status, title, canonical and indexability, and the baseline you’ll compare against.
Pull traffic data. Connect Search Console and GA4 so you know which URLs bring clicks and visits. Those are the URLs the redirect map must get exactly right.
Build the redirect map. One row per old URL, with its new equivalent. Map page to page, not everything to the homepage. Export the old crawl’s URL list as the starting point. The full method, including pages with no equivalent, is in redirect mapping.
Before launch: crawl the new site
Crawl the staging site and check it. If staging sits behind a login, allow your crawler’s IP address instead (Crawlens doesn’t log in to sites), and if staging disallows crawling in robots.txt, turn off Respect robots.txt for this crawl. Then check:
- Indexability: no accidental
noindex, robots.txt rules or canonicals to staging URLs - Canonicals: every page has a self-referencing canonical on the new URL, as Google recommends
- Internal links use new URLs and none are broken
- Hreflang points to new URLs
- Titles, meta and structured data survived the new templates
- JavaScript rendering, if the new front end renders in the browser: compare raw and rendered HTML
Crawlens’s audit covers each of these: indexability, canonical, link, hreflang, content and structured data checks run on every crawl.
The staging site SEO guide separates private preview access from launch-time indexing controls, so a staging noindex or robots rule does not reach production.
At launch: redirects
Google’s guidance:
- Use server-side permanent redirects (301 or 308).
- Redirect to the final destination directly. Googlebot can follow up to 10 hops, but Google advises keeping chains low, ideally no more than 3. See redirect chains.
- Keep redirects for at least a year, so signals can transfer.
- Update internal links, canonicals, hreflang and sitemaps to the new URLs.
- If the domain or subdomain changes, check whether the exact source and destination are eligible for Search Console’s Change of Address tool. Do not assume a move into a path on an existing host qualifies; redirects, updated links and sitemaps remain essential. See subdomain-to-subfolder migration for that case.
After launch: verify every old URL
Crawl the old URL list in Crawlens’s URL list mode (paste or import the URLs from your benchmark crawl). Every old URL should return one permanent redirect to its mapped new URL. The audit flags:
| Check | What it catches |
|---|---|
| Redirect chains (2+ hops) | Old URLs taking several hops |
| Redirect loops | Rules that send URLs in circles |
| Temporary redirects | 302/307 used where 301 is needed |
| Internal pages return 4xx | Old URLs with no redirect at all |
| HTTP version does not redirect to HTTPS | HTTPS migrations missing the site-wide redirect |
Check URLs with traffic first. With Search Console and GA4 connected, two checks catch the costly mistakes directly: pages with search traffic that return errors and landing pages with visits that return errors. Pages with search traffic that are not indexable catches noindex and canonical mistakes on pages that earn clicks.
After launch: compare and keep watching
Crawl the new site and compare with a previous crawl of it. If URLs didn’t change (a redesign or replatform on the same URLs), compare directly with the old-site crawl. Crawlens’s comparison shows new and fixed issues per check, plus URL changes: new URLs, URLs no longer found, status code changes, pages that became non-indexable, and changed titles.
Schedule crawls daily or weekly for the first weeks, with email alerts when the health score drops or new critical issues appear. Migrations often break things a few days later, when a cache clears or someone “fixes” a redirect rule.
Expect some movement. Google says rankings can fluctuate temporarily, and for medium-sized sites it can take a few weeks or more for the new URLs to replace the old ones in search. If the drop is deeper or lasts longer, see traffic drop after a site migration.
Keep the old-to-new map after launch, not just the crawl report. The post-migration redirect monitoring plan explains which old URLs and destinations to retest after later CMS, routing and CDN changes.
Checklist
For the full task list by phase and migration type, with progress saved and a CSV export for your team, use the interactive SEO migration checklist. The short version:
Before launch
- Full crawl of the old site saved as a benchmark
- Search Console and GA4 data pulled for every URL
- Page-to-page redirect map, including every URL with traffic
- New site crawled on staging: indexability, canonicals, links, hreflang, content, structured data
At launch
- 301/308 redirects straight to final URLs
- Internal links, canonicals, hreflang and sitemaps use new URLs
- Staging
noindexand robots.txt rules removed - Change of Address submitted (domain or subdomain moves only)
After launch
- Old URL list crawled: one permanent redirect each, to a 200, indexable page
- No errors or noindex on URLs with search traffic or visits
- New crawl compared with the baseline
- Scheduled crawls with alerts for the first weeks
- Redirects kept for at least a year
All Site Migrations guides
- Monitor redirects after a site migration: an ongoing QA planBuild a post-migration redirect monitoring routine that catches broken mappings, chains, old internal links and traffic losses long after launch.
- Hosting Migration SEO Checklist Without URL ChangesMoving hosts or adding a CDN without changing URLs? Protect crawl access, page signals and uptime before DNS cutover, then verify old and new infrastructure.
- HTTP to HTTPS migration SEO: redirect every URL and verify the moveA focused HTTP-to-HTTPS SEO migration plan: certificates, one-hop redirects, canonical and sitemap updates, mixed content and post-launch checks.
- Merge two websites SEO checklist: preserve the pages that matterConsolidate two sites with a content inventory, destination decisions, page-level redirects and combined-site performance monitoring.
- Staging site SEO: keep previews private without shipping noindexProtect a staging site, prevent preview URLs appearing in search, and remove accidental noindex or robots blocks before production launch.
- Subdomain to subfolder SEO migration: move URLs without losing pagesMove blog.example.com to example.com/blog/ with a URL map, direct redirects, updated signals and a practical post-launch verification plan.
- How to change your domain name without losing SEOA step-by-step domain change: both Search Console properties, a page-to-page redirect map, the Change of Address tool, what to update and what to expect.
- CMS migration SEO: how to switch platforms without losing trafficWhat a CMS or platform migration changes for SEO (URLs, templates, metadata, rendering, structured data) and how to compare old and new site around launch.
- Redirect chains: how to find and fix themWhat redirect chains and loops are, why they slow crawling and users down, and how to find and fix every one on your site in a single pass.
- Redirect mapping for a site migration: how to build and test itHow to build a page-to-page redirect map for a migration, which old URLs to include, how to handle pages with no equivalent, and how to test every redirect.
- Traffic dropped after a site migration? How to find and fix the causeNormal fluctuation or a real loss? How to tell after a migration, the mistakes that cause most post-migration drops, and how to find and fix them quickly.
Frequently asked questions
How long should I keep redirects after a site migration?
Google recommends keeping redirects for as long as possible, generally at least one year, so it can transfer signals to the new URLs.
Should migration redirects be 301 or 302?
Use permanent redirects, 301 or 308, from each old URL to its equivalent new URL. Google recommends server-side permanent redirects where possible.
Will rankings drop after a site migration?
Google says to expect temporary fluctuation. For medium-sized sites it can take a few weeks or more for Google to show the new URLs instead of the old ones.
How do I check that all old URLs redirect correctly?
Crawl the list of old URLs after launch. Every one should return a single permanent redirect to its new equivalent, which should return 200 and be indexable.
Do I need the Change of Address tool?
Only when you move from one domain or subdomain to another. For URL changes on the same domain, redirects, internal links and sitemaps do the work.