How to Migrate a Website Without Losing SEO Rankings

Website migrations lose search traffic for predictable reasons: pages disappear without redirects, content that ranked is cut or rewritten beyond recognition, internal links break, and tracking stops working so nobody notices until weeks later. Almost all of it is preventable with planning.

A migration here means any change that alters URLs, platforms or structure: a redesign that renames pages, a move from Wix or Squarespace to WordPress, a switch to Shopify, a domain change, or merging two sites. Changing only the design while keeping every URL and all the content is much lower risk, though not risk-free.

Expect some movement, plan to minimise it

Google’s own documentation on site moves says that a site may see temporary fluctuations in rankings while Google recrawls and processes the change. That is normal. What is not normal is a sustained loss of a large share of traffic, which almost always traces back to something missed in the plan.

The aim is not zero change. It is a short dip, followed by recovery, with nothing important lost along the way.

Before anything changes: record what you have

The single most valuable step happens before the new site is built. You need a complete picture of the current site to protect it.

• Every URL. Crawl the current site with a tool such as Screaming Frog, and combine the results with URLs from your XML sitemap, Google Search Console and analytics. Crawls miss orphaned pages that still receive traffic or links.
• What performs. Export landing pages with organic traffic, conversions and the queries they rank for from Search Console and analytics. These are the pages you cannot afford to lose.
• What has links. Pages with external backlinks carry authority that redirects need to preserve.
• Current metadata and content. Titles, meta descriptions, headings and body content for important pages, so you can check the new versions do not quietly lose what made them rank.
• Tracking setup. Analytics tags, conversion events, Meta Pixel, call tracking and any other scripts.

Keep this as a benchmark. After launch it becomes the way you check that nothing went missing.

Build a redirect map

Every old URL that has traffic, links or rankings needs a 301 redirect to the most relevant page on the new site. Google treats permanent redirects as a strong signal that the new URL replaces the old one.

Map one to one wherever possible: old service page to new service page, old blog post to the same post at its new address. Avoid redirecting large numbers of old pages to the homepage. Google tends to treat irrelevant redirects like that as soft 404s, and the value of those pages is lost. If a page genuinely has no equivalent on the new site, redirect it to the closest relevant category or, for truly obsolete pages with no traffic or links, let it return a 404 or 410.

Avoid redirect chains, where an old URL redirects to another old URL that redirects again. Point each old URL straight at its final destination. Google’s guidance is to keep redirects in place for as long as possible, and generally for at least a year. In practice, there is little reason to ever remove them.

Protect the content that ranks

Redesigns often come with a content rewrite. That is a good opportunity, and also the most common hidden cause of lost rankings. A service page that ranked well with 900 words of detailed explanation may lose its position if the new design reduces it to three short paragraphs and an image.

For your top-performing pages, keep the substance even if the presentation changes. Preserve headings that match search intent, key explanatory content, FAQs and internal links. Improve them by all means, but do not strip them out for visual tidiness.

Check the technical basics on the new site

Before launch, on a staging site that is blocked from search engines:

• Titles, meta descriptions and headings are set correctly for every important page.
• Canonical tags point to the new URLs, not staging or old addresses.
• Internal links point directly to new URLs rather than relying on redirects.
• The new XML sitemap lists only live, indexable URLs.
• Structured data carries across where it existed.
• Mobile layout and page speed are at least as good as the old site. Our guide to why websites are slow covers what to check.
• Analytics, conversion tracking and pixels fire correctly.

Then, critically, check that the noindex settings or password protection used on staging are removed at launch. Forgetting this is one of the most damaging and most common migration mistakes. Our website launch checklist covers the full set of go-live checks.

Launch day and the weeks after

Launch at a quiet time for your business, not before a busy season. Immediately after launch, test the redirect map by running the old URL list through a crawler and confirming each returns a single 301 to the right page. Submit the new sitemap in Search Console. If the domain has changed, use Google’s Change of Address tool in Search Console as well as redirects.

Over the next few weeks, monitor Search Console for crawl errors, rising 404s and pages Google has crawled but not indexed, and compare organic landing page traffic against your benchmark. Problems found in the first fortnight are usually quick to fix. Problems found three months later have already cost you.

When to get help

A small brochure site moving platform with a dozen pages can often be handled carefully in-house. Larger sites, ecommerce stores, sites with a lot of organic revenue, and any project combining a platform change, a URL restructure and a content rewrite at once carry much more risk. If you are planning a redesign, our website redesign guide explains how to scope it so SEO is part of the plan from the start.

Migrating without losing what you have built

Your existing rankings represent years of accumulated value, and a migration is the moment that value is most exposed. Our website design and development service builds migration planning, redirect mapping and post-launch monitoring into every rebuild, with technical SEO support for larger or more complex moves.