Website relaunch without losing rankings: the safe process

A relaunch is one of the most critical routine events in a website's life. Not because something visible breaks - but because something invisible does. The new site is faster, cleaner, more modern. And three weeks later the enquiries are gone, the rankings have slipped, the traffic has halved. Nobody understands why, because everything looks better.

That's not bad luck and it's not an isolated case. It's a pattern with a clear cause: rankings don't live in the design. They live in URLs, in structure, in content and in technical signals - and those are exactly what a relaunch changes, often without anyone noticing.

This article shows why that happens, which five silent risks are behind it, and in what order a relaunch has to run so that visibility survives the move. At the end there's a real case where we had to do exactly this cleanup - and a self-check before you press the launch button.

Why a prettier design alone saves nothing

Google doesn't rank design as taste. But it does rank the signals a relaunch often changes: URLs, content, internal links, load time, indexability and technical structure. A page that has held position 3 for a search like "electrician in Munich" for two years earned that ranking through signals attached to that one URL.

A relaunch touches almost all of those signals at once: the URL changes. The page structure changes. Copy gets rewritten, headings reordered, internal links relaid. Each of those changes is, on its own, an intervention in a ranking factor. All of them together, on a single day, are an abrupt change to many signals at once.

Google itself is clear: in a move with URL changes, temporary ranking fluctuations are normal, and a medium-sized move takes a few weeks for most pages to be reindexed. So the question isn't whether it fluctuates - it's whether you lose temporarily or permanently. The difference between the two is preparation.

The one mistake that's almost always behind it: redirects

When a relaunch costs rankings, in the vast majority of cases exactly one thing is the cause: missing or incorrect redirects.

The mechanics are simple - and they forgive no gaps. The old URL ranks and has backlinks. In the relaunch the page gets a new address, the old one is deleted. If you don't set up a redirect from old to new, you sever the connection: the old URL returns a 404, the ranking decays, and every external link that ever pointed to the old address now leads nowhere. The authority you built over years is lost.

A clean redirect strategy follows four rules:

• 1:1 mapping. Every old URL is pointed to its closest matching new counterpart - not everything bundled onto the homepage. Google effectively treats a mass redirect to the homepage as a soft 404; the value of the old pages is lost.
• 301, not 302. A 301 is a permanent redirect and carries the old page's signals across. A 302 signals "temporary only" - a common, expensive configuration mistake.
• No chains. Old → new in one step. Redirect chains (old → middle → new) dilute the signal; keep them short.
• Keep them long enough. Google recommends keeping redirects in place as long as possible - for a site move typically at least a year, and longer while relevant traffic or backlinks still flow through them.

What to do: The redirect map is built before launch, not after. Every existing URL is inventoried and assigned a target, before the old page disappears.

A redirect map built after launch isn't prevention anymore. It's damage control - and some damage can no longer be controlled.

The five silent risks

Redirects are the most common cause, but not the only one. These five mistakes do the damage nobody notices at launch - because the site works and looks good.

1. An accidental noindex. During development the staging site is hidden from Google - via a noindex tag or a robots.txt block. If that block isn't removed at go-live, the new website tells Google for weeks: "don't index me." The classic relaunch mistake, precisely because it's invisible from the outside.
2. Removed or trimmed content. Pages or text that ranked well get trimmed, merged or "tidied up" during the relaunch. With them goes exactly the content Google judged the page relevant for. Prettier doesn't automatically mean more visible.
3. Collapsed internal linking. A new navigation buries pages that were previously easy to reach three clicks deep. Internal links govern how authority flows through the site - break that structure and even pages you didn't technically change will sink.
4. Performance regressions. The new design brings heavier images, a larger framework, more scripts. Load time rises, Core Web Vitals worsen - and with them a signal that feeds into the overall page experience.
5. Lost measurement signals. Analytics tag forgotten, Search Console not migrated, structured data dropped in the redesign. The insidious part: you don't just lose signals - you lose the ability to even see the damage.

What to do: Each of these belongs on a launch checklist that's ticked off before go-live - not discovered in the troubleshooting afterwards.

The process that protects rankings

A relaunch without ranking loss isn't luck, it's a sequence. This one has proven itself:

