A website that's a few years old and starting to feel dated puts most business owners in front of the same decision. Start again from scratch, or update what's already there. Both are reasonable answers depending on the situation, and getting it wrong in either direction is expensive, either paying for a full rebuild you didn't need, or pouring time into refreshing a site whose underlying structure was never built to do what the business needs now. Working through these questions in order, rather than jumping straight to "how much would a new site cost", tends to give a much clearer answer.
1. What does the business need to do now that it couldn't when the site was built?
Everything else follows from this question, so it's worth answering properly before anything else. A site built five years ago for a business that only needed to explain what it does and take enquiries by phone is answering a completely different brief to one that now needs to take bookings online, manage a growing service list, or support a second location. If the answer is "nothing has really changed, it just looks old", that's a very different situation to "we need the site to do things it was never built to handle."
2. Can the existing structure support that without contortion?
Once you know what the site needs to do now, the next question is whether the current structure can actually stretch to cover it, or whether every new requirement is being forced in sideways. A booking system bolted onto a site that was never built with one in mind, a service area added as an afterthought because the original navigation didn't account for it, plugin after plugin stacked on top of each other to make the site do something it wasn't designed for. If updates keep feeling like contortion rather than addition, that's usually a sign the structure itself, not just the content sitting on top of it, has reached its limit.
3. Is there SEO equity worth preserving?
A site that ranks well for the searches that actually matter to the business is a real asset, and it's one that's easy to underestimate until it's gone. A rebuild, done carelessly, can genuinely damage that, and the risk has to be worth taking rather than assumed away. This doesn't rule out a rebuild if one's genuinely needed, but it does mean the migration itself, redirects, URL structure, preserving what's already working, needs to be treated as a real part of the project rather than an afterthought once the new site's already live.
4. Can the business maintain it day to day?
A site that nobody in the business can update without calling in help stops getting updated, and a site that stops getting updated starts to drift out of date quietly, service lists that don't reflect what's actually offered any more, old prices, outdated photography, closed opening hours still showing as current. If the honest answer is that updates have been avoided because they're too fiddly or require someone technical, that's a real factor, not a minor inconvenience, and it applies whether you're weighing up a refresh or a rebuild.
5. How much plugin and theme debt has built up underneath?
This is the one that's easiest to ignore because it's invisible from the front end. Years of plugins added for one-off needs, a theme that's been patched and customised well past what it was designed for, page builder shortcodes layered on top of each other, all of it adds weight, slows the site down, and makes every future change riskier and slower than it should be. A site can look fine on the surface and still be carrying a genuinely fragile structure underneath.
Why the order of these questions matters
It's tempting to start with the plugin and theme question, since it's often the most obviously broken thing when you go looking, but starting there tends to produce the wrong answer. A site that's genuinely showing its age technically can still be the right shell to build on, if what the business needs from it hasn't fundamentally changed, and a rebuild aimed purely at fixing technical debt often ends up rebuilding something that didn't need to grow into anything new. Answering the first question properly, what does the business actually need to do now, before getting into the state of the plugins underneath, keeps the decision anchored to the business rather than to whatever looks most broken on the surface.
Putting it together
A refresh is usually the right call when the structure holds up under all five of these questions and what's actually dated is the presentation and the content sitting on top of it, new photography, updated copy, a visual refresh that brings it in line with where the business is now. A rebuild is the right call when the answer to the first question needs structure the original build was never designed to support, and every attempt to force it in is making the site more fragile rather than better. If you're not sure which side of that line your own site sits on, that's a genuinely useful conversation to have before committing to either, and it's exactly where we'd start regardless of which direction it ends up going.
