Does your website need a rebuild, or just a few fixes?

Your website isn't brilliant. You know it. Maybe it looks dated, or it's fiddly to update, or the phone hasn't rung from it in months.

The question is whether you need a whole new website, or whether a few changes would do the job.

That's a fair question, and it deserves an honest answer. I rebuild websites for a living, but plenty of sites I look at don't need rebuilding. They need three or four specific fixes. Spending money on a rebuild you don't need is just as bad as patching a site that's beyond saving.

Here's how to tell the difference.

Quick answer: Fix it if the problems are specific and the site is easy to change: an unclear headline, a hidden phone number, a broken form, a few outdated pages. Rebuild it if several problems stack up and the site makes them hard to fix: it's awkward on phones, painfully slow, you can't edit it, nobody has the logins, or it describes a business you no longer are.

Three questions we'll answer:

• What are the signs that fixing is enough?
• When does fixing become more expensive than starting again?
• How do you rebuild without losing what's working?

Start by finding out what's actually wrong

Before deciding anything, write down the actual problems. "It looks old" isn't a problem by itself. Plenty of plain, older-looking websites bring in steady work.

Better questions:

• Do people find it? (Check Google Search Console.)
• When they arrive, do they get in touch? (Check enquiries, calls and form submissions.)
• Can you update it when you need to?
• Does it work properly on a phone?
• Is it accurate about what you do now?

If you're not sure where people drop off, my guide to websites that get visitors but no enquiries walks through how to check, step by step.

Signs a few fixes will do

Here's the first question. You probably don't need a rebuild if:

• The problems are specific. You can point to them: "the headline's vague", "the phone number's hidden", "the form doesn't send".
• The site works on mobile. Text is readable, buttons are tappable, nothing's falling off the screen.
• You can edit it, or someone can, without breaking it.
• It's reasonably quick. It loads in a sensible time on a phone signal.
• It's mostly accurate. A few pages need updating, but the business it describes is still yours.

In that case, a list of targeted improvements is usually the cheapest and quickest route. Clearer headline, tappable phone number, better photos, shorter form, a couple of new service pages. That can transform how a site performs without starting from scratch.

Signs it's time to rebuild

Now the other side. A rebuild starts to make sense when several of these are true at once:

• It's hard to use on a phone. Tiny text, pinching to zoom, menus that don't work. If a big share of visitors are on mobile, this alone can be decisive.
• It's very slow. Google's free PageSpeed Insights gives you a mobile score and lists the main problems. A site weighed down by an old theme and lots of plugins can be hard to speed up without rebuilding.
• You can't change it. Nobody has the login, the builder or plugin it relied on is gone, or every small change costs a call-out fee and a fortnight's wait.
• It's built on something you can't move or don't own. My guide on who owns your website explains why this matters.
• It describes a different business. You've added services, dropped others, moved area or changed your name, and the site no longer fits.
• Security warnings. Browsers flag it as "Not secure", or it runs old software that hasn't been updated in years.
• It's embarrassing. If you avoid giving people the address, it's costing you work.

One of these on its own can usually be fixed. Three or four together usually means patching will cost more, over time, than starting fresh.

When fixing becomes more expensive

Here's the second question. Fixing is cheaper per job. Rebuilding is cheaper when the jobs keep coming.

A simple way to think about it:

1. List every change you'd need to make the site work well.
2. Ask a designer to estimate the cost of making those changes to the current site.
3. Ask for a quote for a rebuild that includes all of them.
4. Add the yearly running costs of each option.

If the fixes cost most of what a rebuild would, and the old site will still be slow, hard to edit or hard to move afterwards, the rebuild is often the better deal. My guide to what a small business website costs explains how to compare quotes over three years, which makes this decision much clearer.

How to rebuild without losing what's working

Here's the third question. A rebuild should be an upgrade, not a reset. Before anything changes:

Keep a record of the current site

• List every page and its web address.
• Save a copy of the text and images.
• Note which pages bring in the most visitors, from Search Console or your analytics.

Keep or redirect important addresses

If a page called /boiler-servicing is bringing in visitors from Google, the new site should either keep that address or send visitors to the new equivalent with a permanent redirect. Pages that simply vanish lose whatever position they'd earned.

Keep the content that's working

Improve it, by all means. But if a page is doing well, don't throw away what makes it useful.

Check after launch

Watch Google Search Console for a few weeks after the new site goes live. Look for pages Google can't find and fix them quickly.

A careful rebuild can improve your visibility. A careless one can set it back for months. The difference is mostly planning.

A quick self-check

Score your site. Give it a point for each of these that's true:

1. It's awkward to use on a phone.
2. It's noticeably slow on mobile.
3. You can't update it yourself or easily get it updated.
4. You don't have the logins, or aren't sure who owns it.
5. It no longer describes what you do.
6. It shows security warnings or runs very old software.
7. You avoid telling people the address.

0 to 2 points: targeted fixes are probably enough.

3 or more: it's worth getting a rebuild quote alongside a quote for fixes, and comparing them properly.

Either way, a second opinion helps. Sometimes the problem you've been worrying about is the least important one, and the real fix is something you hadn't noticed.