Website Relaunch: When It Is Truly Worth It

A relaunch is the fundamental renewal of an existing website. Unlike a pure redesign that only adjusts the looks, a full relaunch usually affects several layers at once: the visual appearance, the technical foundation, the content structure and often the underlying content management system. The goal is not to build something new for its own sake, but to structurally fix existing weaknesses and bring the site up to the current state of technology, design and law.

It is important to distinguish this from smaller measures. When only individual pages are revised, texts updated or colours adjusted, that is upkeep or a refresh. A relaunch goes deeper: the site often moves to a new system, the URL structure changes, templates are rebuilt and content is migrated. It is precisely this depth that distinguishes a refresh from a genuine restart – and exactly why a relaunch needs more planning than a quick design correction through ongoing maintenance.

A common misconception is that a relaunch is primarily a design task. In reality it is above all a strategic and technical one. The central question is not "How should it look?" but "What should the website do better than it does today?". Should it generate more enquiries, load faster, convince on mobile, become accessible or be easier to maintain? Only from these goals does it follow how deep the rebuild needs to go and which areas are touched at all.

Not every website needs to be rebuilt the moment it is a few years old. There are, however, clear signals that argue for a relaunch. The more of these points apply, the more likely the investment pays off – not as a cost item, but as a contribution to more visibility and more enquiries through the website.

A single one of these symptoms rarely justifies a complete rebuild. A slow site can often be improved by targeted performance optimization, an outdated text by a revision. But when several factors come together – say outdated design, lacking mobile usability and a system that can no longer be maintained – a relaunch is usually the more economical route, because patch repairs on a brittle foundation rarely last long. Which option makes sense in your case is best clarified by a sober look at the current state in an initial consultation.

Speed is not a technical detail but a business factor. Research by Google and SOASTA shows that the probability of a bounce rises sharply the longer a page takes to load: as load time grows from one to three seconds, the bounce probability increases by around 32 percent (Google/SOASTA), and even more at five seconds. Across all mobile pages, around 53 percent (Google) of users leave a page that takes longer than three seconds to load. These figures are averages and vary by industry, but the direction is unambiguous: slow pages lose visitors before they even see the content.

Google measures this user experience through the Core Web Vitals – specifically the Largest Contentful Paint (loading feel), the Interaction to Next Paint (responsiveness) and the Cumulative Layout Shift (visual stability). These values feed into search results as a ranking signal. A relaunch is the natural moment to lay these foundations cleanly: lean templates, optimized images in modern formats, sensible caching and reliable hosting in Germany. The technical background is explored in our article on website costs.

Mobile usability is just as important. Google evaluates websites primarily in their mobile version (mobile-first indexing). A page that is hard to use on a smartphone therefore has not only a user problem but also a visibility problem. A modern relaunch builds the mobile experience in from the start: legible font sizes, sufficiently large touch areas, a menu that can be operated with the thumb and content that appears in the right order even on small displays.

Since 28 June 2025, the Accessibility Strengthening Act (BFSG) has applied in Germany. It obliges many providers of digital products and services to make their offerings accessible – including numerous online shops and bookable services in the consumer business. A relaunch is the most pragmatic moment to implement these requirements, because accessibility is best designed in from the ground up and can only be retrofitted into an existing site with considerable effort.

Accessibility follows the Web Content Accessibility Guidelines (WCAG 2.2) at conformance level AA. This includes sufficient colour contrast, full keyboard operability, meaningful alternative texts for images, a logical heading structure and correct markup of forms for screen readers. These measures help not only people with disabilities but also improve clarity and structure for all visitors – and often the way search engines process the site.

The biggest risk of a relaunch is the loss of search visibility. Over years, a website has built trust with Google: individual URLs rank for certain search terms, external sites link to specific subpages, users have set bookmarks. If the URL structure changes during the relaunch without the old addresses being cleanly redirected to the new ones, all these connections break. The result is error pages, lost rankings and a noticeable drop in organic traffic – often exactly where most enquiries came from before.

The technical core against this loss is a complete redirect plan using 301 redirects. Every old URL that changes or disappears must be permanently (status code 301) redirected to the thematically matching new address. This transfers the accumulated trust and existing links to the new structure. It is important that an old page is redirected to its content counterpart and not blanketly to the home page – otherwise the effect fizzles out and Google rates the redirect as unhelpful.

Besides redirects, there are further SEO traps. An accidentally active block for search engines (such as a restrictive robots.txt or a forgotten noindex from the development environment) can remove an entire site from the index overnight. Lost metadata, changed heading structures or missing alt texts also weaken search engine optimization. A well-considered relaunch therefore transfers not only the content but also title tags, meta descriptions and structured data – and systematically checks after go-live whether the new site is fully indexable.

A relaunch follows a clear process that keeps the risk manageable and carries over the substance of the old site. It starts with an audit: which pages exist, which bring traffic and enquiries, which content is outdated, where do the technical and design weaknesses lie? This analysis is the basis for all further decisions and should include search-engine data, analytics figures and a technical crawl of the existing site.

The analysis is followed by the concept. Here the goals are defined, the new site structure (information architecture) is designed, the URL mapping is prepared and the design direction is set. Only then does the actual implementation with design and development begin. During this phase the new site is built on a protected development environment that is unreachable for search engines, so that no duplicates enter the index. The way we generally approach web design projects can be applied to a relaunch.

The go-live itself is not the end but the start of an important observation phase. In the first days and weeks after the switch, rankings, crawling errors, indexing status and traffic should be monitored closely. A short, mild fluctuation effect after a relaunch is normal, because Google first has to re-crawl and re-evaluate the new structure. If the effect stays away or visibility recovers quickly, the migration was clean. This is exactly where the combination of a prepared redirect plan and continuous monitoring through maintenance pays off.

Before the first line is built on the new system, the old website belongs fully backed up. A relaunch is an intervention in a grown system, and nothing is more annoying than discovering after go-live that an important piece of information is irretrievably lost. A complete backup covers not only the files and the database but also the less visible data that makes up a website's digital capital.

Documenting the initial state in particular is often underestimated. Anyone who fails to record before the relaunch how many visitors the site had, which pages brought the most enquiries and which search terms ranked well will find it hard afterwards to judge whether the rebuild was successful. These figures are also the basis for targeted adjustments after go-live, should individual pages lose visibility. A sober before-and-after comparison replaces gut feeling with reliable numbers.

Not every problem requires a complete rebuild. Before deciding on a relaunch, an honest weigh-up against targeted individual measures is worthwhile. A slow but still design-viable site sometimes benefits more from focused performance optimization than from an expensive complete rebuild. Conversely, it makes little sense to invest a lot of money in a site whose technical foundation is at the end of its life.

From more than 50 web and relaunch projects (project experience) we know that the most honest answer is often a combination: preserve proven content and good rankings, renew the technical foundation and bring the design up to today's standard. Which route is the most economical in your case depends on the state of the existing site, your goals and your budget. A sober look at the figures and a comparison with concrete reference projects quickly bring clarity here, before effort flows in the wrong direction.

For online shop operators, additional considerations apply, because here, besides visibility, carts, customer accounts and payment processes can be affected as well. A shop relaunch based on Shopware Community Edition combines the open, vendor-independent platform with a clean migration concept – how such a shop is built is shown on our online shop page. Here too the rule applies: first back up the data, then migrate cleanly, then monitor closely.