TM
February 12, 2026
|
14 min read


A website relaunch is rarely "just" a new layout. It usually involves an overhaul of brand, content, technology, processes – and the signals Google has learned over the years.
Typical triggers include: too few inquiries, outdated CMS, weak performance, or a brand that has evolved. The biggest risks lie in SEO losses due to URL changes, overlooked content, and lack of coordination.
If you plan meticulously, you'll gain something invaluable in return: more clarity, better user guidance, higher conversions, measurable performance – and a website that's easier to maintain long-term.
SEO Migration
UX
Content Audit
Performance
Accessibility
Redirects
Core Web Vitals
CMS Change
Tracking
Green Web
When we talk to teams about a relaunch, we often hear first: "We need a fresh design." And yes: First impressions count. But a relaunch is not the moment you only change colors – it's the moment you reorganize the entire house.
Definition as we use it in projects: A website relaunch is the complete overhaul of a website – typically involving changes to structure, content, design, and technology. A redesign is often just a visual update. Many guides draw the same line: A relaunch involves a "reintroduction in all areas." <cite data-type="source" data-url="https://www.ramoser-webdesign.com/ratgeber/website-relaunch">Ramoser Webdesign</cite>
The difference is practically relevant because it determines how much risk and impact you bring into the project. A pure redesign can be gentle. A relaunch can be a fresh start – and it can be great if you know what you're doing.
We see relaunches as translation: You translate your current business, your brand, and your offering into a digital form that people immediately understand. This involves things like information architecture, texts, interactions, forms, loading time, tracking – and also Google.
A simple guiding question helps, which we ask in almost every project (our Method 1): "What should be easier for users after the relaunch than before?" If you don't have a clear answer to that, the relaunch quickly becomes a matter of taste.
And something else that's often underestimated: The website is the most important marketing channel for many companies. 91 percent of companies say exactly that. <cite data-type="source" data-url="https://www.digitalsilk.com/digital-trends/website-design-statistics/">Digital Silk</cite> If the website is so important, then a relaunch is not cosmetics – but a strategic decision.
There's a moment we almost always experience in relaunch preliminary discussions: Someone on the team says, "The site still works." And someone else says, "Yes, but it's working against us." The truth lies right between these sentences.
A relaunch rarely pays off just because something is "old." It pays off when costs, risks, or missed opportunities become greater than the investment.
A strong signal is conversion: Many relaunches start because the website closes too few deals. In a survey, 80.8 percent stated that a low conversion rate was the trigger. <cite data-type="source" data-url="https://www.sixthcitymarketing.com/web-design-stats/">Sixth City Marketing</cite> In practice, it appears as: Traffic is there, but inquiries don't come. Or inquiries come, but they're 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. <cite data-type="source" data-url="https://www.sixthcitymarketing.com/web-design-stats/">Sixth City Marketing</cite> This is not a "performance issue," it's a trust and relationship issue. No one likes to wait.
And then there are the silent signals: Editorial work takes forever because the CMS is cumbersome. Tracking is unreliable. The site is not accessible, even though from 2025 many sectors will be much more obligated under the European Accessibility Act (even if details vary depending on the offer and target audience).
Here's our Method 2, which works surprisingly well in many projects: "Retain what's effective – renew what's holding you back." This sounds simple but is a real antidote to activism.
We look at three things with you: What demonstrably generates leads or trust (e.g., pages that have been organically sustaining for years)? What continuously causes friction (e.g., loading time, maintenance, bounce rates)? And what no longer fits with your brand (e.g., tone, images, positioning)? This often creates a clear plan: Sometimes it's a relaunch. Sometimes it's a focused redesign plus technical overhaul.
Important is: A relaunch is not a mandatory program every two years – but many companies revise their websites in 2–3-year cycles. <cite data-type="source" data-url="https://www.walkersands.com/article/why-companies-redesign-websites-every-three-years-on-average-or-do-they/">Walker Sands</cite> If you wait much longer, it usually doesn't get cheaper, but more confusing.


