A website does not need a relaunch simply because it is a few years old. What matters is whether it clearly represents the business today, works reliably and guides visitors towards the right next step.
A relaunch makes sense when the existing website can no longer fulfil its business purpose without fundamental changes to its structure and technical foundation.
A targeted update is often enough when the technical foundation is sound and only certain content, pages or user journeys no longer fit. A full relaunch makes sense when the offer, positioning, site structure and technology no longer work together. In that situation, a more modern layout only changes the surface.
Decision matrix
The right approach depends on the specific problem. This comparison provides an initial assessment.
| Option | When it fits | Typical scope | Key question |
|---|---|---|---|
| Ongoing maintenance | Objectives, structure and technology are working. | Texts, images, case studies and minor technical corrections. | Is the information accurate and up to date? |
| Targeted update | The foundation is sound, but individual pages or user journeys no longer work. | Refine the positioning, reorganise content and improve navigation or forms. | Which focused change solves the specific problem? |
| Full relaunch | The business model, information architecture or technology no longer fit together. | Rebuild the strategy, page roles, content, design, technology and migration plan. | What website does the business need today? |
The table is a guide. The decision should be based on an inventory of pages, technology and content.
From our work
Whether a full relaunch is necessary becomes clear from the tasks a website has to bring together. Two published projects show the difference between a new appearance and a newly organised foundation.
Law firm · Aachen
The static relaunch brought eleven practice areas, four lawyer profiles, the firm's history, downloads and contact paths together in a consistent structure. A visual update alone would not have been enough: content, user journeys and the technical foundation had to be reorganised together.
View the LWB projectSecurity technology · B2B
For HTsecurity, complex security services were reorganised both structurally and visually. The relaunch created a sound foundation for navigation, service presentation and subsequent technical and content-focused SEO support.
View the HTsecurity projectThese examples document the project tasks and implementation. We only state ranking or enquiry outcomes when a current, dated measurement supports them. Further insights are available under Web design and relaunch.
Five signals
A single shortcoming rarely requires an immediate rebuild. The combination of these signals shows how extensive the change needs to be.
New services or target groups are often simply added. If visitors see plenty of information but cannot identify the right offer, the old structure no longer supports the new positioning.
Service pages, case studies, guides and contact pages each need a distinct role. If several pages say the same thing, the information architecture needs to be reorganised.
Warning signs include unclear responsibilities, outdated dependencies or changes that cause errors elsewhere. The key question is whether the foundation can still be maintained and extended in a controlled way.
Navigation, readability, forms and calls to action must work reliably on small screens. The entire journey is reviewed, from the search query to confirmed contact.
A relaunch changes content, internal links and sometimes URLs. Before implementation begins, it requires a URL inventory, a mapping from old to new destinations, permanent redirects, current canonicals, updated internal links and a controlled sitemap. A relaunch therefore does not end when the new layout is uploaded.
Process
This process keeps strategy, design and technical migration aligned.
Inventory pages, URLs, content, forms, integrations and measurement data.
Define the question, target audience and next step for every important page.
Plan navigation, offers, supporting evidence and contact paths before designing layouts.
Bring design, technology, performance, privacy and forms together.
Test URLs, redirects, data, links, forms and presentation.
Starting again does not mean discarding everything that already exists. Content that answers questions well, working URLs, genuine case studies and reliable forms can all be valuable.
Conclusion
A website should be rebuilt when its existing structure no longer supports the business as it operates today and targeted changes can no longer solve the problem. Focusing only on a new appearance overlooks the value that should be preserved.
Primary source
For URL changes, Google recommends mapping old URLs to their new destinations, using server-side redirects, updating internal links and monitoring the migration afterwards. Larger changes should be divided into manageable steps where appropriate.
Google Search Central: Site Moves and MigrationsFAQ
Next step
Together, we identify which parts of your website are working, where friction occurs and which approach genuinely makes sense.