Fix or rebuild? How to tell when your website is beyond saving

Your website is slow, or it looks wrong on a phone, or something broke after an update and nobody can quite say why. So you ask around, and the answer comes back fast: you need a rebuild. New site, clean slate, few thousand pounds, sorted.

Maybe. But here is the thing I want you to know before you spend a penny: most websites are far more fixable than their owners fear. A site that feels like a lost cause is often one clear fault away from working properly. And anyone who says “rebuild” before they have actually looked under the bonnet isn’t advising you — they’re selling you the thing they most enjoy building.

So let me give you what I’d want if it were my money on the line: how to tell the difference, a set of questions you can work through yourself, and how to judge any quote you’re handed — including one from me.

The honest default: assume it’s fixable

I start almost every job assuming the site can be repaired. Not because I’m soft, but because it’s usually true.

Think of it like a house. A cracked tile, a dripping tap, a door that won’t close — these are annoying, sometimes urgent, but they don’t mean you knock the house down. You only rebuild when the foundations have gone, or when so many bad extensions have been bolted on over the years that fixing one thing breaks another.

Websites are the same. A broken contact form, a slow-loading homepage, an out-of-date plugin, a colour that looks wrong — these are repairs. They can look alarming from the outside, especially when the site is your shopfront and it’s misbehaving in front of customers. But alarming is not the same as terminal.

The reason this matters: a rebuild is the most expensive answer to almost any website problem. If a repair would do, and someone talks you into a rebuild anyway, you’ve paid many times over for a result you could have had for a fraction of the cost.

The genuine reasons to rebuild

That said, rebuilds are sometimes the right call — and when they are, trying to patch the thing is throwing good money after bad. Here are the signals that actually point to a rebuild, as opposed to the ones that just sound scary.

The foundation is abandoned or unsupported. Most small-business sites are built on a platform (like WordPress) plus a theme and often a page-builder — the tools that control how the site looks and behaves. If the theme or builder your site depends on has been abandoned by whoever made it — no updates, no security fixes, company gone — then you’re building on sand. It will keep breaking, and each fix gets harder. This is a foundation problem, not a repair.

It’s patches stacked on patches. Some sites have been worked on by four or five different developers over a decade, each adding a workaround on top of the last person’s workaround. Open it up and nothing is where you’d expect; a small change in one place breaks something unrelated three pages away. At some point, untangling the mess costs more than starting clean. Not because any single thing is broken, but because the whole thing has become a knot.

The platform is so old that updating it safely is impossible. Software needs updating to stay secure, the same way a car needs servicing. If a site has been left on a version so old that the safe update path no longer exists — you can’t get from where it is to where it needs to be without everything falling over — then a rebuild on current foundations is often the only responsible route.

It’s fundamentally broken on mobile. Most people will visit your site on a phone. If your site was built before that was true and never properly adapted, “make it work on mobile” can be a genuine foundation job rather than a tweak — the layout has to be reconceived, not adjusted. There’s a real difference between a button that’s slightly too small (a fix) and a site that simply wasn’t designed for the screen most people use (often a rebuild).

It would honestly be faster to rebuild than to untangle. This is the one that ties the others together. When a competent person opens the site and can see that starting fresh would take less time — and cost you less — than unpicking what’s there, that’s a rebuild. The test is time and cost, not taste.

The reasons to fix

The flip side. These are the signs your site is worth saving:

• There’s one specific, identifiable fault. The form doesn’t send. One page is slow. An update broke a layout. A named, findable problem is a repair, almost always.
• The foundations are reasonably modern and sound. Built in the last few years, on a supported platform and theme, kept roughly up to date. The bones are fine.
• It works on mobile. Not perfectly, maybe, but it adapts to a phone screen and is usable. That tells you it was built with the right assumptions.
• A competent person can look at it and tell you what’s wrong. If someone can open it up and explain the problem in plain terms — “your contact plugin is out of date, that’s the whole issue” — you don’t need a rebuild. You need that thing fixed.

A decision framework you can use yourself

You don’t need me to run through this. Work through these questions honestly:

1. Can you (or anyone) name the actual problem? If it’s “the booking form stopped working,” that’s specific — lean fix. If it’s a vague “it just feels broken and old and everything’s a struggle,” dig further.
2. How old is it, roughly, and is it kept updated? Built in the last three or four years and maintained — lean fix. Nobody’s touched it in five-plus years and no one knows what it’s running on — lean rebuild.
3. Does it work on a phone? Pull it up on your own mobile. Usable, adapts to the screen — fix. A shrunk-down desktop site you have to pinch and zoom — likely rebuild.
4. How many different hands have been in it? One builder, coherent — fix. A chain of developers each patching the last — lean rebuild.
5. When someone competent looked, could they see what was wrong? Yes, clearly — fix. “It’s a mess in here, honestly it’d be quicker to start again” — that’s an informed rebuild, which is the only kind worth paying for.

If most of your answers point to fix, be sceptical of anyone insisting on a rebuild. If most point to rebuild, patching will only postpone the bill.

What a properly done rebuild actually includes

If you do land on a rebuild, this is the part that protects you — and it lets you judge any quote, mine included. A rebuild done properly has all of these:

• Work happens on a staging copy. The new site is built on a private copy, not on your live site. Nobody experiments on the shopfront while customers are watching.
• Your current site stays live until the new one is finished, tested, and you’ve approved it. You should never be dark. The switch happens once, at the end, when the new site genuinely works. (Doing that switch cleanly is its own skill — I’ve written separately on how to move a website without it going down.)
• There’s a written scope. In plain English: which pages, which features, how many rounds of revisions. So “finished” means the same thing to both of you.
• The price is fixed and agreed up front. You know the number before work starts. Not “we’ll see how it goes.”
• There’s a plan to keep it maintained afterwards. A site is a living thing; it needs the odd update. A rebuild that ends the day it launches is a rebuild that starts rotting the day after.

If a quote is missing several of these — no staging, no written scope, a fuzzy price, no aftercare — that’s worth questioning, whoever it comes from. A proper rebuild is what I do under Rebuilds, done right, and the checklist above is exactly how I’d want you to hold me to it.

The cost trap worth naming

The most expensive rebuild is the cheap one that repeats the old mistakes.

If you rebuild on the same shaky foundations, skip the aftercare, and take the lowest number in the room, you’re not saving money — you’re renting a problem. In a year or two you’ll be exactly where you are now, paying again, having thrown away the first spend entirely. I’ve written more on this in the real cost of a cheap website, because it’s the mistake I see cost owners the most over time. A rebuild is worth doing once, properly, or not at all.

When to get help

Get a second opinion when: you’re being told to rebuild but nobody has explained, in plain terms, what’s actually wrong; your answers to the framework above are genuinely mixed; or the problem keeps coming back no matter who fixes it — that pattern itself is information.

What you want is someone who’ll look first and tell you honestly which side of the line you’re on, even when the honest answer is the less profitable one for them. That’s the whole point of my Free Site Check: I look, and I tell you whether it’s a fix or a rebuild — including when the answer is “leave it alone, it’s fine.” Because the goal isn’t to sell you the biggest job. It’s to make sure the money you spend is the last money you have to spend on this for a good while.