Design is visible – but the reasons why relaunches fail are often invisible: unclear goals, lack of data, too many opinions, too little responsibility.
Before we start implementing, we need a shared picture of what "good" actually means. And in such a way that you can verify it after the launch.
We like to work with a small selection of KPIs that together create a complete picture. Not because numbers are everything – but because they ease discussions.
Firstly: 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. <cite data-type="source" data-url="https://www.sixthcitymarketing.com/web-design-stats/">Sixth City Marketing</cite>
Secondly: Visibility. Which pages currently bring organic traffic? Which search queries are valuable? For this, the Google Search Console is invaluable.
Thirdly: Experience. We don't mean "Do we like it," but: Do people find what they are looking for faster? Do they have fewer drop-offs? Do they stay longer? Here, qualitative signals also help: support tickets, feedback from sales conversations, or small user tests.
Fourthly: Trust. 75 percent of users judge a company's credibility based on web design. <cite data-type="source" data-url="https://www.sixthcitymarketing.com/web-design-stats/">Sixth City Marketing</cite> Trust is reflected, for example, in contact rates, repeated visits, and willingness to share data.
To ensure you don't just hope it's better, we use a simple routine in relaunches (Method 3): We establish a baseline before starting the project. Loading times, top landing pages, conversions, visibility, common search queries, technical errors. After the relaunch, we measure again at the same points – after 1 week (find errors), after 4 weeks (stability), after 12 weeks (trend).
This takes the pressure off launch day. And it ensures that you don't experience the relaunch as a one-off event but as a starting point for controlled improvement – that's where long-term impact is created.
Let's quickly clarify if you need a relaunch or an update.
A relaunch often feels like a leap: old today, new tomorrow. In practice, it's more a series of decisions you need to sequence.
We like to structure relaunches in five phases. Not as a rigid process poster, but as orientation, so nothing important "disappears between design and launch."
First, you want to know what you actually have: Which pages exist, which work, which are ballast? Here, Google Search Console and GA4 plus a crawl with Screaming Frog help. From this inventory, a list of all old URLs emerges – later the basis for redirects.
Now you organize the offering so that people understand it. Here, we focus strongly on clarity: few levels, meaningful URLs, sensible entry points. And we introduce a Pola theme that many guides leave out: Access for all. Accessibility is not a later refinement; it influences structure, components, and texts from the start.
Design is not decoration but a promise: "You're in the right place, you'll reach your goal here." The first impression is made extremely quickly – studies cite 50 milliseconds. <cite data-type="source" data-url="https://old.websiteoptimization.com/speed/tweak/blink/">Website Optimization</cite> That's exactly why we always link design with content and interaction: What should someone do next? What do they need to say yes?
Now it gets technical. CMS, components, templates, performance. And simultaneously: Content. This is often the bottleneck. If texts, images, downloads, metadata, and internal links aren't ready on time, your schedule will collapse.
The launch is not the finish line. We always plan a follow-up phase where we fix errors, check SEO signals, verify tracking, and respond to user reactions. Exactly here it is decided whether the relaunch is not just "online", but also effective.
If you take this as a roadmap, a relaunch suddenly seems less like a risk – and more like a project you can control.


