Should you repair or replace an old business website?

A website built ten years ago is not automatically useless. Some older sites have clear information, loyal search traffic, and a platform that can still be maintained. Others look acceptable on the surface while depending on unsupported software, lost credentials, broken forms, or a theme nobody can safely update.

Begin with condition, not appearance

Check who controls the domain, hosting, administrator accounts, backups, email delivery, analytics, and business listings. Then test the site on a phone, submit every important form, read the content as a new customer, and review the software and security history.

Repair when the foundation is still sound

Repair may be sensible when the platform is supported, access is under control, the content structure is usable, and improvements can be made without fighting fragile code. A focused repair can improve mobile behavior, calls to action, accessibility, speed, security, and local-search information.

Replace when every change increases risk

A rebuild is usually safer when the platform cannot be updated, important plugins are abandoned, the site has been repeatedly compromised, nobody owns the accounts, or the structure makes ordinary content changes expensive. Replacement is also reasonable when the business has changed so much that the old site tells the wrong story.

Ask for the reasons in writing

A responsible provider should explain what can remain, what must change, what the client will own, and what ongoing care will cost. “It looks old” is not a sufficient technical diagnosis.