A website migration is any major change to a site’s platform, structure, URLs, domain or design that can affect how search engines find and rank it. Handled well, website migration SEO protects years of rankings and traffic. Handled badly, it can wipe out a large share of organic revenue overnight.
This checklist walks through every stage of a large-site migration, from planning and redirect mapping to launch day and the first 90 days, so your new site keeps the visibility your old one earned. Before you start, an enterprise SEO audit of the current site is strongly recommended.

Types of Website Migration
| Migration type | What changes | SEO risk |
|---|---|---|
| Platform or CMS change | The system that builds and serves pages | High: templates, URLs and code often change |
| Domain change | The website address, such as a rebrand or merger | High: all signals must move to a new domain |
| URL structure change | Folders, slugs or parameters | High: every changed URL needs a redirect |
| Site redesign | Templates, navigation, content and layout | Medium to high: content and internal links can be lost |
| HTTP to HTTPS | Protocol only | Low if redirects and canonicals are correct |
| Content consolidation | Merging or removing pages and sections | Medium: relevance and links must be preserved |
Many enterprise projects combine several of these at once. Each extra change adds risk, so where possible, avoid changing the domain, platform and URL structure in the same release.
Why Migrations Lose Traffic
- Missing or incorrect redirects send users and search engines to error pages.
- Content removed or thinned during a redesign weakens relevance.
- Internal links changed or lost, leaving important pages buried.
- Staging settings left live, such as noindex tags or a robots.txt block.
- Slower pages or JavaScript rendering problems on the new platform.
- Lost structured data, titles or meta descriptions in new templates.
- Tracking not migrated, so problems go unnoticed.
Phase 1: Planning (8 to 12 Weeks Before Launch)
- Involve SEO at the start of the project, not the week before launch.
- Agree the scope: which URLs, templates and content will change.
- Choose a low-traffic launch window and avoid your busiest season.
- Set success measures: organic sessions, rankings, conversions and indexed pages.
- Agree who owns redirects, testing, sign-off and post-launch fixes.
Phase 2: Benchmark the Current Site
- Crawl the full site and save the list of every URL, title, H1, canonical and status code.
- Export the top pages by organic traffic, conversions and revenue from analytics.
- Export pages with backlinks from your backlink tool and Search Console.
- Record current rankings for priority keywords and AI visibility for key prompts.
- Save XML sitemaps, robots.txt and structured data examples for each template.
- Record Core Web Vitals by template.

Phase 3: URL Mapping and Redirects
The redirect map is the most important document in any migration. It lists every old URL and the most relevant new URL it should go to.
- Map every indexable URL, every URL with backlinks and every URL with traffic, not just the top pages.
- Use permanent 301 or 308 redirects from each old URL to the closest equivalent new URL.
- Avoid redirecting large numbers of pages to the homepage; Google often treats these as soft 404s.
- Redirect old URLs in one hop. Remove existing redirect chains while you are at it.
- Use pattern rules for large sections, then test samples carefully.
- Keep images, PDFs and other files in the map if they receive traffic or links.
Google’s John Mueller has advised keeping redirects in place for at least one year so search engines see them several times (Search Engine Journal). For valuable URLs with backlinks, keep them in place indefinitely.
Phase 4: Test on Staging
- Block staging from search engines with password protection, not just noindex.
- Crawl staging and compare titles, H1s, canonicals, content and internal links with the benchmark.
- Test the redirect map against staging and confirm every old URL returns one 301 to a 200 page.
- Check rendered HTML to make sure content and links are visible without user interaction.
- Validate structured data, hreflang and XML sitemaps on new templates.
- Test Core Web Vitals and mobile layouts for each template.
- Confirm analytics, tag manager and conversion tracking are installed.
Phase 5: Launch Day
- Remove staging restrictions: password protection, noindex tags and robots.txt blocks.
- Switch on redirects and test a sample of top URLs immediately.
- Submit new XML sitemaps in Search Console. For domain changes, keep the old sitemap briefly so Google discovers the redirects.
- For domain moves, verify both properties and use the Change of Address tool in Search Console.
- Update key external links you control, such as social profiles, Google Business Profiles and partner sites.
- Crawl the live site to catch broken links, redirect errors and missing tags.
- Check analytics is recording traffic and conversions.
Phase 6: Monitor for 90 Days
Some ranking movement after a large migration is normal while search engines process the changes. What matters is spotting real problems early.
| When | What to check |
|---|---|
| Daily for the first week | Search Console coverage and crawl errors, 404s, server errors, organic traffic to top pages |
| Weekly for the first month | Rankings, indexed pages, redirect hits in logs, conversions, Core Web Vitals |
| Monthly for three months | Organic traffic and revenue against benchmark, backlinks, AI visibility, remaining old URLs in the index |

