Relaunch

A website relaunch is the fundamental redesign of an existing website, not a cosmetic refresh but an intervention in design, structure, technology and often content too. Triggers are usually an outdated design, technical debt, a change of CMS, a shifted business strategy or simply a brand relaunch. As exciting as the result can be – a relaunch is always also the single biggest risk an established website can take. Done wrong, rankings, backlinks and direct traffic built up over years shrink to a single-digit percentage of former visibility. Planned right, it’s the foundation for the next growth phase.

When is a relaunch worthwhile?

Typical triggers:

• Design age: the site looks dated, loads slowly, runs poorly on mobile (mobile-first indexing takes full effect)
• Technical debt: the CMS is no longer supported, plugins outdated, security updates missing
• Conversion problems: the site converts markedly worse than it should, and detail optimisation no longer suffices
• Brand relaunch / repositioning: a new corporate identity, a new audience, a new tone
• Strategy change: a new business model, new service lines, new markets
• Architecture deficits: the URL structure sprawls, the navigation no longer makes sense, the content doesn’t hold together
• Performance problems: the Core Web Vitals are permanently in the red and the theme/template can no longer be optimised

An honest preliminary analysis shows whether a relaunch is genuinely necessary or whether a targeted rebuild (technical refresh, on-page SEO, content overhaul) achieves the same effect more cheaply.

Risks of a relaunch

The worst thing that can happen in a relaunch: the site is suddenly prettier, but nobody finds it any more.

The process in seven phases

1. Inventory analysis

Before the first wireframe: where does the site stand? Which URLs rank? Which backlinks point where? Which content genuinely performs, which is dead weight? Tools: Google Search Console, Google Analytics, Screaming Frog, Ahrefs/Semrush. Output: a complete URL list with traffic, ranking and link values.

2. Concept

The fundamental decisions fall here: information architecture, navigation, templates, CMS choice, tech stack. Wireframes, clickable dummies, a binding design system. Important: the “old URL → new URL” mapping starts now, not only at launch.

3. Content migration

Clean up, consolidate and restructure old content. Merge weak pages instead of rescuing them individually. Resolve duplicate content. While you’re at it: go over every page’s substance again – does the value proposition hold, is the search intention clearly served?

4. Technical implementation

Set up the new CMS, build the templates, develop custom functionality, keep the performance budget (LCP, CLS, INP in the green), check accessibility.

5. Redirect mapping

The absolute mandatory field: every old URL must point via 301 redirect to its best new counterpart. Even when the URL stays structurally identical – spot-check, don’t guess. A hidden pluralisation (/leistung/seo → /leistungen/seo) is otherwise enough to lose rankings built over half a year.

# Example in .htaccess
RedirectMatch 301 ^/old-page$ /new-page

Tools: the old crawl, mirrored against the new URL structure, in a CSV → generate the redirects from that.

6. Soft launch + QA

Before go-live: a complete crawl of the staging environment, a Lighthouse audit of every central page, cross-browser testing, mobile smoke testing, tracking validation, a sitemap check. Fix all 404s and 500s before launch.

7. Launch + monitoring

Go-live with a minimal downtime window. Then: submit the new sitemap in Search Console, watch indexing speed, check the Search Console error reports daily, accompany ranking movements over 4–8 weeks. Experience shows the “new normal” appears 6–12 weeks after launch.

Redirect mapping: what must not happen

• A mass redirect of old URLs to the homepage (a “catch-all” to /) – Google treats that as a soft 404 and strips all backlinks of their effect
• Redirect chains (/a → /b → /c) – every additional hop eats link equity
• 302 instead of 301: Google interprets 302 as temporary and keeps the old URL in the index
• Forgotten image URLs: image search comes with its own index and needs the image redirects too

Frequently asked questions about relaunches

How long does a relaunch take? From briefing to go-live, realistically 3–9 months depending on scope. Main phases: concept (4–8 weeks), implementation (6–16 weeks), migration + QA (2–6 weeks).

Do you always lose rankings in a relaunch? With clean preparation – no. With neglected redirect mapping – almost always. A certain fluctuation range (±10% visibility) in the first weeks is normal and recovers afterwards.

Is a theme change enough to count as a “relaunch”? That’s more a redesign than a relaunch. A real relaunch intervenes in structure, URLs and often technology. Just pulling in a new theme is cheaper and less risky.

How big is the budget for a typical relaunch? Heavily dependent on scope, CMS choice and custom functionality. A professional relaunch of a mid-sized company website starts in the five-figure range; for e-commerce or corporate web presences, easily six figures.

When is the best time for a launch? Rather mid-week, not Friday (weekend monitoring is harder). Outside your industry’s peak season. Never shortly before the core team’s holidays.

Conclusion

A relaunch is the biggest SEO risk an existing website consciously takes, and at the same time its biggest creative opportunity. The difference between a successful and a ruinous relaunch almost never lies in the design but in the preparation: a complete URL inventory, precise redirect mapping, an honest QA phase. We accompany website relaunches from analysis to post-launch monitoring – more details on the website relaunch page or directly in a no-obligation consultation.