Should you improve your website or rebuild it?

By Jeroen · Creative Technologist at Digital Powder

A website can look dated and still do its job. A newer one can look polished while making everyday changes unnecessarily difficult. Neither its age nor its appearance tells you, on its own, whether it needs rebuilding.

Before proposing a new website, we look at what is causing the difficulty. The answer might be a few changes to the content, a different design or a more substantial rebuild. Those are different projects, and it is worth knowing which one you are paying for.

Start with a problem you can describe

“We need a better website” is a starting point, but it does not give you much to work with.

Try describing what happens instead. Customers keep calling because they cannot find the opening hours. A service has changed, but its page still describes the old offer. Updating an event means copying a layout and hoping nothing breaks. Enquiries arrive without the information needed to respond.

Each problem suggests a different kind of work. Missing information may need a clearer place on the page. An awkward editing process may need a better way to manage that content. Neither automatically calls for replacing the entire website.

Choose the problems that matter most and agree what an improvement would look like. That gives you something more useful to assess than whether the new version feels newer.

Separate the design from the technical setup

Keeping the same platform does not mean keeping the same website design. Equally, changing the design does not always require moving to a different platform.

A WordPress website, for example, can be rebuilt without retaining its existing theme or page builder. Its content management system may still be useful even when the way pages are assembled needs to change.

The same distinction applies to the visual identity. A business may still be happy with its logo, colours and photography. The work might be to use those elements more effectively, rather than commission a new identity alongside the website.

Keeping these decisions separate makes the scope easier to understand. It also makes it easier to explain why a particular part needs replacing.

Decide what is worth keeping

Before taking anything apart, make an inventory of what the website contains and what people use.

That includes the obvious material—pages, images and documents—but also forms, booking links, orders, account records and connections to other services. Some of those may matter much more to the business than the homepage layout.

For each part, decide whether to keep it, improve it or retire it. Record the existing page addresses too. When an address needs to change, the route from the old page to the new one belongs in the project, rather than becoming a problem to discover after launch.

This is also a useful moment to remove information that no longer applies. Preserving useful content is not the same as carrying every old page into the new site.

What a rebuild can retain

We have worked with Corkage Bath since 2019. In 2026, we rebuilt the restaurant website, replacing its general-purpose theme setup with a custom WordPress build.

The restaurant did not need to become a different brand. The website needed to present its food, wine and events clearly, while giving the team a more practical way to maintain that information. Custom menu and event tools separate those updates from the page layout: changing the content does not require redesigning the page around it.

The HNHCP / Hemcare project involved a different kind of website. We replaced its theme-builder setup with a custom build while retaining WooCommerce as the basis for registration. The wider platform connects registration with delegate management, QR tickets and educational materials.

In both cases, a rebuild meant deciding which parts to replace and which still had a useful role. It did not mean abandoning WordPress, or treating every existing component as a problem.

Include the changeover in the scope

A finished design is not the whole delivery.

The new website needs to carry out the tasks the business relies on. Test where forms arrive, whether booking links lead to the right place, whether important documents remain accessible and whether someone can make an ordinary content update without help.

For a site that takes orders or registrations, also decide what happens to records created while the replacement is being prepared. A copy taken at the start of development may no longer represent the live business when it is time to switch.

Agree how the switch will happen, what will be checked afterwards and how the previous version can be restored if necessary. These are practical parts of the rebuild, not optional finishing touches.

Choose the scope that solves the problem

A focused improvement is a sensible choice when the underlying setup works and the problems are limited. A stronger case for rebuilding emerges when even ordinary changes repeatedly need workarounds: edits across several templates, duplicated content or another fix to compensate for an earlier one.

At that point, compare the work involved in continuing to patch the site with the work involved in replacing the troublesome parts. Neither option is automatically cheaper or more suitable. The recommendation needs to explain what would actually change.

Ask for the reasoning behind the recommendation. What will become easier? What stays? What changes? What work is involved in moving from one version to the other?

Those answers should make the proposal understandable before any new design is presented.