Website Refresh or Complete Rebuild: Which One Do You Need?

"Our website looks old."

That sentence starts a lot of projects, and it hides two completely different problems with very different price tags.

Sometimes the site is structurally sound and simply looks dated — the digital equivalent of a house that needs painting. Sometimes the foundations are the problem, and no amount of new paint will help.

Getting this wrong is expensive in both directions. Rebuild when a refresh would have done and you have spent three times what you needed. Refresh when a rebuild was needed and you have spent real money to arrive at the same problems, slightly prettier.

What each one actually means

A refresh keeps the existing structure and technology. You change how it looks and reads: colours, typography, imagery, layout of existing pages, copy, calls to action. Sometimes you add a few pages. The plumbing stays.

A rebuild replaces the foundations. New structure, new templates, often new technology and hosting. You usually carry over the content that still works, but everything under it is new.

There is a middle option people forget: a rebuild of one section. You do not always have to choose between painting the whole house and demolishing it. Rebuilding just the service pages, or just the enquiry journey, is frequently the right answer and almost nobody proposes it.

Signs a refresh is enough

A refresh is likely the right call when:

• the site loads quickly and behaves properly on a phone;
• you can add and edit pages without asking a developer;
• the structure makes sense — services have their own pages, nothing important is buried four clicks deep;
• nothing is broken, it just looks like it was designed several years ago;
• your messaging has moved on but the site hasn't;
• you're rebranding — new name, colours or positioning — on a site that otherwise works.

If most of those are true, be sceptical of anyone proposing a full rebuild. You may be paying to replace things that were fine.

Signs you need a rebuild

Start considering foundations when:

• the site is slow and the causes are structural, not just big images;
• the mobile experience is genuinely poor rather than merely imperfect;
• every change requires a developer, so nothing ever gets updated;
• there is nowhere sensible to put a new service, location or landing page;
• the platform is no longer supported or receiving security updates;
• search engines struggle with the site — pages not indexed, duplicate URLs, a structure Google can't follow;
• it is cheaper to start again than to work out how the current site was built.

That last point deserves saying plainly. On older sites we sometimes find that understanding the existing code would take longer than replacing it. When investigation costs more than construction, rebuilding is the frugal choice, not the extravagant one.

Security is not optional here. An unsupported platform stops receiving patches, and "it still works" is not the same as "it is still safe". That one is a rebuild trigger on its own.

The decision table

What's true today	What you probably need	Why
Looks dated, works fine	Refresh	You're buying appearance, not engineering
Rebranding, structure is sound	Refresh	New skin over working bones
Converts poorly, but pages load fine	Refresh, focused on message and journey	This is a copy and layout problem
Slow on mobile despite optimisation attempts	Rebuild	Usually structural
Can't add pages without a developer	Rebuild	You'll pay this tax forever otherwise
Platform unsupported or insecure	Rebuild	Not really a choice
Only the enquiry journey is broken	Rebuild that section	Don't replace what works
Nobody knows how it was built	Rebuild	Investigation would cost more
You're not sure what's wrong, only that leads are down	Diagnose first — neither yet	See below

When the honest answer is "diagnose first"

Sometimes "the website looks old" really means "sales are down and the website is the thing I can point at".

Before spending on either option, it is worth knowing whether the website is actually the problem. Traffic may have fallen for reasons that have nothing to do with design. Or traffic may be fine and the site may be losing people at a specific, fixable point.

Our guide to traffic that doesn't become enquiries walks through that diagnosis, and the seven website problems worth fixing before more ad spend covers the usual suspects. If the answer turns out to be "the message is wrong", a rebuild will not fix it — you'd have rebuilt the same misunderstanding on better foundations.

The thing everyone forgets: protecting your search visibility

This is where rebuilds quietly go wrong, and it is worth being blunt about it.

If your site has been around for years, it has accumulated search visibility. Pages that rank. Links from other sites. URLs Google has indexed and trusts. A rebuild can destroy that in an afternoon if nobody is paying attention.

The usual damage: URLs change without redirects, so every ranking page becomes a 404. Content gets "tidied up" and the paragraphs that were actually ranking disappear. Page titles get rewritten by someone who has never seen a search console. The new site launches, everyone admires it, and organic traffic falls off a cliff six weeks later.

Non-negotiables for any rebuild:

• Map every existing URL to its new equivalent before launch, and set up 301 redirects.
• Keep the content that ranks. Find out which pages bring traffic first, then decide what to change.
• Preserve titles and descriptions that are working, or improve them deliberately rather than accidentally.
• Benchmark before you launch — traffic, rankings and indexed pages — so you can tell whether something broke.
• Check indexing after launch, not six months later.

A refresh carries far less of this risk, which is a genuine point in its favour and one reason not to rebuild casually.

Cost, time and disruption

Rough shape, not a quote:

• A refresh is faster, cheaper, lower-risk, and limited by the existing structure. If the foundation is the problem, you will be back within two years.
• A rebuild costs more, takes longer, needs more of your time for content and decisions, and carries launch risk — but removes the constraints permanently.
• A section rebuild sits between the two and is often the best value when only part of the site is holding you back.

The real question is not "which is cheaper today". It is "which one am I still happy with in three years".

How to decide this week

1. Open your site on your phone, on mobile data. Note everything that frustrates you.
2. Try to add a new page. Time how long it takes and how many people are needed.
3. Run one important page through PageSpeed Insights.
4. Ask whoever maintains it what the platform is and whether it is still supported.
5. Look at which pages currently bring you traffic and enquiries.

If steps 1–4 are fine and only the appearance bothers you: refresh. If two or more are painful: talk about foundations. And whatever you do, finish step 5 before anyone touches anything.

Most sites need less than people fear and more than people hope. The useful move is finding out which, before the invoice rather than after it.