Website Migration SEO: The Checklist for Moving a Site Without Losing Rankings
Most of the traffic lost in a website migration is lost before launch day, in decisions nobody thought were SEO decisions: a developer who rebuilt the URL structure because the new platform preferred it, a designer who merged three service pages into one, a hosting move that quietly dropped the old redirects. The ranking drop shows up a fortnight later, after the agency has been paid and moved on.
This guide is the checklist we run on every migration, alongside a full technical SEO audit, whether we are moving a client’s site onto WordPress, taking over a site built elsewhere, or rebuilding one of our own. It covers what to do before, during and after the move, which migrations carry the most risk, how to build a redirect map, what to watch after launch, and what to do if rankings fall. If your project is a design refresh with no URL changes, start with our SEO checklist for a website redesign and come back here for the redirect and monitoring stages.
What counts as a website migration?
Definition: A website migration is any change that alters how search engines reach, crawl or understand your site: a new domain, a new platform or CMS, a new host, a change of URL structure, a move from HTTP to HTTPS, a merge of several sites into one, or a redesign that changes page content and internal links. The common thread is that Google has to re-learn the site, and anything it cannot match to what it knew before is treated as new or gone.
Not every migration carries the same risk. The risk comes from how much changes at once, and above all from whether URLs change.
| Migration type | Risk | Why | Key protection |
|---|---|---|---|
| Hosting or server move (same URLs) | Low | Nothing changes for Google if the site responds identically from the new server | Carry over redirects, robots.txt and SSL; check speed before and after |
| HTTP to HTTPS | Low to medium | Every URL changes by protocol, but the mapping is one to one | Site-wide 301s, update canonicals, internal links and sitemap; fix mixed content |
| Design refresh (same URLs) | Medium | Content, headings, internal links and templates change even though addresses do not | Compare crawls of old and new; keep word count, headings and links on priority pages |
| Platform or CMS change (same URLs) | Medium | New templates, new markup, new performance profile, often new default URL patterns | Force the old URL structure, audit the staging crawl against the old site line by line |
| URL restructure (same domain) | High | Every changed URL needs a redirect and loses some history during the move | Complete redirect map, one hop, no blanket redirects to the homepage |
| Domain change | Highest | Google has to transfer trust and links to a domain it has never seen | Redirect map, Change of Address in Search Console, keep the old domain and redirects for at least a year |
| Site merge or consolidation | Highest | Several histories collapsing into one; duplicate pages compete during the transition | Map each old page to the single best equivalent; consolidate rather than duplicate content |
Google’s own advice is to change one thing at a time: in its site move documentation, under general best practices, it says to plan your changes “one after the other, not everything at the same time”. A redesign, a new CMS and a new domain in a single launch is three migrations stacked on top of each other, and if traffic falls you will not know which one caused it. If you must do them together, treat the project as the highest-risk type on the table and plan for it.
Why migrations lose rankings
Every migration failure we have been asked to fix traced back to one of six causes. Knowing them tells you what the checklist is protecting against.
- Redirects missing, wrong or chained. Old URLs that return a 404, redirect to the homepage, or redirect through two or three hops lose the rankings and the backlinks those pages had. We cover this in our guide to whether 404s are bad for SEO.
- Noindex or robots.txt rules carried over from staging. The single most common launch-day mistake: the new site goes live still telling Google not to index it. Our guide to indexing explains the signals involved.
- Content thinned or merged. Pages that ranked because they answered a question in depth get cut to a paragraph in the new design, or three pages become one and two sets of rankings disappear.
- Internal links rebuilt badly. New navigation and templates drop the contextual links that told Google which pages mattered. See what internal links do for SEO.
- Technical signals lost. Canonical tags, structured data, hreflang, title tags and meta descriptions do not survive a platform change unless someone carries them across deliberately.
- Performance regressions. A new build on heavier templates or slower hosting can push Core Web Vitals from passing to failing. Our guide to how hosting affects SEO covers the hosting side.
The website migration SEO checklist
Forty-four checks in four stages. Work through them in order; the stages build on each other, and the benchmark in stage one is what makes stage four possible.
Stage 1: Benchmark and plan (four to eight weeks before launch)
- Define the scope in writing: what is changing (domain, platform, host, URLs, design, content) and what is not. This decides the risk level and the size of the job.
- Crawl the current site in full and keep the export. This is your record of every URL, title, description, heading, canonical, status code, word count and internal link count as they were.
- Export every URL Google knows about from Search Console (Pages report, including excluded URLs) and from your XML sitemap. A crawl finds what is linked; Search Console finds what is indexed, which is often more.
- Export twelve months of Search Console performance data by page and by query. Keep clicks, impressions, average position and CTR; you will compare against these after launch.
- Record rankings for your priority keywords with a rank tracker, by URL. Daily tracking from here until 90 days after launch.
- List your priority pages: the twenty to fifty URLs that produce most of your organic traffic, leads or revenue, and every page with meaningful backlinks. These get manual review at every stage.
- Export your backlink profile by target URL. Pages with inbound links must redirect correctly or the links are wasted; our link building guide explains why they matter.
- Benchmark Core Web Vitals and page speed for templates, not just the homepage: a service page, a blog post, a category page, a product page.
- Record the current indexed page count (Search Console Pages report) and the number of valid URLs in the sitemap.
- Note everything that depends on current URLs: Google Business Profile links, ad campaigns, email templates, social profiles, printed material, third-party listings and directory entries.
- Confirm access to Search Console, Analytics, the domain registrar, DNS, hosting and the new platform for everyone who needs it, before the week of launch.
- Set the launch window. Tuesday to Thursday morning, UK time, outside your peak season, with the developer, the SEO and the person who can roll back all available for the following 48 hours. Never a Friday.
Stage 2: Build the redirect map and audit the new site (two to four weeks before launch)
- Build the redirect map: one row per old URL, the new URL it maps to, and the reason. Every URL from steps 2 and 3 must be on it, including images, PDFs and old redirected URLs that still receive traffic.
- Map each page to its closest equivalent, not to the homepage. Where a page has no equivalent, map it to the parent category or the nearest page on the same topic. A blanket redirect of everything to the homepage tells Google the pages are gone.
- Keep URLs the same wherever you can. If the new platform allows the old structure, use it; the fewer rows in the redirect map, the less there is to lose.
- Check existing redirects. Old redirects from previous migrations must point directly to the final new URL, not chain through the intermediate one. One hop only.
- Crawl the staging site and compare it line by line with the benchmark crawl: titles, descriptions, H1s, canonicals, word count, internal links out, structured data. Every difference on a priority page needs a reason.
- Check that content has not been thinned. If a page that ranked for a term has lost its headings, tables or half its words in the new template, restore them before launch, not after.
- Rebuild internal links deliberately: navigation, footer, contextual links in body copy, related content. The links that pointed at your priority pages must still point at them.
- Carry over canonical tags, structured data, hreflang (if you have international versions), meta robots and pagination handling. Our guide to canonical tags covers the first of these.
- Confirm staging is blocked from indexing (password or IP restriction, not just a noindex tag) and that the block is documented so it can be removed at launch.
- Generate the new XML sitemap on staging and check it lists only final, indexable, 200-status URLs. See our guide to sitemaps.
- Test the redirect map on staging or a test server: every old URL resolves to its mapped new URL with a 301, in one hop, with no loops.
- Confirm analytics and Search Console tracking fire on the new templates, with the same property and goals, so post-launch data is comparable.
- Test speed on the new templates against the benchmark. A new design that is slower than the old one is a regression to fix before launch.
- For a domain change, verify the new domain in Search Console now and check its history (previous owners, penalties, spam) before you commit to it.
- Write the rollback plan: how to put the old site back, who does it, and the trigger (for example, a redirect failure affecting priority pages that cannot be fixed within two hours).
Stage 3: Launch day
- Lower the DNS time-to-live a day before a domain or host change so the switch propagates in minutes rather than hours.
- Remove the staging block and the noindex rules the moment the new site is live, and check robots.txt on the live domain allows crawling. Then check again from a different device.
- Test the redirects live: your priority pages first, then a sample of every section, then the full redirect map by crawling the old URL list. Fix anything that returns a 404, 302 or a chain.
- Confirm SSL is valid on the new domain and, for a domain change, on the old one, which must keep serving redirects for at least a year.
- Submit the new XML sitemap in Search Console. For a domain change, also use the Change of Address tool; Google says you only need it when moving from one domain or subdomain to another, not for HTTPS or same-domain changes.
- Use URL Inspection to request indexing for your priority pages.
- Crawl the live site in full and compare with the staging crawl. Launch processes often reintroduce problems that were fixed on staging.
- Check analytics is recording live traffic and conversions within the first hour.
- Update the URLs you listed in step 10: Google Business Profile, ads, email, social, listings.
Stage 4: Monitor and fix (the first 90 days)
- Check Search Console daily for the first two weeks: Pages report for indexing errors, crawl stats for spikes in 404s or server errors, and the sitemap status.
- Track rankings daily against the benchmark. Expect movement for two to six weeks; investigate any priority term that has not recovered within three weeks.
- Compare organic traffic by page against the same period before launch, and against the same period last year to separate migration effects from seasonality.
- Watch the indexed page count. It should move towards the sitemap count; a count that keeps climbing past it means old URLs or parameters are being indexed, and a count that stalls well below it means pages are being excluded.
- Recrawl the redirect map monthly for the first three months and fix any redirect that has broken, chained or started returning the wrong status.
- Keep the old domain registered and redirecting for at least a year. Google’s site move guidance says to keep the redirects for as long as possible, generally at least a year, and that a small to medium site can take a few weeks for most pages to move.
- Review backlinks to old URLs after a month. Links to pages that now redirect are fine; links to pages that 404 are the ones to fix, by adding the missing redirect or asking the linking site to update.
- Hold a 30-day and a 90-day review against the stage-one benchmark and write down what moved, what recovered and what did not. The 90-day number is the one that tells you whether the migration worked.
How to build a redirect map
The redirect map is the document the whole migration rests on, so it is worth being precise about it. It is a spreadsheet with one row per old URL and, at minimum, the columns below. Build it from the full crawl plus the Search Console and sitemap exports, not from the navigation menu, because the menu misses old blog posts, tag pages, PDFs and anything that was quietly delisted years ago but still ranks.
| Column | What goes in it | Why |
|---|---|---|
| Old URL | The exact current address, including trailing slash and protocol | Redirects match exactly; a missing slash is a different URL |
| Status | The old URL’s current response (200, 301, 404) | Tells you which rows are live pages and which are already redirects to fold into one hop |
| New URL | The single page that best replaces it | One destination per row; never a list, never the homepage by default |
| Match type | Exact, closest equivalent, parent category, or retired | Flags the rows that need a human decision and the ones that will lose some relevance |
| Priority | Yes if the page is in your top traffic, revenue or backlink list | These rows get tested by hand on staging and again on launch day |
| Traffic (12 months) | Clicks from Search Console | Sorts the map by what matters and shows the cost of any row you get wrong |
| Backlinks | Referring domains to the old URL | A page with links must redirect, even if it has no traffic |
| Tested | Date and result on staging, then live | Nothing is done until it has been tested twice |
Three rules apply to every row. Use 301 (permanent) redirects, not 302 (temporary), because a 302 tells Google the old URL is coming back. Redirect to the final destination in one hop, because every hop in a chain is a chance for a redirect to break and a delay for the crawler. And never redirect everything to the homepage: Google treats an irrelevant redirect much like a page that has gone, and you lose the rankings either way. Google is clear that permanent redirects do not lose PageRank; what loses rankings is a redirect to the wrong page, or no redirect at all.
Migrating a WordPress site, or moving onto WordPress
Most of the migrations we run involve WordPress at one end or both, so a few points are specific to it.
- Permalinks. The new site’s permalink settings decide whether old URLs survive. Match the old structure exactly (including trailing slashes and category bases) before you import content, not after.
- Redirect management. Redirects can live in the SEO plugin, a dedicated redirect plugin, or the server configuration. Server-level redirects are faster and survive plugin changes; plugin redirects are easier to manage and audit. Pick one, document it, and do not run both.
- Imported content. Importers bring across posts and pages but routinely drop custom fields, featured images, structured data settings and per-page titles and descriptions. Check the staging crawl against the benchmark for exactly these.
- Page builders. Moving from one builder to another rebuilds every page’s markup: headings become divs, alt text disappears, links in builder modules go missing. Audit the priority pages by hand.
- Hosting moves. A WordPress site moving host with the same domain and URLs is the lowest-risk migration on the table, provided the .htaccess or server rules (redirects, caching, security headers) move with it and the site is not briefly served from both servers with different content.
- Staging to live. Search and replace the staging domain in the database on launch, then check canonical tags and the sitemap, which are the two places a staging URL most often survives.
Every build in our web design packages includes migration from your existing site with the redirect map and the checks above; our WordPress web design page covers what is included for WordPress specifically. If the site is already live and the problem is technical debt rather than a move, our technical SEO services page covers the audit-and-fix work.
Website migrations and AI search
GEO Note: AI Overviews and assistants such as ChatGPT and Perplexity cite pages they have already read and trusted. A migration that changes URLs, strips structured data or thins content can drop a site out of AI answers even where its Google rankings recover, because the citation points at a URL that no longer exists or a passage that no longer reads the same way. Treat your most-cited pages as priority pages: keep their URLs where possible, keep the passages and structured data that earn the citations, and check the answers for your key queries before and after launch.
Before launch, record which of your pages are cited in AI Overviews and in the assistants your customers use, for the queries that matter. After launch, run the same queries at two weeks and at 90 days. Our guide to generative engine optimisation explains what earns those citations in the first place, and how to get your website cited in AI covers the on-page work.
What to do if rankings drop after a migration
Some movement in the first few weeks is normal and is not a reason to roll back. A sustained drop on priority pages is. Work through the causes in order; the first three account for most cases.
- Indexing directives. Fetch the live page and look for a noindex tag or a robots.txt disallow. Remove it, request indexing, and expect recovery within days.
- Redirects for the pages that dropped. A 404, a 302, a chain or a redirect to the wrong page explains most individual losses. Fix the redirect; recovery follows the next crawl.
- The page itself against the benchmark crawl: title, H1, word count, headings, internal links in, structured data. Restore what is missing.
- Sitemap, canonical tags and speed: staging URLs or the wrong protocol in the first two, or a Core Web Vitals regression in the third, which produces a slower, broader decline rather than a cliff.
- If everything checks out and the drop persists past six weeks, the site changed more than the plan admitted: merged pages, lost internal links, or a redesign that cut the depth of content. Restore what the old site had, page by page, starting with the highest-value losses.
Our guide to how to measure SEO results covers the reporting side, so the 30-day and 90-day reviews compare like with like.
Frequently asked questions
What is website migration SEO?
Website migration SEO is the set of checks and changes that protect a site’s search visibility when it moves domain, platform or host, changes its URL structure, or is redesigned. It covers benchmarking the current site, mapping every old URL to a new one with a permanent redirect, auditing the new site on staging before launch, and monitoring indexing, rankings and traffic after launch so problems are caught and fixed quickly.
How long does a website migration take?
The technical switch can take an afternoon. The SEO work around it takes four to eight weeks before launch for a typical small business site, longer for large or complex sites, plus 90 days of monitoring afterwards. Google says a small to medium site can take a few weeks for most pages to move in its index, and larger sites take longer.
Will I lose rankings when I migrate my website?
Some fluctuation during the move is normal and Google says as much in its site move guidance. A well-planned migration with a complete redirect map and no content loss should hold its rankings and often improves them, because the new site is usually faster and better structured. The losses come from missing redirects, noindex tags left on, thinned content and broken internal links, all of which the checklist above is designed to prevent.
Do 301 redirects lose link equity?
No. Google states that 301 and other permanent redirects do not cause a loss in PageRank. What loses value is redirecting to an irrelevant page, redirecting through several hops, or using a temporary 302 for a permanent move.
How long should I keep redirects in place after a migration?
Google’s guidance is to keep them for as long as possible, and generally for at least a year. In practice we recommend keeping them permanently where the old domain is still registered, because backlinks and bookmarks to old URLs keep arriving for years.
Do I need Google’s Change of Address tool?
Only when moving from one domain or subdomain to another. Moving from HTTP to HTTPS, changing from www to non-www, or changing URLs within the same domain does not need it; the redirects and a new sitemap are enough.
Can I redesign and migrate at the same time?
You can, but Google advises changing one thing at a time, and so do we. Combining a redesign with a domain or platform change makes any traffic drop impossible to diagnose. If the timing forces it, treat the project as the highest-risk type, keep URLs identical wherever possible, and hold the content on priority pages unchanged until the migration has settled.