A relaunch is meant to make a website better: modern design, clearer structure, faster load times. Yet in practice this very step often backfires. A few weeks after going live, rankings collapse, traffic drops and enquiries fall with it. In many cases the cause is not the new design but a handful of avoidable mistakes with redirects, content, structure and speed. From more than 50 projects we have supported (project experience) we know that a relaunch need not cost any rankings if you treat it as a migration rather than a fresh start. This article shows the most common mistakes and how to avoid them concretely, so the new site looks better and still gets found. No one can seriously promise a specific position, but a clean approach keeps existing visibility stable and lays the foundation to expand it afterwards.
Why a Relaunch So Often Costs Rankings
Google does not evaluate your domain as a whole but each individual URL. Over years, every page accumulates signals: rankings for specific search terms, inbound links, click and dwell data. During a relaunch, exactly the things these signals are attached to often change: the addresses of the pages, their content and the internal linking. When a proven URL disappears without replacement or reappears under a new address with no connection to the old one, Google loses the thread. The accumulated signals evaporate, and in the eyes of the search engine the new page starts almost from scratch.
There is also a time effect that is often underestimated. After a relaunch, Google has to recrawl the entire site, process the redirects and reclassify the structure. This re-evaluation typically takes 4 to 12 weeks (project experience), depending on scope and how often the site is crawled. During this phase rankings fluctuate, and that is normal. It only becomes dangerous when technical mistakes are added, because then a temporary fluctuation turns into a permanent loss. These very mistakes can be planned for and avoided. How to set up a website for findability in general is described in our article on the SEO basics for businesses.
Briefly explained: what ranking loss means
Mistake 1: Forgetting or Misconfiguring Redirects
By far the most common and most expensive mistake concerns redirects. When URLs change, every old address must point via a permanent 301 redirect to its thematically matching new counterpart. The 301 tells Google that a page has permanently moved and passes the existing ranking signals to the new address (Google Search Central). If this redirect is missing, users and search engines hit a 404 error page and all signals of the old URL are lost. Equally damaging is redirecting all old pages to the home page en masse: Google treats such catch-all redirects like an error and does not pass the signals on.
The solution is a complete redirect map. Before the relaunch you export all existing URLs, for example from the sitemap, the Search Console and the server logs, and assign a new one to each old address. Every redirect should lead directly to its target and not run through chains of several hops, because each additional stop costs time and signal. Even seemingly unimportant detail pages belong in the map, because it is precisely older subpages that often carry valuable links. After go-live, the map is checked: every old URL must land via a 301 on a working target page.
# Every old URL points via 301 to its thematic counterpart
Redirect 301 /services/web-design-old /services/web-design
Redirect 301 /products/detail-123 /shop/product-webshop
Redirect 301 /blog/2019/old-article /magazine/plan-a-relaunch
# Right: 1:1 to the matching page
# Wrong: all old URLs to the home page en masse (/)
# Wrong: chains like A -> B -> C instead of direct A -> CRedirect checklist
Mistake 2: Cutting Content Instead of Carrying It Over
A new design tempts you to declutter radically: shorter texts, fewer pages, leaner content. Visually this looks tidy, but for visibility it is often a step backwards. Many rankings depend on concrete content, on a detailed service text, on answered questions, on technical terms within the body copy. If this content is heavily shortened or removed entirely during the relaunch, the page loses the substance it ranks for. It is particularly risky to delete extensive guides, reference pages or blog articles without replacement because they are no longer envisaged in the new concept.
The better order is: preserve first, then improve. Before the relaunch you record which pages bring the most organic traffic and for which terms they rank. This content is carried over into the new design and carefully revised rather than replaced. New, shorter texts can complement the old ones but should not push them out without replacement. It is also important that shortened content still fully answers users' questions, because this is exactly how Google measures relevance. How to build and maintain content deliberately is explored in our article on conversion optimization for more enquiries.
Inventory the content
Before the relaunch, record every page with traffic and rankings. What drives visibility is carried over deliberately, not discarded by chance.
Carry over and improve
Keep strong texts and modernize them carefully instead of replacing them with shorter placeholders. Substance stays, form is renewed.
Keep answering questions
Even leaner pages must fully answer the search queries. Relevance comes from answers, not from visual polish alone.
Mistake 3: Rebuilding Structure and URLs Needlessly
Many relaunches change the URL structure without it being necessary: out of habit, because of a new system, or because the menu is reorganized. But every changed address means one more redirect, a piece of lost signal and a further risk. The basic rule is therefore: preserve as much structure as possible and change only where there is a real reason. If an existing URL is descriptive, short and thematically fitting, there is rarely any reason to replace it. Stable addresses are a value in themselves, because links, bookmarks and rankings are attached to them.
At the same time, internal linking is an often overlooked lever. After the relaunch, all internal links must point directly to the new URLs and not run through redirects. The navigation, breadcrumbs and sitemap should also cleanly reflect the new structure so that Google quickly understands the hierarchy. Where the structure genuinely improves, for example through clearer categories or a flatter hierarchy, a change makes sense, but it should be deliberately planned and fully secured with redirects. How a well-considered structure strengthens local findability is shown in our article on local SEO and the Google Business Profile.
| Aspect | Risky relaunch | Safe relaunch |
|---|---|---|
| URL structure | Rebuilt across the board | Largely preserved, improved selectively |
| Redirects | Missing or pointing to the home page | Complete 301 map, 1:1 to matching pages |
| Content | Heavily cut or deleted | Carried over, modernized, extended |
| Internal links | Run through redirects | Point directly to the new URLs |
| Go-live | All at once, without testing | Checked, then live, then monitored |
Mistake 4: Underestimating Technology and Speed
A relaunch is the opportunity to improve the technical foundation, but just as often it becomes a step backwards. A new, playful design with large images and many scripts can worsen load time, and that directly affects users: around 53 percent (Think with Google) of mobile visitors leave a page that takes longer than three seconds to load. Google factors loading performance into its assessment via the Core Web Vitals, so a slower page after the relaunch not only loses visitors but can also lose visibility. It is equally important that the new site works cleanly on all devices, because Google primarily evaluates the mobile version.
Technology holds further silent traps. An accidentally active instruction that blocks search engines can remove the entire site from the index after go-live: staging environments are deliberately blocked for search engines, and if this block is not removed at launch, the site stays invisible. A missing or outdated sitemap, incorrectly set canonical references or a forgotten switch to secure connections can also cost rankings. These points belong on a launch checklist that is worked through before and immediately after going live. How to improve loading performance in a targeted way is described in our article on the Core Web Vitals and load time.
The most expensive mistake is the invisible one
The Safe Approach: Relaunch in Phases
A relaunch without ranking loss is above all a question of sequence. Anyone who follows the right steps before, during and after go-live turns a risky major event into a controlled transition. The following order has proven itself in practice and can be applied to small and large projects alike. What matters is that going live is not the conclusion but the start of a monitoring phase, in which you spot mistakes early and correct them before they take hold in the rankings.
- Take stock: record all URLs, top pages, rankings and links before the relaunch
- Create the redirect map: every old URL gets a matching new target via 301
- Secure the content: carry over strong content and improve it carefully instead of deleting it
- Preserve the structure: keep URLs as far as possible, point internal links to the new targets
- Check the technology: test load time, mobile rendering, sitemap and indexability before go-live
- Monitor after launch: watch redirects, error pages and rankings over several weeks
A word on expectations belongs here. Even with a clean relaunch, rankings can fluctuate slightly in the first few weeks because Google first has to re-evaluate the new site. This phase is normal and usually settles within 4 to 12 weeks (project experience). A specific position cannot be promised, because Google calculates rankings from many signals and continually adjusts its systems. What can be planned are the factors that demonstrably count: complete redirects, preserved content, a stable structure and a fast foundation. How this visibility ultimately turns into enquiries is explored in our article on what a website costs in 2026 and what matters for the value in return.