Relaunch without SEO loss

During a relaunch a website always loses visibility short-term — the only question is: how much and for how long.

With a technically clean migration: a 5–15% temporary drop in the first 1–2 weeks, full recovery in 4–8 weeks. That's the normal “reset” of a URL change — Google first has to crawl the new structure and reassign trust signals.

With a faulty migration: a 30–50% drop within the first 4 weeks, only partial recovery over 6–12 months. The main causes are almost always the same: blanket redirects instead of 1:1 mapping, content consolidation without an SEO strategy, missing internal linking in the new structure.

Important to understand: what's “normal” depends less on the relaunch itself — and almost entirely on the preparation.

Stabilization happens in three phases — and each has its own logic.

Phase 1: Re-crawl (day 1–14) — Google discovers the new URL structure. Rankings are most unstable in this phase, they jump, some URLs temporarily disappear from the index. That's normal and no reason to panic.

Phase 2: Re-indexing & consolidation (week 2–6) — the old rankings are assigned to the new URLs via your 301 redirects. Trust signals are reassigned. More than 80% of rankings are back in this phase.

Phase 3: Full stabilization (week 6–10) — the new structure is fully indexed, all signals are consolidated. From here, the site behaves like an “established” domain again.

What you shouldn't do in this phase: further structural changes. Each additional modification extends the stabilization phase by a full crawl cycle — so at least 2–3 weeks extra.

The most common mistake in website relaunches is also the most expensive — and at the same time the easiest to avoid.

The classic: blanket redirects to the homepage. All old URLs are redirected to the new homepage via a wildcard rule. At first glance it seems logical (“the user lands on the site after all”), but from an SEO perspective it's catastrophic.

Why Google ignores it: such blanket redirects are interpreted as a “soft 404” — that is, an error page posing as a success. The redirect is counted in the crawl statistics, but the link juice of the old URL is not transferred to the homepage.

• A 1:1 mapping for each URL: old → topically fitting successor
• If no successor exists: deliberately set a 410 status code (tells Google: “it's deleted, ignore it”) instead of a wildcard redirect
• When consolidating several old URLs: 301 to the combined page, with a clear canonical relationship

URL changes are one of the most frequently misjudged decisions in a relaunch — many want “nice new URLs” but overlook the cost.

Even with a perfect 301 setup, you lose between 5 and 15% of link juice per redirect hop. Multiplied across thousands of URLs, that results in a measurable visibility loss — which only recovers over months.

If URL changes are unavoidable: complete the full mapping before the relaunch, don't develop it in parallel with the build. Otherwise mapping gaps only become visible after go-live — and retroactive corrections are considerably more involved.

• When URL changes are worth it: ID-based URLs without keywords, missing or illogical hierarchy, inconsistent language routes, non-migratable legacy paths
• When it's better to leave URLs alone: when the old structure is fundamentally logical, when the old URLs have backlinks and rankings, when the improvement would only be “cosmetic”

Problems after a relaunch show up early — if you know what to look for. Whoever only notices after weeks that something's wrong has already made the most expensive mistake.

Warning signs in the first 7 days: 404 errors in the Search Console suddenly rise (more than 5× the normal level), crawl volume drops, server response times are higher than before the relaunch.

Warning signs in weeks 2–4: a visibility drop in Sistrix or Ahrefs of more than 20% below the pre-relaunch level, top keywords disappear from the top 10, click-through rate falls — the new URLs do rank, but generate fewer clicks.

Most important rule: whoever doesn't actively monitor in the first 14 days often only sees problems when they're considerably more expensive to fix. What would be solvable in 1 hour on day 7 often costs several days of work on day 30.

Yes — that's actually one of the most common use cases. You bring in the SEO migration expertise as an independent second opinion, without touching your existing collaboration.

What you get: an independent migration guide with URL mapping, risk assessment and a step-by-step checklist — as a specification your agency can implement.

How the collaboration works: I clarify questions directly with your agency's tech lead, if desired. No provider switch, no duplicate work.