The SEO fear is real. Not because Google "punishes relaunches," but because a relaunch changes many things Google has learned as stable over the years: URLs, internal links, content focuses, technical signals.
If you introduce new URLs during the relaunch and let old ones disappear, it's a loss for Google initially. Without a clear relocation logic, 404 pages appear, signals run into the void, backlinks lose their impact. It happens faster than you think.
A prominent example is Frankfurt.de: Despite long planning, the site lost around 50 percent visibility after the 2020 relaunch. <cite data-type="source" data-url="https://www.factor.partners/insights/erfolgreicher-website-relaunch-die-alarmierende-rolle-der-seo">factor.partners</cite> Our point here is not gloating, but humility: If such a project can stumble, any project can.
Google evaluates pages URL by URL. Each URL collects signals: relevance, links, user signals. If you rename everything, you force Google to re-learn.
And even if you do everything right, it can wobble temporarily because a new structure needs to be crawled and reclassified. This is normal. It's dangerous if the wobbling never ends.
In practice, we see that the toughest SEO trap is not in server configs but in content: During the relaunch, "clean-ups" occur – and suddenly the exact pages that carried organically are missing. Or texts are simplified so much that they look pretty but no longer answer what people were looking for.
Our countermeasure is simple but effective: We treat SEO not 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 is merged, and what gets a new, better page.
And yes: A relaunch can also have positive effects. The domain migration from real.de to kaufland.de was cleanly executed and led to growth of over 20 percent. <cite data-type="source" data-url="https://www.factor.partners/insights/erfolgreicher-website-relaunch-die-alarmierende-rolle-der-seo">factor.partners</cite> This shows: SEO is not fate. It's craftsmanship.
If you take one "technical" aspect seriously during a relaunch, it's this: Moves must be traceable. For people – and for search engines.
We use a practice internally often called "URL accounting." Not because we love numbers, but because it prevents chaos.
1) Crawl everything that exists. With Screaming Frog, export all old URLs, including status codes and metadata.
2) Every important URL gets a target. This is the redirect mapping. Old service page to new service page, old blog post to new post or a thematically appropriate overview page. We avoid "everything to the homepage," as it's rarely meaningful for users and Google.
3) Implement and test 301 redirects server-side. Without 301s, the damage can be brutal: A documented case shows 66 percent visibility loss and €37,000 revenue loss per week caused by missing redirects. <cite data-type="source" data-url="https://www.sagemedia.de/webseiten-relaunch-ohne-rankingverluste/">SageMedia</cite>
4) Monitor closely after launch. In Google Search Console, we check indexing, crawling errors, and sitemaps. In Analytics, we check if conversions and events are triggered cleanly. And we keep an eye on the main keywords – not hourly, but regularly.
SEO migration affects not only Google. A relaunch also breaks links from ads, newsletters, PDFs, social profiles, and partner sites. We therefore create a short "link maintenance" list in parallel: the 20 most important external locations that need updating after go-live.
We 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 absorb unexpected effects.
If you execute these four steps consistently, the likelihood is high that your relaunch won't end in an SEO shock but as a smooth transition. And that's precisely the goal: no magic – just diligence.


Get a clear redirect plan before go-live.
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.
A number we like to use as a reality check: On average, about 6.8 grams of CO₂ is mentioned per page view. <cite data-type="source" data-url="https://analytik.news/blog/2019/165.html">analytik.news</cite> Whether the value is higher or lower in individual cases depends heavily on data weight, end device, and hosting. But the direction is clear: Heavier pages cost energy.
In everyday life, a website often grows unnoticed: new tracking scripts, larger images, additional fonts, embedded videos. Each small wish seems harmless. Together it becomes heavy.
During a relaunch, you have the rare opportunity to consciously reduce. Our approach is very concrete:
And: We talk about hosting. If you're moving anyway, it's often a good time to switch to a green power or green hosting model. It's not the only adjustment – but one that's easy to do when rebuilding anyway.
For teams, it's helpful to make performance tangible. The Core Web Vitals and tools like PageSpeed Insights or Lighthouse are suitable for this. The effect is not just "SEO." It's human: If a page responds noticeably faster, it's perceived as more reliable.
And here's a fresh perspective, rarely seen in relaunch checklists: Performance is also an attitude. You decide whether your website respects attention – and whether it values resources.


