Can My Website Be Fixed, or Do I Need a New One?

You do not automatically need a new website because the current one looks dated. Equally, a cheaper repair is not good value if it leaves you paying to work around the same problem every month.

The useful distinction is between a website with a few weak parts and one whose foundations no longer support the business. Start with what customers cannot do, then assess whether the existing site can reasonably be made to do it.

Describe the problem before choosing the solution

A supplier can assess the options more usefully when you can describe what is going wrong. “It needs modernising” leaves both the work and the result open to interpretation. “The enquiry form fails on a phone” or “customers cannot find our second service” gives a supplier something concrete to investigate.

Separate the list into three groups: things that do not work, information that is wrong or missing, and appearance you would like to improve. This stops a visual refresh from taking priority over a broken customer journey.

Alongside the problems, it is worth noting the parts customers already use successfully. A useful gallery, familiar booking process or page that brings good enquiries may be worth keeping even if the surrounding design changes.

When a repair is a sensible choice

A repair is worth considering when you have access to the site, its underlying software can still be maintained and the changes are reasonably contained.

Typical examples include rewriting a confusing service page, improving navigation, fixing form delivery, replacing oversized images or making an existing layout behave properly on smaller screens. These are different jobs, but none automatically requires throwing everything away.

Ask for the proposed repair to be described in terms of its result. Instead of “mobile optimisation”, ask which pages and tasks will be checked, what will change and how you will confirm that it works. A small paid assessment can be useful where the supplier needs to inspect an unfamiliar system before giving an honest price.

When rebuilding becomes easier to justify

A rebuild may make sense if your business now needs something the existing platform cannot support sensibly, or if basic changes repeatedly break other parts of the site.

Other reasons include unsupported software with no realistic maintenance route, a structure that no longer reflects the business, or a site you cannot move or maintain under acceptable terms. Missing access needs investigating first; it does not always mean the website itself must be replaced.

Be cautious about a recommendation based only on which software the new supplier prefers. Ask what specifically prevents the old site from being improved and what a new build would solve. “We always use this platform” explains their process, not your business need.

Compare the full scope, not the two headline prices

Ask for a repair option and a rebuild option where both are genuinely practical. Compare what is included in each rather than assuming the more expensive option does more.

Use the UK small business website cost guide to compare the build price with ongoing costs. It includes first-year calculations rather than treating the launch invoice as the whole budget.

For a site handling bookings or orders, the handover plan can make a real difference to which option you choose. Each proposal should explain any likely disruption and how the supplier intends to keep it manageable.

Keep the useful parts of the old website

Before changing anything, make an inventory of current pages, forms, integrations and account access. Identify pages linked from adverts, emails, printed material or other websites.

A rebuilt page does not have to keep the same appearance, but visitors following an old link still need to reach the right information. Google's guidance on moving a site with URL changes explains why mapping old addresses to relevant new ones is part of a considered migration.

That does not guarantee that search performance will stay unchanged. Be wary of anyone promising a risk-free ranking improvement simply because the design is newer.

Keep a recoverable copy of the existing website and agree when the old hosting can be cancelled. Where email is bundled with hosting, check that separately before changing the subscription.

Ask what you will be able to manage afterwards

A new website should not leave you unable to make the same routine changes that were frustrating you before. Decide which tasks you want to do yourself and which you want someone else to handle.

Request a demonstration of a real task, such as changing opening hours or adding a work example. A dashboard containing many settings is not proof that those tasks are straightforward.

Whichever option you choose, written details of ownership, licences, administrator access and support will help you understand what you are taking on. A repair can change these arrangements too, particularly when a new supplier introduces paid software or takes over hosting.

Make the decision around the next few years

If the site needs a handful of improvements and otherwise fits the business, repair can buy useful time without unnecessary disruption. If each planned improvement depends on replacing another part, a rebuild may be the clearer investment.

The aim is not to preserve old code at any cost or chase a newer appearance. It is to get a maintainable website that supports the work you actually want. My business website service explains the sort of builds I handle; you can also send the current site and your list of problems for a starting assessment.