Migrations go wrong when nobody recorded what the old site did. Most of this checklist is about writing that down before anything changes.
Quick answer
Before launch: crawl the live site and save a baseline, decide which URLs change, build and test a redirect map, check the staging build for blocking rules, confirm canonicals, titles and internal links match the plan, test tracking, and prepare the launch-day checks. Do not leave SEO to the week of launch.
1. Record the baseline
Crawl the live site and save a record of every URL: status, title, meta description, H1, canonical, indexability and schema. Add Search Console and analytics data so you know which pages carry traffic and links.
When I did this for my own site, the crawl found 101 indexable URLs against about 40 I had expected. Without it I would have planned a migration of the wrong size.
2. Decide what changes, then keep the rest
Every change adds risk. Keep URLs, titles, headings and body content the same wherever you can, and change them in a separate step after the move has settled. Where URLs must change, map each old URL to its closest equivalent. See how to build a redirect map.
3. Check what actually runs on the old site
Do not rely on the source code or documentation alone. On my own migration, the theme code disabled a sitemap and redirected a duplicate URL, but the live site did neither. Settings such as analytics IDs, security headers and form handling were all in theme files and would not have been in a content export. List what the old site does, then check it against the live version.
4. Check the staging build
Staging is where most launch-day mistakes are born.
- Noindex tags or robots.txt blocks that should be removed on launch
- Password protection or IP restrictions
- Canonical tags pointing at the staging domain
- Absolute links, sitemaps or schema URLs using the staging domain
- Duplicate canonical tags, or missing Open Graph and social tags
- Test and placeholder content
Crawl staging the way Google would, and compare the result with the baseline crawl.
5. Test the redirects before launch
- Run the old URL list through the new redirect rules
- Check each ends in one hop at a page that returns 200
- Confirm the www and non-www versions, HTTP and HTTPS, and trailing slash variants
- Spot-check high-traffic and high-backlink URLs by hand
6. Prepare tracking and sitemaps
- Analytics and conversion tracking fire on the new site
- Search Console access is in place for the right property
- A new XML sitemap is ready, and the old one is not left live alongside it
- robots.txt references the correct sitemap
7. Launch-day checks
On the day, check the following in order.
- Live robots.txt allows crawling and has no staging rules
- Key pages have no noindex and are self-canonical
- Redirects work on the live domain
- Analytics is recording
- The sitemap is reachable and lists only final URLs
- Crawl the live site and compare it with the baseline
8. Plan the after
Keep a short list of what to monitor in the first days and weeks. See what to monitor after a website migration and common migration mistakes.
When to get support
If you want a second pair of eyes before the URLs change, SEO migration support covers the baseline crawl, redirect map, staging review and launch-day checks.
FAQ
When should SEO be involved in a migration?
As early as possible, ideally before URL structures, templates and content decisions are final.
Do all old URLs need redirects?
Any valuable or accessible old URL should have a relevant redirect. Prioritise URLs with traffic, links, rankings or business value.
Should I migrate and redesign at the same time?
It is safer not to. Each extra change makes it harder to tell what caused a movement in rankings.