Website Migration SEO: How to Move Without Losing Rankings

A new website should bring more leads. Too often, it does the opposite. Traffic drops the week after launch, rankings disappear and nobody is sure why.

The cause is almost always the same: URLs changed, redirects were missed, content was removed or the new site was accidentally blocked from Google. This guide explains website migration SEO in practical terms, with a checklist for before, during and after launch. It is part of our complete SEO guide for businesses.

What counts as a website migration?

Any change that affects how search engines find and understand your pages counts as a migration.

The higher the risk, the more planning matters.

Why rankings drop after a migration

Rankings are tied to specific URLs. Each URL has its own history: backlinks pointing to it, signals Google has learned about it and its position for certain searches. When a URL disappears without a redirect, that history is lost.

The most common causes of traffic loss:

• Missing or wrong redirects, so old URLs return 404 errors
• Redirecting everything to the homepage instead of to matching pages
• Removed content, where pages that ranked are dropped or cut down
• Changed titles, headings and copy that removed the keywords pages ranked for
• A noindex tag or robots.txt block copied from the staging site
• Broken internal links pointing to old URLs
• Slower page speed on the new templates

Every one of these is preventable.

Before launch: the planning checklist

This is where most of the work happens.

1. Benchmark everything

Record current performance so you can compare after launch:

• Organic users and key events (formerly called conversions) from Google Analytics 4
• Clicks, impressions and top pages from Search Console
• Rankings for your important keywords
• Core Web Vitals for key templates

2. Crawl and list every URL

Crawl the current site with Screaming Frog and export every URL. Add URLs from your XML sitemap, Search Console's top pages, GA4 landing pages and your backlink tool. Some URLs with traffic or backlinks are not linked anywhere on the site, so a crawl alone will miss them.

3. Identify your most valuable pages

Mark the pages that bring the most organic traffic, leads, revenue and backlinks. These need extra care. Their content, title tags and headings should carry over to the new site unless there is a clear reason to change them.

4. Build the redirect map

A redirect map is a spreadsheet with every old URL in one column and its new destination in the next.

Rules for a good redirect map:

• Use 301 redirects for permanent moves.
• Redirect each old URL to its closest matching new page, not to the homepage.
• Redirect directly to the final URL, with no chains.
• Only let a URL return 404 or 410 if there is no relevant page and it has no traffic or backlinks.

On an Apache server, redirects can sit in the .htaccess file. These are three separate scenarios, not one combined file:

# Scenario 1: a single page that moved on the same domain
Redirect 301 /local-seo.html /services/local-seo/

# Scenario 2: an old URL with a query string, same domain
RewriteEngine On
RewriteCond %{QUERY_STRING} ^id=4$
RewriteRule ^services\.php$ /services/local-seo/? [R=301,L]

# Scenario 3: a whole domain that moved (use this on its own,
# or give earlier rules absolute https://www.newbrand.com targets
# so no URL is redirected twice)
RewriteCond %{HTTP_HOST} ^(www\.)?oldbrand\.in$ [NC]
RewriteRule ^(.*)$ https://www.newbrand.com/$1 [R=301,L]

A simple Redirect line cannot match query strings, which is why URLs with parameters need a RewriteCond rule. Platforms such as Shopify and Wix, and WordPress redirect plugins, have their own redirect managers. Ask your developer which method suits your setup.

5. Review the new site on staging

Before launch, check the staging site against the old one:

• Titles, meta descriptions and H1s carried over for important pages
• Content on important pages kept, not shortened
• Internal links pointing to new URLs
• Canonical tags pointing to the new live URLs, not staging URLs
• Structured data in place
• Mobile layout and Core Web Vitals at least as good as before

Keep staging blocked from search engines with a password, not only with noindex, so it never gets indexed by accident. Our on page SEO checklist is useful for reviewing key templates.

Launch day checklist

• Remove the staging block. Check robots.txt and noindex tags on the live site within minutes of launch.
• Upload the redirects and test a sample of old URLs, including your most valuable pages.
• Submit the new XML sitemap in Search Console.
• Keep the old sitemap available briefly so Google recrawls old URLs and discovers the redirects faster.
• Check analytics and tracking are recording visits and key events.
• For a domain change, verify the new domain in Search Console and use the Change of Address tool.

After launch: what to monitor

Expect some movement in the first few weeks while Google processes the changes. Watch closely:

• Search Console Pages report for new 404 errors and indexation issues
• Crawl the old URL list to confirm every redirect works and goes to the right page
• Rankings for important keywords, daily for the first two weeks
• Organic traffic and conversions against your benchmark
• Core Web Vitals on the new templates
• Backlinks to old URLs. For your strongest links, ask the linking sites to update to the new URL where practical.

Keep redirects in place for at least a year. Google's guidance is to keep them for as long as possible, and many sites keep them permanently.

How long does recovery take?

On a well planned migration, traffic often stays steady or dips only briefly. A small domain move can settle within a few weeks. Larger sites, platform changes and domain moves can take longer. If traffic is still well below the benchmark after a month or two, something has usually gone wrong, most often redirects or removed content. Our guide on how long SEO takes explains what normal ranking movement looks like.

A migration done properly

For one industrial component manufacturer, we owned SEO for a full site migration, preserving URLs across more than 40 product pages while improving heading structure, schema and internal links. See the industrial B2B SEO case study.

A migration is also a good moment to make your site easier for AI assistants to read. Our guide to schema markup for AI search covers what to add while templates are being rebuilt.

Planning a redesign?

If you are rebuilding your site or changing platforms, bring SEO in at the planning stage, not after launch. Our website development and SEO services teams work together on migrations. Request a free SEO audit and we will benchmark your current site and flag the pages that need protecting.