Website relaunch without losing rankings: how to migrate properly

A website relaunch only costs Google rankings if URLs, content or internal linking are changed without a plan. With a complete URL inventory, clean 301 redirects and a few weeks of monitoring, your visibility survives the move practically unscathed. Here is the process I use for relaunches – including the mistakes I see most often in the wild.

Why relaunches cost rankings

Google ranks individual URLs, not websites as a whole. If a page's address changes during the relaunch without a redirect establishing the connection, the new URL starts from zero – the signals built up over years for the old address evaporate. Add to that two other classics: content that is dropped without replacement, and technology that makes crawlers' lives difficult.

Step 1: create a URL inventory

Before the rebuild comes the stocktake: which URLs exist, and which of them actually bring visitors? The sources are Google Search Console (performance report), the current sitemap and analytics data. The result is a complete list of all old addresses – the foundation for everything that follows.

Step 2: map old content to new

For every old URL a decision is made: will the page exist under a new address? Will it be merged with another one? Or is it deliberately dropped? Important: pages that rank and bring visitors must not disappear "by accident" – if you cut content, you should know which rankings depend on it.

Step 3: set up 301 redirects

Every old URL that has an equivalent gets a permanent 301 redirect to its new destination – individually and directly. Two rules make the difference:

• No chains: old → new in one hop, not via intermediate stops. Every additional hop costs crawl budget and dilutes signals.

• No blanket redirect to the home page: Google treats that like a 404 – the redirect has to match in terms of content.

Step 4: carry over on-page signals

Page titles, meta descriptions, heading structure, structured data and – for multilingual websites – hreflang annotations: these signals should be designed deliberately during a relaunch, not left to chance. If you migrate from an old system, take working titles and descriptions with you instead of reinventing them.

Step 5: the launch checklist

• The staging environment was protected with noindex – and the noindex has been removed on the live site (the most common launch mistake of all).

• New XML sitemap generated and submitted to Google Search Console.

• Spot checks: the most important old URLs redirect correctly with status 301.

• Actively inform search engines – for example via IndexNow, so Bing and others know the new URLs immediately.

Step 6: monitoring after launch

For the first eight to twelve weeks, Google Search Console belongs on your desk: are 404 errors rising? Are redirected pages being picked up cleanly? Minor ranking fluctuations in the first weeks are normal – if individual important pages stay behind permanently, targeted fixes can counteract this.

The most common mistakes at a glance

• Setting up redirects "later" – later, the damage is already done.

• Redirect chains from several relaunch generations.

• Indexable staging environments going live as duplicate content.

• Deleting ranking content without replacement because it "no longer fits the concept".

From practice: the relaunch of this website

This website is itself a complete relaunch – from a legacy Laravel system to a new Laravel 13 application, including a new URL structure with language prefixes. All legacy URLs redirect to their new equivalents via 301, and 404 candidates that later surfaced in Search Console were followed up specifically. The result: the rankings survived the move, and visibility has kept growing since.

Conclusion: a relaunch is a move with mail forwarding

When you move house, you set up mail forwarding – that is exactly what 301 redirects do for your website. I handle relaunches as a complete package: new system, content migration and a full redirect concept so your Google rankings are preserved. Tell me about your project in a free initial consultation – or first get an overview of my services as a web developer in Kassel.