How do you migrate a website without losing your SEO rankings?

The short answer: you migrate a website without losing rankings by benchmarking the current site, mapping every old URL to a new one with 301 redirects, building on a staging site search engines can't see, carrying over the titles, headings and content that already rank, testing everything before launch, and monitoring indexing closely for the first eight weeks. Rankings fall when Google can no longer find, crawl or trust pages it already ranked, and almost every cause is preventable.

A website redesign or platform change is the riskiest moment in a site's SEO life. A careless relaunch can undo years of progress in an afternoon, usually because of missing redirects or a "noindex" tag left over from staging. This guide walks through the full process in order, with the checklists, URL rules and monitoring plan you need, and it covers the common cases: a redesign, a move to a new platform such as WordPress, a URL structure change, a domain change and an HTTPS switch.

Key takeaways

• The redirect map is the most important document in any migration: one old URL to one relevant new URL.
• Never redirect everything to the homepage.
• Staging sites must be blocked from search engines, and the block must be removed on launch day.
• Some movement in rankings for a few weeks after launch is normal; a sustained drop means something fixable is wrong.
• Keep redirects in place for at least a year.

What counts as an SEO website migration?

An SEO website migration is any change that alters how search engines reach, read or identify your pages: a new design, a new platform, new URLs, a new domain or a switch to HTTPS. The more of those change at once, the higher the risk, so it helps to know which type you're doing.

Why do rankings drop after a website migration?

Rankings drop when search engines can't find the old pages, can't crawl the new ones, or no longer see the signals that earned the ranking. The usual causes are:

• Missing or wrong redirects, so old URLs return 404 errors and lose their accumulated authority.
• A leftover noindex tag or robots.txt block carried from the staging site to the live site.
• Changed or removed content: rewritten titles, dropped headings, or pages deleted because they "looked old".
• Broken internal links and a changed navigation that buries important pages.
• A slower site, often from a heavy theme or page builder.
• Lost structured data and tracking, so you can't see or protect what was working.

Each of these is checked in the steps below.

Step 1: Benchmark the current site before changing anything

You can't protect what you haven't measured. Before any work starts, capture the current state so you can compare after launch:

• Crawl the whole site with a crawler (Screaming Frog is a common one) and export every URL with its status code, title, H1, canonical and indexability.
• Export your top pages by organic traffic and by conversions from Analytics and Search Console. These are the pages you must not lose.
• Record current rankings for your priority keywords.
• Export backlinks pointing to your key pages, since those URLs need especially careful redirects.
• Note page speed for the main templates.
• Keep a full backup of the old site.

Step 2: Map every old URL to a new URL

The redirect map is the core deliverable of a migration. For every URL on the old site that has traffic, links or rankings, decide which new URL replaces it, then set up a 301 (permanent) redirect from old to new. Use one-to-one matches by topic wherever possible.

Follow these rules: avoid redirect chains (old to old2 to new), redirect to the most relevant page rather than the homepage, and include image and PDF URLs that have backlinks. Sending every old URL to the homepage tells Google the old content no longer exists and is often treated as a soft 404.

Step 3: Build on a staging site that search engines cannot see

Develop and test the new site on a staging environment that isn't publicly indexable. Password protection is the safest option; a noindex tag helps, but a robots.txt block on its own does not reliably keep known URLs out of search results. The most common launch mistake is copying the staging site live with the block still in place, so add "remove staging block" to your launch checklist now and check it twice.

Step 4: Carry over what already ranks

A migration is not the moment to rewrite everything. For pages that rank and convert, keep the elements search engines already associate with them:

• Page titles, meta descriptions and H1s, unless you have a clear reason to improve them.
• Body content, headings and internal links to and from the page.
• Structured data, image alt text and canonical logic.
• The page's position in the site hierarchy and its prominence in the navigation.

Improve pages in a second phase, once the migration has settled, so that if something changes you know which change caused it.

Step 5: Design SEO-friendly URLs

If your URLs are changing, this is the time to get them right. SEO-friendly URLs are short, readable, lowercase, hyphenated, and describe the page's topic. They should be stable, so you never have to change them again.

Only change URLs when there's a genuine benefit. Every change is a redirect you have to maintain and a small risk you're taking on.

Step 6: Test everything before launch

Run a full pre-launch quality check on the staging site. Work through this checklist:

Which tools help audit SEO readiness before launch? A site crawler to compare the staging site with your benchmark crawl (and to test your redirect list in bulk), Google PageSpeed Insights or Lighthouse for speed, Google's Rich Results Test for schema, and Search Console for the live site once verified. Our technical SEO audit checklist lists what we check on every website.

Step 7: Launch carefully

Launch day is a sequence, not a single click. Choose a lower-traffic period and follow it in order:

1. Push the new site live and activate the redirect map.
2. Remove the staging block (password, noindex, robots.txt disallow).
3. Confirm robots.txt and the XML sitemap are correct, then submit the sitemap in Search Console.
4. Test your top 50 old URLs on the live site to confirm they redirect correctly.
5. Confirm HTTPS works everywhere and Analytics is recording.
6. If you changed domains, use Search Console's Change of Address tool and keep redirects from the old domain live.

Step 8: Monitor for the first eight weeks

Post-launch monitoring is where migrations are saved or lost. Watch for problems early, while they're still small:

Expect some fluctuation for a few weeks as Google re-crawls and re-evaluates the site. A sustained, page-specific drop usually points to a fixable cause such as a missing redirect, an indexing block, or changed content, and comparing against your baseline shows you which. No one can guarantee zero movement, and timelines vary with site size and how much changed. Keep redirects in place for at least a year.

What are the most common website migration mistakes?

• Launching with the staging noindex or robots block still on.
• Redirecting all old URLs to the homepage instead of to relevant pages.
• Building redirect chains or loops.
• Changing URLs, content, design and platform all at once, making problems impossible to diagnose.
• Rewriting titles and headings on pages that already rank.
• Forgetting tracking, so you can't tell what happened.
• Removing redirects after a few months.
• Skipping monitoring because the launch "went fine".

How do you choose an SEO-friendly platform to migrate to?

Choose a platform that gives you control over the things that matter to SEO. Before you commit, confirm that you can: set custom URLs, create 301 redirects, edit titles, meta descriptions and canonical tags per page, add structured data, generate and edit an XML sitemap, and control page speed by managing scripts and images. Some hosted website builders limit one or more of these, so check before committing, especially for a site that depends on organic traffic.

Hosting matters mainly through speed and reliability: fast server response, stable uptime and HTTPS. You don't need "SEO-specific" hosting. For a longer look at platform choices and how to plan a build around SEO from the start, read our SEO-ready website design guide, or see how to choose an SEO-ready web design company.

The bottom line

A migration that keeps its rankings is the result of preparation, not luck: benchmark, map every URL, build on staging, keep what ranks, test thoroughly, launch in order and monitor for eight weeks. The redirect map and the launch-day checklist do most of the protecting.

Our SEO-ready web design service includes 301 redirect mapping, a pre-launch SEO QA checklist, Analytics and Search Console setup, and post-launch monitoring of indexing and rankings. If you're planning a redesign or replatform, we'll review your plans and flag the risks before a page is built.