Migrating International and Multi-Location Websites
Sites with several countries, languages or branches need extra checks, because errors repeat across every market:
- Update hreflang tags so every language and country version points to the new URLs, and confirm they are reciprocal.
- Keep the same country targeting structure (folders, subdomains or country domains) unless there is a strong reason to change it.
- Redirect each local page to its local equivalent, never to a global page.
- Update website links in every Google Business Profile once location pages move.
- Stagger launches by market if the release is very large, starting with a lower-risk market.
Protecting AI Search Visibility During a Migration
AI answers in Google AI Overviews, ChatGPT and other tools often cite specific pages. When those URLs change, citations can disappear until the new pages are crawled and trusted. To limit the impact, keep answer-first content, FAQs and structured data on the new templates, make sure AI search crawlers are not blocked by new firewall or CDN rules, and track your most important prompts before and after launch. Our guide to generative engine optimisation explains what AI systems look for.
Website Migration SEO Checklist: Quick Reference
- SEO involved from the start, with a clear scope and owners.
- Full crawl, analytics, backlink and ranking benchmarks saved.
- Every valuable old URL mapped to its closest new equivalent.
- One-hop 301 redirects tested on staging.
- Titles, headings, content, internal links and structured data preserved on new templates.
- Staging protected by password, with all blocks removed at launch.
- New XML sitemaps submitted, and Change of Address used for domain moves.
- Analytics and conversion tracking confirmed on the live site.
- Daily, weekly and monthly monitoring planned for 90 days.
- Redirects kept for at least a year, and permanently for valuable URLs.
Common Migration Mistakes to Avoid
- Leaving the robots.txt block or noindex tags from staging on the live site.
- Redirecting everything to the homepage.
- Changing domain, platform and URLs in one release without extra testing.
- Removing pages with backlinks without redirecting them.
- Launching on a Friday or just before peak season.
- Removing redirects after a few months.
- Not updating internal links, so users and bots hit redirects on every click.
What to Do If Traffic Drops After a Migration
- Compare the drop by section and template to find where it is concentrated.
- Check robots.txt, noindex tags and canonicals on affected pages.
- Test redirects for the URLs that lost the most traffic.
- Compare old and new content, titles and internal links for those pages.
- Review Search Console for crawl errors, indexing changes and manual actions.
- Fix, resubmit sitemaps and monitor recovery, which can take several weeks.
Get Expert Help With Your Migration
A migration is one of the highest-risk moments for an enterprise website. Our technical SEO team plans redirect maps, tests staging sites, supports launch day and monitors results, as part of our wider enterprise SEO services. To plan your budget, see our guide to enterprise SEO cost in the UK.
We support businesses across the UK, including Birmingham, Leeds, Cardiff and Newcastle, and AI search visibility is part of every plan. Read our guide to generative engine optimisation to see how.
Planning a migration? Book a free migration review before you launch, and we will show you the biggest risks to fix first.
Need expert help with your migration? Our website migration SEO services cover planning, redirect mapping, staging tests, launch support and post-launch monitoring. Moving a WordPress site? See our WordPress SEO services.
Frequently Asked Questions
What is website migration SEO?
Website migration SEO is the planning, testing and monitoring needed to protect search rankings and traffic when a site changes its platform, domain, URL structure or design.
How long does it take to recover rankings after a migration?
Well-planned migrations often settle within a few weeks. Large or complex moves can take several months, especially domain changes, while search engines process redirects and re-index pages.
How long should I keep 301 redirects after a migration?
Google has advised keeping redirects for at least one year. Redirects for URLs with valuable backlinks or traffic should usually be kept permanently.
Should I redirect old pages to the homepage?
No. Redirect each old URL to the most relevant new page. Mass redirects to the homepage are often treated as soft 404s and lose the value of the original pages.
Can I change my domain and platform at the same time?
It is possible, but each change adds risk. Where you can, split them into separate releases, or allow extra time for testing and monitoring.
When should SEO be involved in a website migration?
From the start of the project, ideally two to three months before launch, so URL structures, templates and redirects are planned with search in mind.