Accessibility is often treated as an extra task: "We'll do it later." Our experience is: Later it becomes more expensive – and worse.
Since 2025, accessibility in Europe has been much more in focus because the European Accessibility Act has shifted in many areas from "nice" to "necessary." Even if not every company is immediately obligated, expectations have significantly increased: Users compare. And many people have always been there – they were just too often excluded.
During a relaunch, new components are created: buttons, forms, navigation, maps, accordions, cookie banners. These elements determine whether a page is operable with a keyboard, whether screen readers make sense of it, whether contrasts are right.
If you retrofit that after design, you have to rebuild foundations. If you plan it from the start, it becomes part of your system.
We like to incorporate accessibility into rules, not individual "fixes." Specifically, this means:
1) Contrast and typography are set early, so that later not every page is renegotiated.
2) Components get clear states (focus, hover, error, disabled), so forms don't become stumbling blocks.
3) We test early and simply: with a keyboard, with a screenreader spot check, with tools like axe DevTools or WAVE. These tools don't replace a full audit, but they prevent the typical beginner mistakes.
Accessibility is not a "compliance block" for us but a matter of respect. It fits surprisingly well with conversion: A clear, understandable interface helps everyone – not just people with limitations.
If you're planning a relaunch, it's the chance to not just say "access for all," but to translate it into navigation, content, and interactions.
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 mean, but because new content suddenly provided no clear answers.
Many teams have "accumulated" over the years: old landing pages, duplicate service pages, news posts, PDFs. The reflex at relaunch is: Throw everything away and start anew.
Our experience: That's risky. Google often rewards exactly the content that has built trust over time. If you remove these pages, you also remove their signals.
To prevent content decisions from sinking into discussions, we use a simple classification:
1) Carriers: Pages that demonstrably bring traffic, inquiries, or trust. These are prioritized for migration and improvement.
2) Misleaders: Pages that set false expectations or are unclear. These are rethought.
3) Ballast: Content without purpose or with outdated offerings. These can go – but not without a trace. They need a clean redirect or a deliberate "farewell" strategy.
You can underpin these classes with data: In Google Search Console, you see which URLs are visible for which queries. In GA4, you recognize which pages appear in journeys leading to conversions.
Here's a perspective we find particularly important as a branding and product team: Structure is language. If your website is just a list of menu items, the red thread is missing. If it has a clear dramaturgy, it becomes digital brand guidance.
A relaunch is often the moment when you decide: Do you just want to store information – or guide people? For Purpose Brands, this is particularly noticeable: Values don't have to be in a paragraph; they need to be visible in decisions. For example, in how transparently you talk about impact, how clearly you explain offerings, how little distraction you allow.
That's the point where a relaunch becomes truly "new": not just new pages, but new clarity.


Launch day is emotional. For weeks everything is "almost ready," and suddenly it's public. That's exactly when the mistakes happen that you'd later like to undo: a form that doesn't send. A tracking issue that doesn't count. A robots.txt that inadvertently blocks everything.
To prevent this, we treat the launch as a small, consciously planned handover – not a moment where you just hit "publish."
We like testing to be lean but consistent. A good plan doesn't have to be 80 pages long. It needs to cover the few things that support your business:
1) Test critical journeys (contact, purchase, booking, newsletter) in at least two browsers and on mobile.
2) Verify tracking: Do events match in GA4? Are conversions arriving? Are consent settings correct? Often a quick check with the browser debugger or Tag Assistant helps.
3) SEO checks post-go-live: Crawl, 301 chains, 404s, canonicals, sitemap submission in Search Console.
4) Spot-check performance with PageSpeed Insights on the most important page types.
We always plan a stabilization phase after the relaunch. Why? Because rankings can fluctuate, because users do things no team foresaw, and because real usage is different from staging.
This attitude is underrepresented in many guides: A relaunch is not "finished" when it's online. It's finished when it's stable.
And if you want to take a bit of pressure off: Perfection is not a sensible launch ambition. What matters is that the cornerstones are in place. Everything else improves when you measure, observe, and iterate.
That's how a relaunch doesn't become a strain every two years – but a step towards a website that can live and grow with you.
If you want, we can outline the next steps for you.
Frequently asked questions about costs, duration, SEO, CMS, risks, and team roles – answered briefly and honestly.
Send us a message or book a non-binding initial consultation – we're excited to meet you and your project.
Our plans
Copyright © 2026 Pola
Learn more
Directly to
TM