Not every old website needs a full rebuild. And not every old website deserves another two years of patching holes. Sometimes it is enough to improve the structure, refresh the design, clean up the content and fix years of technical neglect. Sometimes, though, you are trying to turn a car into something modern when it has fresh paint, shiny new wheels and a frame that still remembers three previous crashes. You can do it. The question is how many more times you want to pay to straighten the same frame.

A website redesign sounds harmless enough. In practice, that label can mean anything from a cosmetic refresh to an almost complete rebuild while keeping the domain, some of the content and existing Google visibility. So before you start asking about price, there is a more basic question to answer: what is actually worth saving from the current website? Not because old automatically means bad. Because once technical debt reaches a certain point, the cost of preserving the old system starts exceeding the value of what you are preserving.

A redesign makes sense when the foundation is healthy

If the current website has a sensible technical structure, the content still reflects the business, the URLs are logical, the CMS can still be developed and the main problems are an outdated design, weak navigation or untapped SEO potential, a redesign can be exactly the right move. There is no prize for throwing away a working system just because someone said, “let’s rebuild everything from scratch”. You do not replace the engine in a car just because the upholstery remembers the Nokia 3310 era.

WebsiteGarage / Services

Explore our services.

In that situation, keep what has real value: the domain, established URLs, content that already brings traffic, working integrations, analytics data and elements users already know. A website redesign should not be a competition to see who can delete the most. It should be a controlled change that improves what works badly without wrecking what already works well.

A new website makes sense when the old system dictates every decision

The worst point is when every new idea starts with: “we can’t do that because the old website…”. We cannot change the structure because of the theme. We cannot simplify the form because of the plugin. We cannot improve mobile because of the page builder. We cannot touch the checkout because something might break. We cannot update because one plugin stopped existing in 2021. That is no longer a system supporting the business. It is the thing holding the business back, only with an admin panel.

If the information architecture was built for a company that sold three services five years ago and now sells twelve; if WordPress is wrapped in random code snippets, builders and dependencies nobody wants to touch; if the database contains years of junk, there is no staging environment and production updates follow the “click it and see what happens” method, another visual refresh may do nothing more than put a clean shirt on the same problem. Technically, the site will look new. Operationally, you are still driving a car where the stereo is worth more than the gearbox.

The most important question: what exactly is wrong with the current website?

If the answer is “it looks ugly”, you probably do not need a full rebuild straight away. If the answer is “it is unusable on a phone”, you need to find out whether the problem is the design or the underlying structure. If “Google cannot find us”, you need a technical and content audit, not automatically a new website. If “every change takes half a day because nobody knows what will break”, the problem runs much deeper.

A good redesign decision starts with diagnosis, not a hero-section mockup. Before anyone chooses fonts and gradients, they should check the URL structure, organic traffic, content, conversions, user behaviour, technology, dependencies, integrations and the state of the CMS. If the old site has good parts, keep them. If it has bad parts, do not carry them into the new project just because “that is how it was before”. Migrating a mess still leaves you with a mess, just on a new server.

SEO during a website redesign: the easiest thing to lose is what nobody inventoried

One of the most expensive mistakes in a website redesign or rebuild is treating old URLs like renovation debris. The team builds a beautiful new structure, launches the site and then someone notices that URLs which spent years accumulating rankings and links now return 404s or have all been redirected to the homepage. It is a bit like moving an entire company and throwing away the only customer address book because it was printed on old paper.

A redesign should therefore include a map of the old and new site, plus decisions about what stays, what gets merged, what gets removed and where redirects should point. You need to know which pages have traffic, external links and actual business value. Not everything needs to survive. But removing something should be a decision, not the accidental result of a developer not knowing the URL existed.

Not every redesign needs a rebrand, and not every rebrand needs a redesign

Companies love throwing several problems into one project. If we are touching the website anyway, maybe we should get a new logo. If we get a new logo, we need new messaging. If we change the messaging, let’s change the offer. If we change the offer, maybe the CRM too. And before anyone notices, a website project has turned into an organisational transformation while the budget still looks like it was meant for a homepage and five subpages. Sometimes that makes sense. More often, it is better to separate things that genuinely depend on each other from things that are simply tempting because “we are already making changes anyway”.

When I would say: fix it

I would fix the existing site if the system is current or can be updated reasonably safely, the database and code do not look like an archaeological dig, the content structure still makes sense and the main problem is design, UX, performance or a few missing features. I would also fix it when the site already has strong visibility and plenty of valuable content, and the changes can be introduced in stages. There is no reason to tear a house down to the foundations just because the kitchen is from 1998.

When I would say: rebuild it

I would rebuild if the technology is blocking growth, nobody can update the system safely, the current architecture no longer reflects the business, every change needs a workaround for another workaround, or repair costs are starting to look like a fine-dining bill served in a room with a hole in the floor. Especially if the company is planning new processes, integrations, multiple languages, online sales or a major increase in content. In that situation, keeping the old foundation may only look cheaper.

And if you are not sure? Audit first, quote second

You do not need to know whether you need a redesign or a rebuild. That should be assessed by someone who can evaluate the current state properly. I really dislike the model where a client says, “I think I need a new website”, and fourteen seconds later the provider replies, “yes, a new website will cost €4,990”. Maybe the client genuinely needs a new website. Maybe they need two days of competent work on the existing one. Selling the biggest product before doing any diagnosis is about as sensible as replacing an engine because the car started pulling to the right.

A website redesign makes sense when the decision comes from the problem, not the age of the site. A new website makes sense when the old one has stopped being a foundation and started being a constraint. In both cases, the most expensive mistake is the same: designing the solution before anyone has properly checked what is actually broken.