When does a company website need rebuilding?

Websites don't usually get replaced because they break. They get replaced when nobody wants to show them any more - and by that point the site has been costing money for a while without anyone seeing an invoice.

Below are the signs that let you make the decision on facts rather than on feel.

Clear signs the site needs attention#

Changing content requires a developer#

This is the most expensive problem, because it isn't visible from outside. If adding a service or changing a price means emailing a developer, the site will inevitably fall behind. The content ages because updating it is a nuisance.

The site is slow for real users#

Open it on a phone, on mobile data, not on the office WiFi. If the first content appears after more than three seconds, you're losing visitors before they see anything. Check the result in Google Search Console's Core Web Vitals report - that shows real user data, not a lab measurement.

The mobile view "sort of works"#

Responsive doesn't just mean the page fits on the screen. If the buttons are too small, tables scroll off the edge, or the menu opens on the third tap, the mobile visitor simply leaves - and for most companies that's the majority of visitors.

The software hasn't been updated in years#

Every version skipped makes the next update riskier. If the WordPress core, the theme and the plugins have gone untouched for three years, the question is no longer whether something happens but when.

The site brings in no enquiries#

If there are visitors but no contacts, the problem usually isn't the design. It's the structure: the visitor can't tell what you do, who for, and what the next step is. A new colour palette doesn't fix that.

There's no analytics, or nobody looks at it#

If a form submission and a tap on the phone number aren't tracked as events, every decision that follows is guesswork. Before commissioning a new site, it's worth collecting at least two months of data about what people actually do on the current one.

Repair or rebuild?#

The answer depends on what's underneath.

Repairing is usually sensible when:

• the foundation is modern and the software is maintainable
• the problems are specific - speed, the mobile view, one broken form
• the structure and the messaging work, but the visual is tired
• content management is already in the client's hands

A new foundation is usually sensible when:

• the theme is a bought template that's been patched for years
• the site is held together by dozens of plugins, some no longer maintained
• every change breaks something else
• the structure itself is wrong and the content needs rethinking anyway

There's a middle option, and it's often the most sensible one: keep the content and the URLs, rebuild the foundation. That way you lose neither your search results nor your history.

What not to forget during a rebuild#

1. Map the old URLs. Every indexed address that changes needs a 301 redirect. This is the most common reason a new site ends up harder to find than the old one.
2. Measure beforehand. Record the current speed, traffic and conversions, so there's something to compare against afterwards.
3. Look at what's actually used. Analytics usually shows that half the pages get no visits. Those don't need migrating.
4. Agree who manages the content. If the answer is "the developer", the same problem returns in three years.

Where to start#

If you're not sure which way the decision falls, start with a technical review. We look at the current build, the hosting, the versions and the backups, and say honestly whether it makes more sense to develop what you have or build a new foundation. If patching the old one would cost more than replacing it, we say so.