Signs your site genuinely needs a rebuild (and when it does not)

A lot of agencies lead with a rebuild. It is the most expensive thing they can sell you, and it is often the easiest answer for them to give. But most websites do not need a rebuild. They need to be handled properly.

When a rebuild is the right call

• The platform is end of life — the underlying tech is no longer supported or secure.
• The structure is fundamentally wrong — the information architecture cannot be fixed with tweaks.
• Performance is unfixable on the current stack, even after optimisation.
• You have outgrown it — the site cannot support what the business now needs.
• Maintenance has become a money pit — keeping it running costs more than starting fresh.

When it is not

• It just looks dated — a redesign handles that without a full rebuild.
• It is slow — that is a performance problem, not a platform problem.
• A few things are broken — those are fixes, not a rebuild.
• You were told it is "old technology" — age alone is not a reason.

The honest answer

Most of the time, the right move is to fix what is broken, improve what works, and maintain it properly. Rebuild when you genuinely need to, not because someone told you to.

The takeaway

A rebuild is a last resort, not a default. If you are being told you need one, get a second opinion on whether the problems are fixable first.