How to know when your website needs a rebuild versus a repair

This is one of the most common questions I get, and the answer isn't always obvious from the outside.

A repair makes sense when the foundation is solid but specific things are broken or outdated. A page that loads slowly, a contact form that stopped working, content that no longer reflects your services, a design that needs refreshing. These are surface problems. Fixing them doesn't require starting over.

A rebuild makes sense when the structure itself is working against you. If visitors can't find what they need, if the site was built on a platform that limits what you can do, if your business has changed significantly since the site was built, or if the site was assembled from a template that was never really yours to begin with, those are structural problems. Patching them costs more over time than rebuilding correctly once.

The question worth asking is whether the problems you're experiencing are symptoms or the actual cause.

A slow site might need a performance pass. It might also be running on outdated hosting with a plugin stack that was never optimized, in which case the repair addresses the symptom and the problem remains.

A good web consultant should be able to tell you which situation you're in before recommending anything. If the answer is always a full rebuild, that's worth questioning.