The SEO Site Migration Checklist (Don’t Lose Rankings)

Site migrations are the single most dangerous project in SEO. A redesign, a platform change, a domain move, or a restructure can wipe out years of accumulated rankings and traffic overnight if it is handled carelessly — and the internet is littered with businesses that lost half their organic revenue the week they "just launched the new site." The tragedy is that almost all of this loss is preventable with disciplined planning.

The word "migration" covers several kinds of change, each with its own risks: moving to a new domain, switching platforms or CMS, restructuring URLs, redesigning templates, consolidating multiple sites, or moving to HTTPS. What they share is that they alter the URLs, structure, or content search engines have already indexed and ranked — and any break in the mapping between old and new is where rankings leak away.

This guide is a practical, end-to-end checklist: how to plan a migration, map redirects correctly, QA before launch, execute on launch day, and monitor afterwards — so you carry your hard-won equity across intact rather than watching it evaporate.

Plan before you touch anything

The most expensive migration mistakes are made before a single URL changes, in the decision to treat SEO as an afterthought. SEO must be involved from the very start of a migration project, not consulted the week before launch, because the structure, URLs, and content decisions made early determine how much equity survives.

Planning begins with clarity about scope: exactly what is changing — domain, platform, URLs, templates, content — because each change adds risk and needs its own handling. It continues with a full crawl and inventory of the existing site, capturing every indexed URL, its rankings, traffic, and links, so nothing is lost or forgotten in the transition. And it includes a realistic timeline that treats redirect mapping and QA as major workstreams rather than launch-week checkboxes.

Crucially, plan to migrate quality, not just move pages. A migration is an ideal moment to apply content pruning — but deliberately, with equity-preserving redirects, not by silently dropping pages. Deciding in advance what to keep, consolidate, and retire prevents the panic decisions that cause losses.

Benchmark everything first

You cannot tell whether a migration succeeded — or diagnose what went wrong — without a clear picture of where you started. Comprehensive benchmarking before launch is your safety net, and skipping it means flying blind if anything drops.

• Full URL inventory. Crawl the site and export every indexable URL.
• Rankings. Record current positions for your important keywords.
• Traffic and conversions. Capture organic traffic and conversion baselines by page and section.
• Backlinks. Export your backlink profile so you know which URLs must not break.
• Indexing and technical state. Note indexed page counts, Core Web Vitals, and any existing issues.

Store these benchmarks safely before anything changes. If traffic dips after launch, they let you pinpoint exactly which pages and keywords are affected and how badly — turning a vague panic into a targeted fix.

The redirect map: the heart of a migration

If a migration has a single make-or-break element, it is the redirect map. When URLs change, every old URL must 301-redirect to its correct new equivalent, so that users, search engines, and accumulated link equity all follow the page to its new home. A missing, wrong, or broken redirect is precisely where rankings are lost.

Build the map as a complete, one-to-one mapping from every old URL to its most relevant new URL — not a lazy blanket redirect of everything to the homepage, which Google treats as a soft 404 and which discards the equity you are trying to preserve. Where a page is being retired rather than replaced, redirect it to the closest relevant surviving page. Use permanent 301 redirects, and avoid redirect chains, which dilute equity and slow crawling.

This is painstaking work, especially for large sites, but it is the work that determines whether the migration succeeds. Every hour spent getting the redirect map complete and correct is an hour of insurance against catastrophic loss — and there is no shortcut that does not cost you rankings.

Pre-launch QA on staging

Launch day is far too late to discover problems, so thorough QA on a staging environment is essential. The goal is to catch every issue while it is still cheap to fix, before real users and crawlers ever see the new site.

Verify that the redirect map works correctly on staging, that important pages retain their titles, meta, headings, and content, and that structured data, canonical tags, and internal links are all intact and pointing to the right places. Confirm the new site is crawlable and — critically — that staging itself is blocked from indexing so it does not create duplicate content. Check that the XML sitemap reflects the new URLs and that analytics and Search Console tracking are ready.

A frequent, disastrous oversight deserves its own mention: a stray "noindex" or a blanket robots.txt "Disallow" left over from staging, shipped to production, can deindex the entire site overnight. Make verifying indexability on the live site the first thing you check the moment you launch.

Launch day execution

With planning and QA done, launch day becomes a controlled sequence rather than a leap of faith. The priority is to get the new site live correctly and verify the highest-risk elements immediately.

1. Deploy the new site and immediately confirm it is indexable — no stray noindex or blocking robots.txt.
2. Verify the redirects are live and resolving correctly on production, spot-checking top pages.
3. Submit the updated XML sitemap in Search Console to speed rediscovery.
4. Confirm analytics and Search Console are tracking the new site.
5. Do a rapid crawl of the live site to catch broken links, errors, and missed redirects.
6. Monitor server logs and error rates for crawl problems as bots hit the new URLs.

