Website Migration SEO: Reduce the Risk of Ranking Loss

The new website is live, the design finally looks modern – and three weeks later, enquiries dry up. A look at Search Console tells the story: pages that used to sit on page one have dropped off a cliff. That is what ranking loss after a migration looks like – a common and largely avoidable risk. Getting website migration SEO right means thinking about search from the start, not once the damage is visible.

Ranking losses are rarely random – they have concrete, well-known causes. Know them and work through them before launch, and you cut the SEO risk of the migration considerably.

This guide starts with why migrations can cost rankings in the first place. Then it walks through an SEO-conscious migration step by step – from the URL inventory to the redirect map to the launch checks. At the end you get a mistakes table and a site migration checklist to work through.

Why a website migration costs rankings

A migration usually changes more than you expect: URLs, structure, content, technology. Each of those changes can break signals that took years to build. Search engines have indexed your site and learned its structure – a migration requires them to process those signals again.

The typical causes of ranking loss are:

• URL changes without a redirect: when a URL changes and the 301 is missing, Google loses the link to the old, well-ranking page. Backlinks and search results lead nowhere.
• Deleted or merged content: migrations often involve “tidying up”. If pages that drove traffic disappear, their rankings disappear with them.
• Lost metadata: title tags and meta descriptions are frequently regenerated or forgotten in the new system. Changed titles can shift relevance signals, while missing descriptions also affect how search results are presented.
• A slower new site: a fresh design with heavy images and lots of script can load slower than the old one. A worse page experience can affect users and search visibility.
• Missing internal links: internal linking spreads relevance across the site. Rebuild the navigation and drop old references, and important pages lose their connections.

These mistakes rarely occur alone. Usually several combine – and their effects add up. The rest of this guide shows how to rule out each cause deliberately.

Step 1: Build a URL inventory

Before you change anything, you need a complete list of every existing URL. A URL inventory is the foundation of any SEO-conscious migration – without it, you do not know what you even need to redirect.

Collect your URLs from several sources so nothing slips through:

• The XML sitemap of the old site as a first overview
• Google Search Console: which pages bring impressions and clicks
• A crawler (such as Screaming Frog) that walks the site end to end
• Server logs or analytics for pages with real traffic

For each URL, note which pages are especially valuable: high traffic, strong rankings, many inbound links. These pages take priority and must not be lost in the migration.

The result is a table of all old URLs – your map for the steps that follow. Skip this step and you are planning the migration blind.

Step 2: Build a redirect map with 301s

The redirect map is the heart of an SEO-conscious migration. It defines, for each old URL, which new URL it redirects to with a 301. The 301 signals a permanent move to Google and helps associate signals from the old address with the new target.

Here is how to approach it:

• Every old URL gets a target. When the address changes, the 301 points to the closest matching new page.
• Redirect by relevance. Do not blanket-redirect everything to the homepage. A service page belongs on the corresponding new service page, a blog post on the matching new post.
• If a URL stays the same, no redirect is needed. Only changed addresses need one.
• Avoid redirect chains. Point straight to the final target, not through several hops.

Google describes the process for moves in its official documentation on site moves with URL changes. For a permanent move, use a permanent server-side redirect such as 301 or 308; 302 and 307 are intended for temporary redirects.

Test the redirects on a staging environment before launch. Every URL from the inventory should 301 exactly once to its correct target.

Step 3: Carry over content and metadata

Rankings depend heavily on content. If a page ranks well, its text, structure and title tag are important parts of the picture. Review and carry these elements over deliberately so relevant signals remain intact.

Deliberately carry over:

• The actual body content of well-ranking pages. Do not trim strong content just because the new design allows for less text.
• Title tags and meta descriptions. Check in the new system whether these came across correctly – many systems otherwise generate new ones automatically.
• The heading structure (H1, H2 …). It helps search engines understand how the page is built.
• Image alt text and descriptive file names, especially where images bring traffic through image search.

If you genuinely want to consolidate content, do it deliberately: merge two weak pages into one strong page and redirect both old URLs to the new one. Never simply delete a page that brings traffic. How a clean move works in detail is covered on our website migration page. If your old site still runs on Joomla, our Joomla alternative page covers what is specific to that switch.

Step 4: Check internal links

Internal linking spreads relevance and guides both visitors and search engines through your site. It is easy to lose in a migration – new navigation, new structure, and suddenly important pages are poorly connected.

Watch these points:

• Update internal links to the new URLs. Links should point straight to the new address, not run through a redirect.
• Connect important pages well. Your strongest pages should be reachable from the navigation or from relevant content.
• Avoid orphan pages. Every important page needs at least one internal link, or visitors and crawlers will barely find it.

After the internal rebuild, use a crawler to check whether internal links lead nowhere or still point to old URLs. It is quick to do and stops you from wasting relevance inside your own site.

Step 5: Launch checks and monitoring

Launch is not the end – it is the start of the critical phase. The first days and weeks decide whether the migration runs cleanly. Close monitoring catches problems before they become permanent.

Right after launch:

• Create a new XML sitemap and submit it in Google Search Console.
• Watch Search Console: keep an eye on index coverage, crawl errors and sudden drops.
• Turn on 404 monitoring: find error pages and add the missing redirects.
• Test redirects live: open a sample of the most important old URLs in the browser and confirm they redirect correctly.
• Check robots.txt and indexing: make sure the new site is not accidentally set to “noindex” or fully blocked – a classic mistake when moving from staging to live.

Keep monitoring for several weeks. Short-term fluctuations are normal; if losses remain after several weeks, work through the possible causes deliberately – usually a redirect or a piece of content is missing.

Turn performance into an advantage

A migration is more than damage control. It is a useful opportunity to shed technical baggage and get faster. Where the old site was slow, the new one can create a real advantage – speed can support rankings and user experience at the same time.

Use the migration to:

• Improve load times: optimised images, clean code, little unnecessary script. Which levers matter most is covered in our guide to improving website loading speed.
• Build the mobile experience right from the ground up, instead of bolting it on.
• Clarify the structure: readable URLs, a clear hierarchy, clean internal linking.

Before launch, check that the new site is genuinely faster than the old one – not slower. Our free website check gives you a first read on the state of your current or new site. A migration that slows the site down wastes the very opportunity it offers.

Common migration mistakes at a glance

Many ranking losses trace back to a handful of mistakes. This table shows the cause, the consequence and the fix:

Site migration checklist

Work through this list top to bottom – before, during and after launch:

• Build a complete URL inventory from sitemap, Search Console and crawler
• Mark valuable pages (traffic, rankings, inbound links)
• Build the redirect map: every changed URL 301s to its matching target
• Avoid redirect chains, point straight to the final target
• Carry over content from well-ranking pages, delete nothing without a replacement
• Transfer title tags and meta descriptions into the new system and verify them
• Update internal links to the new URLs, avoid orphan pages
• Test redirects on staging before going live
• Check indexing: no accidental “noindex”, robots.txt correct
• Submit the new XML sitemap in Search Console
• Turn on 404 monitoring and add missing redirects
• Measure the new site’s load time and compare it with the old one
• Watch Search Console and rankings closely in the first few weeks

The biggest lever is at the start: a complete inventory and a clean redirect map. Lay that foundation and monitor the launch to improve the chances of preserving visibility while shipping a faster, clearer website.