A website rarely dies on a specific day. It ages — quietly, mostly. At some point, somebody on the team asks: "Should we rebuild this?" And then, often, one of two wrong answers comes back: "Ah, the old one's fine" or "Just do it completely new, but fast and cheap."
Both answers cost money in the end. A relaunch is an investment that only pays off if you know why you're making it. Here are the signals that, from working with clients, actually matter.
The signals that mean something
Your site loads slowly on a phone
That's the clearest signal. Over half your visitors come from mobile. If your site takes three, four, five seconds to load there, most of them bounce — long before they've read anything. Google has ranked slow pages noticeably worse for years, and that's not getting better.
If you want it more precise: Google's PageSpeed Insights shows you, for free, where your site stands. A mobile score clearly below 70 is a warning. Clearly below 50 is an emergency.
It doesn't work properly on a phone
Worse than slow: text you can't read without zooming. Buttons too small for a finger. Menus that won't open. A contact page where the form disappears on iOS.
That's not just embarrassing, it costs you customers. Anyone who can't send an enquiry from their phone won't send it from a laptop either — they'll go to the next provider.
It looks like 2018
Design trends come and go, and that's fine. But a website that looks like a specific decade reads to customers like a shop where the calendar on the wall has stopped. The question isn't: "Is this still modern?" The question is: "Does this look like someone is still taking care of it?"
If the answer's no, you're losing trust before you even get the chance to earn it.
You can't maintain it yourself any more
One of the most expensive traps: a website that only a single person can change — and that person may no longer be at the company, may no longer be reachable, or may now charge €120 an hour for a text edit.
When every small request becomes a project order, eventually nothing happens at all. The site ages faster than it needs to. A relaunch with a CMS you can run yourself gets you out of that.
It no longer shows up on Google
You used to get enquiries through the website. Now, fewer. Before you suspect "the industry is changing" or "customers come from somewhere else": check whether your site is even being found any more. Google Search Console shows you which searches you appear in and how often you get clicked. If the curve has been steadily downward over the last two years, it rarely has anything to do with the industry.
It doesn't reflect what you actually do any more
You've added new services, dropped old ones, your team has changed, your focus has shifted — and the website still shows everything from 2019. That's not just inaccurate, it's a missed opportunity. Your website is the first impression for many customers. If the first impression lies, what will they believe you on?
There are recurring small technical problems
Broken links. Forms that sometimes don't arrive. Browser security warnings. Outdated plugins that won't update. Individually, small things. Taken together: a sign that the foundations are getting brittle. Eventually the big bill arrives — usually as a cease-and-desist or as a hacked site.
What a relaunch doesn't fix
Just as important: a relaunch isn't a miracle cure.
It doesn't fix a marketing problem. If nobody knows you exist, even the most beautiful website won't help. A new site alone doesn't bring you new customers — it just makes things easier for the ones who'd find you anyway.
It doesn't fix a pricing problem. If you're too cheap, a new website won't change that. Often it's the other way round: a professional website is what gives you the confidence to justify your prices in the first place.
It doesn't fix a broken product. If your offer isn't right, better packaging won't make it better. The offer first, then the website.
A relaunch pays off when the site is actively holding back growth. If it isn't the problem, it won't solve the problem.
How a relaunch actually runs
I do this regularly, and here's the version I think is honest — not the checklist with eight clean steps that every agency has on their site.
Talk first, then build. Before anyone opens a design tool, we clarify: what do you want to achieve? Who are your customers? What works on the old site, what doesn't? What are the three most important enquiries the site should generate? Without these questions, every relaunch is a gamble.
Content before form. Most people think about design when they think relaunch. I think first about the content structure: which pages do you need, what goes on them, in what order. Good design doesn't solve a content problem — it just makes it prettier.
Design as an answer, not as taste. Design decisions should come from the content and the requirements, not from "I like blue". Set up the process like that and you end up arguing less about taste and more about function.
Build, test, correct. Then comes the actual implementation. Responsive, fast, properly tested on real devices — not just on the developer's MacBook.
Launch without drama. A 301 redirect strategy, so old links don't go nowhere. Resubmit sitemaps to Google. A week after launch, check whether everything arrives that's supposed to arrive. Most relaunches don't fail at the design stage, they fail at these details.
After that, it continues. A relaunch is a starting point, not a finish line. Anyone who leaves the site to itself after that has the same problem again in three years. Maintenance, small updates, fresh content now and then — that's the normal operation of a website that's meant to work.
What a relaunch costs
This is hard to answer generally — because it depends on what you had before and what you want afterwards. A relaunch of a small five-page company site typically sits between €3,000 and €8,000, depending on how much of the copy gets rewritten, how much custom design, how many features.
A relaunch that simultaneously introduces a new brand, a new CMS, and new features quickly reaches five figures. More on that in the post on what a website costs.
The rule of thumb I give clients: plan for double what you first imagine. Not because developers want to fleece you, but because things almost always come up in the process that nobody anticipated — and that turn out to matter.
The right moment
The short answer: before it hurts. Anyone who pushes a relaunch to the point of "we have to, right now" has already waited too long and pays the rush premium. Anyone who plans it while the old site still works but shows the first signals gets time, comparability, and a result that actually fits.
Three to four years is a sensible cycle for most company sites. Some last longer, if maintained. Some need shorter, if the business changes quickly. The question isn't: "How old is the site?" The question is: "Is it still working for me?"