Websites

When to Rebuild Your Website (and When a Redesign Will Do)

By Tom Bore · 6 August 2026 · 5 min read

A redesign changes how your site looks. A rebuild changes what it's made of. Confuse the two and you either spend big money solving a problem new paint would have fixed, or you paint over foundations that are already failing.

A redesign reworks the surface: layout, branding, copy, the odd new page, on top of the site you already have. A rebuild replaces the foundations: the platform, the code, the content structure, the way the whole thing is put together. Start by working out which problem you have.

Signs you need a rebuild

New paint won't fix any of these. They live in the foundations:

  • Pages load slowly and no amount of image-squashing helps.
  • Adding a feature means a fight, or a quote that makes you wince.
  • It breaks on phones, and the fixes keep breaking something else.
  • The platform is unsupported or insecure, and updates are overdue.
  • Nobody on your team can edit content without a developer.
  • Search rankings and Core Web Vitals keep sliding whatever you try.

When a redesign is enough

If the site is quick, secure and editable, and it only looks dated or off-brand, you want a redesign. Refresh the look, sharpen the copy, fix the conversion points, and keep the working machine underneath. A rebuild here spends money to recreate what you already have.

The cost of getting it wrong either way

Redesign a broken foundation and the new look ships onto the same slow, fragile base, so you're back within a year. Rebuild a healthy site and you've paid to replace an engine that ran fine. The decision is worth more than the build.

How to decide

List what's wrong in plain terms, then sort each item into surface or foundation. Mostly surface points to a redesign. A cluster of foundation points, speed, security, an outdated platform, no way to add what's next, points to a rebuild. If a rebuild is the answer, treat the first version as an MVP: ship the core site fast, then grow it from real use rather than trying to relaunch everything at once. And before you commit to a platform, run the build vs buy question so you own the parts that matter and rent the rest.

In short

Redesign the surface, rebuild the foundations, and never pay for one when you needed the other. If you want a straight read on which yours needs, send us the URL and we'll tell you.