Your website looks tired, the phone number is wrong and you are not sure whether the contact form works. Should you pay someone to repair it, or start again?
There is no sensible answer based on appearance alone. An older site with sound foundations might only need clearer words, fresh photos and a few repairs. A newer-looking site can still be difficult to maintain or fail when customers try to use it. Work through the problem before deciding what to buy.
Start by testing the customer journey
Pick up your phone and pretend you are a new customer. Search for your business, open the site and try to find the answer to these questions: What jobs do you do? Do you cover my area? Can I see work like mine? How do I get a quote?
Then call the number from the website and submit a test enquiry through the form. Check that the message reaches the right inbox and that any confirmation makes sense. If you cannot complete those tasks easily, you have a concrete list of issues to fix. Our trade website mistakes guide covers other common points of friction.
Problems that often justify a repair
If you are happy with the basic structure and can still access the website, targeted changes may be enough. Examples include:
- Updating the phone number, opening hours or areas covered.
- Rewriting vague headings so customers immediately recognise the service.
- Replacing stock images with recent, permission-cleared job photos.
- Fixing a form, a broken link or a button that does not work on mobile.
- Adding a missing service, testimonial or recent work example.
- Improving a slow page by addressing the actual cause rather than guessing.
Ask for an itemised estimate. A small list of well-defined improvements is easier to price and review than a request to “make the website better”. Websites for Trades currently lists updates and optimisation at £30 per hour; the time needed depends on the site and the issue.
Signs that a rebuild may make more sense
A rebuild is worth considering when you cannot safely or economically make the necessary changes. Perhaps nobody has the logins, the previous supplier has disappeared, the layout breaks across many phones, or every small update takes hours because the underlying site is difficult to work with.
It may also be time to rethink the structure if the business has changed substantially. A site built for occasional handyman jobs may be the wrong starting point for a team now specialising in full bathroom installations. Replacing a few words will not necessarily give those services the space and proof they need.
Before agreeing to rebuild, ask the supplier to explain which problems cannot be repaired, which existing text and photos can be reused, and what will happen to the current website addresses. If an old page has useful links or visitors, the new site should have a sensible destination for them. Confirm that your domain and business email will keep working during the change.
Compare the whole cost of each option
A repair quote should say what will be fixed, how it will be tested and whether further issues might be found. A rebuild quote should say what pages, copy, hosting and launch support are included. In both cases, ask about the ongoing monthly charge and future edits.
Do not compare a repair bill with only the headline price of a new website. Compare what you will have after the work, what it will cost over the next year, and who will help if something breaks. A rebuild can be good value when it solves several persistent problems together; a repair can be good value when the structure is already doing its job.
A quick decision rule
If the site is accessible, its layout works and the problems are a short, specific list, get a repair estimate first. If the structure no longer fits the business or the technical problems are widespread, ask for a rebuild proposal as well. You can then compare real scopes rather than making the decision from a screenshot.
If you would like a second opinion, send us your website and the problems you have noticed. We can discuss whether targeted changes or a fresh three-page site would be the more sensible route.
