What is a website relaunch?

A relaunch changes more than the visible surface

When we talk to teams about a relaunch, we often hear first: “We just need a fresh design.” And yes: First impressions count. But a relaunch is not the moment when you simply change the colors – it is the moment when you reorganize the whole house.

Definition as we use it in projects: A website relaunch is the comprehensive reimplementation of a website – usually involving changes to structure, content, design, and technology. A redesign, on the other hand, is often only the visual revision. Many guides draw the line in exactly the same way: With a relaunch, there is a “relaunch in all areas.” Ramoser Webdesign↗

The difference is practically relevant because it determines, how much risk and how much impact you bring into the project. A pure redesign can be cautious. A relaunch can be a fresh start – and it can turn out great if you know what you are doing.

The relaunch is a translation project

We see relaunches as translation: You translate your current business, your brand, and your offering into a digital form that people understand immediately. This affects things like information architecture, copy, interactions, forms, loading time, tracking – and, of course, Google as well.

A simple guiding question helps here, which we ask in almost every project (our method 1): “What should be easier for users after the relaunch than before?” If you do not have a clear answer to that, the relaunch quickly becomes a matter of taste.

And one more thing that is often underestimated: The website is the most important marketing channel for many companies. 91 percent of companies say exactly that. Digital Silk↗ If the website is that important, then a relaunch is not cosmetic – but a strategic decision.

Rebuilding is only worthwhile when there is genuine structural friction

There is a moment we experience in almost every relaunch consultation: Someone on the team says “The site still works, after all.” And someone else says “Yes, but it’s working against us.” The truth lies exactly between these two sentences.

A relaunch is rarely worthwhile because something is “old”. It is worthwhile when costs, risks or missed opportunities become greater than the investment.

Signals we take seriously

A strong signal is conversion: Many relaunches get started because the website closes too few deals. In one survey, 80.8 percent said that a conversion rate that was too low was the trigger. Sixth City Marketing↗ In practice, this looks like: There is traffic, but inquiries fail to materialize. Or inquiries come in, but they are the wrong ones.

A second signal is patience. If a page takes longer than three seconds to load, around 40 percent of visitors leave again. Sixth City Marketing↗ This is not a “performance issue”, it is an issue of trust and relationships. Nobody likes to wait.

And then there are the quiet signals: Editorial work takes forever because the CMS is cumbersome. Tracking is unreliable. The site is not accessible, even though since 2025 many industries have been under significantly greater obligations due to the European Accessibility Act (even if details vary depending on the offering and target group).

Our decision aid: Repair or rebuild?

Here comes our method 2, which works surprisingly well in many projects: “Keep what works – renew what slows you down.” It sounds banal, but it is a real antidote to actionism.

We look at three things with you: What demonstrably generates leads or trust (e.g. pages that have performed organically for years)? What continuously causes friction (e.g. load time, maintenance, bounce rates)? And what no longer fits your brand (e.g. tone, images, positioning)? This often results in a clear plan: Sometimes it is a relaunch. Sometimes it is a focused redesign plus technical remediation.

What matters is: A relaunch is not a mandatory program every two years – but many companies revise their websites in 2–3-year cycles. Walker Sands↗ If you wait significantly longer, it usually does not become cheaper, but more confusing.

Goals need signals before design begins

Design is visible – but the reasons why relaunches fail are usually invisible: unclear goals, missing data, too many opinions, too little responsibility.

Before we move into implementation, we therefore need a shared picture of what “good” actually means. And in a way that you can check after the launch.

Success criteria that really help

We like to work with a small selection of KPIs that together provide a complete picture. Not because numbers are everything – but because they take the heat out of discussions.

First: Business impact. This can be inquiries, demo bookings, newsletter opt-ins or sales. Many teams start relaunches for conversion reasons; that is measurable and legitimate. Sixth City Marketing↗

Second: Visibility. Which pages currently bring in organic traffic? Which search queries are valuable? This is where Google Search Console is worth its weight in gold.

