Should you fix your website, or start over?

When your website has problems, the real question is whether to fix it or replace it — and the honest answer turns entirely on whether the problems are on the surface or in the foundation. Be a little wary of who you ask, because anyone who builds sites for a living — me included — has an incentive to say "rebuild." Which is exactly why the useful thing to know is when a patch is enough, so nobody sells you a new site you didn't need.

Most of what makes a site feel dated or underperform is surface-level, and surface problems patch cheaply. Outdated copy, missing pages, a stale Google listing, no WhatsApp button, wrong opening hours, a few broken links, no medical-aid information: every one of these is a fix on a sound structure, not a reason to start over. If the bones are fine and the site simply hasn't been kept up, patching is the right call — faster, cheaper, and enough.

A rebuild earns its place when the problem is in the foundation, where a patch can't reach. The clearest case is speed: if a site takes the better part of ten seconds to appear on a phone because of the platform it's built on, no amount of tidying the content fixes that — the foundation itself is the bottleneck. The same goes for a site that was never built for mobile, or whose underlying structure is broken in a way that makes every change a fight. When fixing it piecemeal would cost more than starting clean, the patch is the false economy.

So the test is simple, and you can apply it yourself:

Patch it when

• The problems are content and presentation — copy, photos, missing pages, a dated look that's really just old material.
• The ways in are missing, not broken — no WhatsApp, no booking, a non-tappable number. These are additions, not rebuilds.
• Your Google listing or details are wrong or neglected. That's free to fix and nothing to do with the site's structure.
• A few links or pages are broken. Cheap corrections on a sound site.

Rebuild when

• The site can't be made fast — the platform or foundation is why it's slow on a phone, and no tidying reaches it.
• It wasn't built for mobile — and most of your patients are on one.
• The structure itself is broken, so every change is disproportionately hard or expensive.
• Piecemeal fixes would cost more than starting clean. At that point the patch is throwing good money after bad.

The pattern I see in audits is that most findings are the patchable kind — copy, listing, contact methods, a handful of broken links — and a practice could go a long way with an afternoon of fixes and no rebuild at all. The exception is speed: when a site is slow because of the platform underneath it, that's the one a patch can't touch, and the honest recommendation flips to a fresh build. The deciding line is always the same — is the problem in the content, or in the foundation?

I'd rather tell you a patch is enough and keep your trust than sell you a rebuild you didn't need — and when a rebuild genuinely is the answer, you'll be able to see why for yourself, because it'll be the foundation, not the furniture.

— Paul