Have the team on standby to fix issues fast. The first hours and days are when problems surface, and the speed of your response directly affects how much, if anything, you lose. Calm, prepared execution here is the payoff for all the earlier planning.

Post-launch monitoring and recovery

A migration is not finished at launch; the critical monitoring period runs for weeks afterward as search engines recrawl, reprocess, and re-rank the new site. Expect some short-term fluctuation as this happens — it is normal for rankings to wobble for a week or two — but watch closely to distinguish normal settling from a genuine problem.

Track your benchmarks against live performance: are the right pages being indexed, are redirects all resolving, are rankings and traffic recovering to previous levels or dropping and staying down? Watch Search Console for crawl errors, coverage issues, and manual actions, and keep crawling the site to catch problems that emerge as more of it is reprocessed. If a section drops and does not recover, the benchmarks tell you exactly where to look.

Most migration losses that become permanent do so because problems went undetected during this window and were only noticed once the damage was entrenched. Intensive monitoring, and a readiness to fix redirect, indexing, and crawl issues immediately, is what turns a risky migration into a successful one. Fold the site into your ongoing technical SEO rhythm once it has stabilised.

Special cases: domain moves, HTTPS, and consolidations

Some migration types carry extra risk and deserve specific handling beyond the general checklist. A domain move — changing the actual domain name — is among the riskiest, because you are asking search engines to transfer all the authority associated with one domain to another. In addition to complete redirects, use Search Console's Change of Address tool to signal the move explicitly, keep the old domain's redirects live for an extended period (ideally a year or more), and expect a temporary dip as authority transfers.

Moving from HTTP to HTTPS is a migration many teams underestimate because it feels minor, but every URL changes and must be redirected, canonical tags and internal links must be updated to the secure versions, and mixed-content issues must be resolved. Done properly it is low-risk and even a mild positive signal; done carelessly it can duplicate your entire site across two protocols.

Consolidating several sites into one is the most complex case of all, because you are merging multiple redirect maps, resolving overlapping content, and combining distinct authority profiles at once. It magnifies every risk in this guide, so it demands the most rigorous planning, the most careful content consolidation, and the longest monitoring window. Whatever the type, the underlying principle is constant: preserve the mapping between what search engines knew and what they will find, and verify relentlessly.

How Web of Picasso approaches site migrations

Web of Picasso is an unconventional growth agency built on a single belief: the best returns come from demand your competitors are not fighting for. Instead of bidding up the same crowded auctions and copying the same playbooks, we look for the under-served intent — the questions, channels, and audiences everyone else has overlooked — and we help you own them before they become obvious. That philosophy shapes everything we do, including how we approach site migrations.

In practice, our site migrations work always starts with research rather than tactics. We map the real questions your buyers are asking, audit where you currently appear and — more importantly — where you are invisible, and then prioritise the moves with the highest ratio of impact to effort. From there we execute deliberately and measure relentlessly, so every dollar of budget is tied to an outcome you can see rather than a vanity metric that flatters a slide.

If you want to understand what that looks like in the real world, our case studies show the kind of compounding, durable growth this approach produces — and our team is happy to walk you through how it would apply to your specific situation.

We apply this in every market we serve. If you are US-based, our SEO, AEO, and CBD services by US city map the strategy to your local industries and competitors; if you are in the UK, our UK location pages do the same for British markets.

Frequently asked questions

What is the most important part of an SEO site migration?

The redirect map. Every old URL must 301-redirect to its correct new equivalent so users, search engines, and link equity follow each page to its new home. A complete, one-to-one redirect map is the single biggest factor in whether a migration preserves rankings or loses them.

Why do sites lose rankings after a redesign?

Usually because of broken or missing redirects, changed URLs without proper mapping, lost content or metadata, a stray noindex or blocking robots.txt shipped from staging, or a blanket redirect to the homepage. Nearly all of these are preventable with planning, benchmarking, and pre-launch QA.

Should I redirect old pages to the homepage?

No. Redirecting many old URLs to the homepage is treated by Google as a soft 404 and discards the equity of those pages. Redirect each old URL to its most relevant new equivalent, or to the closest relevant surviving page if it is being retired.

How long does it take to recover after a migration?

Expect some fluctuation for one to two weeks as search engines recrawl and reprocess the site. A well-executed migration typically settles back to previous performance within a few weeks. If a drop persists beyond that, it usually indicates an unresolved redirect, indexing, or crawl issue to diagnose against your benchmarks.

Can I improve SEO during a migration?

Yes, carefully. A migration is a good moment to prune low-value content and improve structure — but do it deliberately, with equity-preserving redirects for anything retired, never by silently dropping pages. Combining thoughtful improvements with disciplined redirect mapping lets you emerge stronger rather than weaker.

Further reading

• Google Search Central — site moves with URL changes
• Ahrefs blog — site migration guide
• Moz — website migration best practices

Migrate without losing your rankings

A migration is the riskiest project in SEO — and the most preventable disaster. Our technical SEO team plans and QAs migrations end to end — talk to us before you launch.