Third: Experience. We don't mean “Do we like it”, but: Do people find what they are looking for faster? Do they abandon less often? Do they stay longer? Qualitative signals also help here: support tickets, feedback from sales conversations or small user tests.

Fourth: Trust. 75 percent of users judge a company's credibility based on its web design. Sixth City Marketing↗ Trust is reflected, for example, in contact rates, repeat visits, and willingness to share data.

Our “Before-and-After” routine

So that you don't just hope it gets better, we use a simple routine in relaunches (Method 3): Before the project starts, we create a Baseline. Load times, top landing pages, conversions, visibility, frequent search queries, technical errors. After the relaunch, we measure the same points again – after 1 week (find errors), after 4 weeks (stability), after 12 weeks (trend).

This takes pressure off launch day. And it ensures that you don't experience the relaunch as a one-off event, but as the starting point for controlled improvement – that is exactly where long-term impact is created.

Five phases make the big leap manageable

A relaunch often feels like a leap: old today, new tomorrow. In practice, it is more like a sequence of decisions that you need to put in order.

We like to structure relaunches into five phases. Not as a rigid process poster, but as a guide so that nothing important gets lost “between design and launch”.

1 Analysis and inventory

First, you want to know what you actually have: Which pages exist, which work, which are ballast? This is where Google Search Console and GA4 plus a crawl with Screaming Frog. This inventory also produces the list of all old URLs – later the basis for redirects.

2 Concept and information architecture

Now you organize the offering so that people understand it. We pay close attention to clarity here: few levels, descriptive URLs, sensible entry points. And we bring in a Pola topic that many guides leave out: Access for everyone. Accessibility is not a later refinement, it influences structure, components and texts from the very beginning.

3 Design as a promise of usability

Design is not decoration, but a promise: “You’re in the right place here, you’ll reach your goal here.” The first impression is formed extremely quickly – studies cite 50 milliseconds. Website Optimization↗ That is exactly why we always connect design with content and interaction: What should someone do next? What do they need to say yes?

4 Build and content migration

Now it gets technical. CMS, components, templates, performance. And in parallel: content. This is often the bottleneck. If texts, images, downloads, metadata and internal links are not ready in time, your schedule falls apart.

5 Launch and stabilization

The launch is not the final full stop. We always plan a follow-up phase in which we fix errors, check SEO signals, verify tracking and respond to user reactions. This is exactly where it is decided whether the relaunch is not only “online”, but also effective .

If you take this as a roadmap, a relaunch suddenly feels less like a risk – and more like a project you can control.

Google loses its bearings when familiar signals disappear

The SEO fear is real. Not because Google “penalizes relaunches”, but because a relaunch changes many things that Google has learned as stable over the years: URLs, internal links, content priorities, technical signals.

If you introduce new URLs in a relaunch and let old ones disappear, this is initially a loss for Google. Without clear migration logic, 404 pages arise, signals lead nowhere, backlinks lose their effect. This happens faster than you might think.

A prominent example is Frankfurt.de: Despite lengthy planning, the site lost around 50 percent visibility after the 2020 relaunch. factor.partners↗ Our point here is not schadenfreude, but humility: If a project like this can stumble, any project can.

What’s behind it

Google evaluates pages URL by URL. Every URL collects signals: relevance, links, user signals. If you rename everything, you force Google to learn again.

And even if you do everything right, things can wobble in the short term because a new structure first has to be crawled and classified again. That’s normal. What’s dangerous is when the wobbling never ends.

The biggest SEO trap isn’t technical

In practice, we see the toughest SEO trap not in server configs, but in content: During a relaunch, things get “cleaned up” – and suddenly exactly the pages that have driven organic traffic are missing. Or texts are simplified so much that they may look nice, but no longer answer what people were searching for.

Our countermeasure is simple, but effective: We don’t treat SEO as a checklist at the end, but as an inventory at the beginning. Which pages bring traffic? Which search queries bring the right people? If you know that, you can consciously decide what stays, what gets merged and what gets a new, better page.