1. Measure first: inventory and baseline

You can't protect what you haven't measured. Before anything is rebuilt, a complete inventory is created: every existing URL, its current rankings, the top pages by traffic, the most important backlinks. That's the blueprint for everything else - and the only reference against which you can honestly judge later whether the move succeeded.

2. Build the redirect map - before launch

Every old URL is assigned its 1:1 target, as a 301. This map is the backbone of the entire move and is created while the old site still exists.

3. Preserve structure and ranking content

What ranks stays - in substance, not necessarily in layout. Well-performing content is carried over and strengthened, not trimmed in the name of freshness. Headings that carry relevance are kept.

4. Execute the launch in an orderly way

For small and medium sites, moving all URLs at once is usually the better choice - it helps the algorithms detect the move faster. Large sites can be migrated in sections if that keeps monitoring and troubleshooting more controllable. Either way, at go-live: remove the staging block and submit the new sitemap in Search Console. For a domain or subdomain move, also use Search Console's Change of Address tool; for plain URL changes within the same domain, clean redirects and an updated sitemap are enough.

5. Monitor afterwards

In the weeks after launch: watch index coverage, check for 404s and broken redirects, hold rankings against the baseline. Fluctuation is normal - but drops that don't recover are a signal to intervene immediately.

What the Rucker Elektro case teaches about cleanup

Sometimes we don't come for the relaunch, but for the cleanup afterwards. That was the case with Rucker Elektro, a Munich electrical company we took over at the end of February 2026 from a previous agency. At takeover, two problem areas were apparent: technical data-protection risks and a setup that hadn't cleanly preserved important SEO signals.

The clearest example: a page on electrical meter cabinet modernisation that had previously held a top position for Munich searches. Through the faulty setup and missing redirects it slipped further and further - until it eventually fell out of the index entirely. We retrofitted the redirect map and salvaged what could be salvaged. But this is exactly where the uncomfortable lesson sits: not everything was salvageable. A page that has already dropped out of the index doesn't return on command, and not necessarily in full.

What could be repaired, we repaired. In seven weeks, with data straight from Google Search Console:

• Average position: +5 places - now top 10 for relevant Munich searches.
• Visibility almost tripled (+147% impressions per day).
• Clicks: +63%.

These numbers aren't an argument for how well recovery works. They're an argument that recovery is more expensive, slower and less complete than prevention. A properly prepared relaunch would never have lost the meter-cabinet page. The cleanup couldn't bring it back.

Pre-launch self-check

Before the new site goes live - can you answer these five questions with yes?

• Is there a complete list of all old URLs with their current rankings?
• Does a 1:1 redirect map (301) exist before the old site disappears?
• Is it guaranteed that the staging environment's noindex block will be removed at go-live?
• Is the content that ranks today being preserved - in substance, not just in look?
• Are analytics and Search Console set up for the first day after launch?

If even one answer is no, that's the issue - not the design.

What to do now

A relaunch is no reason to sacrifice rankings - but it punishes anyone who treats it as a pure design project. If your relaunch is coming up, we check the critical SEO risks before go-live: URLs, redirects, indexing, internal links, ranking content, sitemap, tracking and Search Console. The goal isn't a prettier launch. The goal is a relaunch that protects visibility.

That's the core of our website relaunch service; how the move fits into an ongoing SEO strategy, we clarify in the same step.

Have your relaunch risk reviewed

Closing thought

A relaunch is a promise to the next few years - and a risk to everything you've built so far. Treat the invisible signals with the same seriousness as the visible design, and the move becomes a growth step rather than a setback. Treat them carelessly, and you pay the price where nobody sees it coming: in the enquiries that don't arrive.

Sources:

• Google Search Central - Site moves with URL changes: permanent redirects, move small/medium sites in one go, submit sitemap, keep redirects as long as possible (typically at least a year), temporary fluctuation is normal
• Google Search Central - Redirects and Google Search: permanent redirects as a canonicalization signal; 302 unsuitable for permanent moves
• Google Search Console - Change of Address Tool: correctly registering an address change for a domain or subdomain move
• Rucker Elektro field data: Google Search Console, as of April 2026 (7 weeks after takeover)