And yes: A relaunch can also have a positive effect. The domain move from real.de to kaufland.de was implemented cleanly and led to growth of over 20 percent. factor.partners↗ This shows: SEO is not fate. It’s craftsmanship.

Every old URL needs a clear new destination

If you take only one thing “technically” seriously during the relaunch, make it this: Moves must be traceable. For people – and for search engines.

We use a practice for this that we like to call “URL accounting” internally. Not because we love numbers, but because it prevents chaos.

Our four-step approach

1) Crawl everything that exists. With Screaming Frog you export all old URLs, including status codes and metadata.

2) Every important URL gets a destination. This is the redirect mapping. Old service page to new service page, old blog article to new article or a thematically relevant overview page. We avoid “Everything to the homepage” because that is rarely useful for users and Google.

3) Implement and test 301 redirects server-side. Without 301s, the damage can be brutal: A documented case shows a 66 percent loss in visibility and a 37,000 euro loss in revenue per week, caused by missing redirects. SageMedia↗

4) Monitor closely after launch. In Google Search Console we check indexing, crawling errors and sitemaps. In Analytics, we check whether conversions and events are firing properly. And we keep an eye on the most important keywords – not hourly, but regularly.

What many forget: the “side links”

SEO migration affects more than just Google. A relaunch also breaks links from ads, newsletters, PDFs, social profiles, and partner sites. That’s why we also create a short “link maintenance” list in parallel: the 20 most important external places that need to be updated after go-live.

A calm launch is usually the best

We like to plan relaunches so that you don’t go live in the middle of the biggest campaign window. A “soft launch” in a quieter week gives you room to catch unexpected effects.

If you consistently follow these four steps, there’s a good chance your relaunch won’t end as an SEO shock, but as a smooth transition. And that’s exactly what it’s about: no magic – just care.

Less data means more speed and lower consumption

When we talk about performance at Pola, we don’t just mean “better scores”. We mean: less frustration, fewer drop-offs – and less digital waste.

One figure we like to use as a reality check: On average, around 6.8 grams of CO₂ are cited for a page view. analytik.news↗ Whether the figure is higher or lower in an individual case depends heavily on data weight, device, and hosting. But the direction is clear: Heavier pages consume energy.

Why this is a relaunch topic

In everyday use, a website often grows unnoticed: new tracking scripts, larger images, additional fonts, embedded videos. Every small request seems harmless. Together, it becomes heavy.

During a relaunch, you have the rare opportunity to consciously reduce. Our approach is very concrete:

• We check the data weight per page type (homepage, landing page, blog) and set a budget.
• We question scripts: What do we really need? What is just habit?
• We choose modern image formats (AVIF or WebP) and make sure to use true responsive images.

And: We talk about hosting. If you’re moving anyway, it’s often a good time to switch to a green electricity or green hosting model. That’s not the only lever – but it’s an easy one to pull when things are being rebuilt anyway.

Core Web Vitals as a common language

For teams, it’s helpful to make performance tangible. The Core Web Vitals and tools such as PageSpeed Insights or Lighthouse are well suited for this. The effect is not just “SEO”. It’s human: when a page responds noticeably faster, it is perceived as more reliable.

And right here lies a fresh perspective that we rarely see in relaunch checklists: Performance is also an attitude. You decide whether your website respects attention – and whether it respects resources.

Early decisions make access more affordable

Accessibility is often treated as an additional task: „We’ll do that later.“ Our experience is: Later becomes more expensive – and worse.

Since 2025, accessibility has been much more strongly in focus in Europe, because the European Accessibility Act has shifted from „nice“ to „necessary“ in many areas. Even if not every company is directly required to comply, expectations have clearly risen: Users compare. And many people have always been there – they were just excluded far too often.

Why a relaunch is the best time

During a relaunch, new components are created: buttons, forms, navigation, cards, accordions, cookie banners. These building blocks determine whether a site can be operated with a keyboard, whether screen readers can make sense of it, whether contrasts are correct.

If you retrofit this only after the design, you have to rebuild the foundations. If you plan it from the start, it becomes part of your system.

Our practical approach: accessibility as a design system rule

We like to build accessibility into rules, not individual „fixes“. Specifically:

1) Contrast and typography are defined early, so that later not every page has to be discussed again.

2) Components get clear states (focus, hover, error, disabled), so forms don’t become a stumbling block.

3) We test early and simply: with a keyboard, with a screen reader spot check, with tools like axe DevTools or WAVE. These tools don’t replace a full audit, but they prevent the typical beginner mistakes.

For us, accessibility is not a „compliance block“, but a question of respect. And it fits surprisingly well with conversion: A clear, understandable interface helps everyone – not just people with disabilities.

If you’re planning a relaunch, this is the opportunity not just to say „access for all“, but to translate it into navigation, content and interactions.

Good structure starts with an honest inventory

The most underestimated part of a relaunch is rarely the design – it’s the question: What do we keep, what do we delete, what do we rewrite?

We’ve seen relaunches that were technically clean but still didn’t perform. Not because Google was evil, but because the new content suddenly no longer provided a clear answer.

Content is not quantity, but orientation

Many teams have “accumulated” things over the years: old landing pages, duplicate service pages, news posts, PDFs. The reflex during a relaunch is then: get rid of everything, start over.

Our experience: That’s risky. Google often rewards exactly the content that has built up trust over time. If you remove these pages, you also remove their signals.

Our method: Three classes instead of gut feeling

So that content decisions don’t get lost in endless discussions, we use a simple classification:

1) Pillars: Pages that demonstrably bring traffic, inquiries, or trust. These are prioritized for migration and improvement.

2) Misleaders: Pages that create false expectations or are unclear. These are rethought.

3) Baggage: Content without a purpose or with an outdated offering. These can go – but not without a trace. They need a clean redirect or a deliberate “farewell” strategy.

You can back these classes with data: In Google Search Console you can see which URLs are visible for which search queries. In GA4, you can identify which pages appear in journeys that lead to conversions.

Information architecture as brand work

Here’s a perspective that we find particularly important as a branding and product team: Structure is language. If your website is just a list of menu items, the thread is missing. If, on the other hand, it has a clear dramaturgy, it becomes digital brand management.

A relaunch is therefore often the moment when you decide: Do you just want to store information – or do you want to guide people? This is particularly noticeable for Purpose Brands: values don’t have to appear in a paragraph, they have to be visible in decisions. For example, in how transparently you talk about impact, how clearly you explain offerings, and how little distraction you allow.

This is the point at which a relaunch really becomes “new”: not just new pages, but new clarity.

The first public day needs a test plan

Launch day is emotional. For weeks, everything is “almost finished”, and suddenly it’s public. That’s exactly when the mistakes happen that you’d later most like to undo: a form that doesn’t submit. Tracking that counts nothing. A robots.txt that accidentally blocks everything.

To prevent that, we treat the launch like a small, deliberately planned handover – not like a moment when you simply press “Publish”.

A test plan that doesn’t get out of hand

We like to keep testing lean, but consistent. A good plan doesn’t need to be 80 pages long. It needs to cover the few things that carry your business:

1) Test critical journeys (contact, purchase, booking, newsletter) in at least two browsers and on mobile.

2) Verify tracking: Are events firing in GA4? Are conversions coming through? Are consent settings correct? A quick check with the browser debugger or Tag Assistant often helps here.

3) SEO checks after go-live: Crawl, 301 chains, 404s, canonicals, sitemap submission in Search Console.

4) Performance spot check with PageSpeed Insights on the most important page types.

Post-launch follow-up is not a luxury

We always plan a stabilization phase after the relaunch. Why? Because rankings can fluctuate, because users do things no team could have anticipated, and because real-world usage is different from staging.

This mindset is underrepresented in many guides: A relaunch is not “finished” when it goes live. It is finished when it is stable .

And if you want to take a little pressure off yourself: Perfection is not a sensible launch requirement. What matters is that the foundations are in place. Everything else gets better when you measure, observe and iterate.

That is how a relaunch becomes not a feat of strength that hurts every two years – but a step toward a website that is allowed to live and grow with you.