Should I Fix My Website or Rebuild It? A Simple Decision Guide

You know your website is not working as well as it should. But what to do about it is unclear. Someone tells you it needs a complete rebuild. Someone else says a few tweaks will do. You worry about paying thousands you did not need to, or patching something that should have been replaced.

This guide gives you a way to decide yourself, and the questions to ask any developer so you get an honest answer.

The ten-question scorecard

Answer each question honestly with Yes or No. Count your Yes answers at the end.

1. Is the site hard or impossible to update yourself (or without calling a developer each time)?
2. Does it look or behave badly on a phone (tiny text, things off-screen, hard-to-tap buttons)?
3. Is it still slow after reasonable fixes, such as image compression and removing unused plugins?
4. Is it built on old or abandoned software (for example a theme or plugins that have not been updated for years, or a platform that is being shut down)?
5. Has it been hacked, or does it have repeated security warnings?
6. Has your business changed so that the site describes services, prices or customers you no longer have?
7. Do you break something every time you add a plugin or change a page?
8. Does it lack things you now need (online booking, payments, a customer area, integrations) that the platform cannot support?
9. Is the design so dated that it makes you hesitate to send customers to it?
10. Would it cost more each year to keep patching it than a new site would cost over a few years?

0 to 3 Yes: fix it. 4 to 6 Yes: consider a refresh (a new design on top of a clean rebuild of the front end, keeping your content, domain and structure). 7 or more: a rebuild is probably the cheaper long-term answer.

It is a guide, not a verdict. A single serious problem (for example, repeated hacks) can justify a rebuild on its own.

When fixing is the right call

Fix when the foundation is sound and the problems are specific. Typical examples:

• The site is slow because of oversized images, too many plugins or poor caching (see why your website may be slow).
• The contact form is broken, too long or does not send confirmations.
• Content is out of date, or pages are missing proof, calls to action or clear pricing.
• Mobile layout has a few specific faults.
• It has basic SEO gaps such as missing titles and descriptions.

Fixes cost much less than a rebuild, show results quickly and keep your existing search visibility. Ask for a written list of the problems and a fixed price for them.

When a refresh makes sense

A refresh keeps what works (your content, your address, your structure) and replaces what does not (the visual design and the code underneath). It suits a site that is structurally fine but visually tired or technically heavy. It is the middle path, and often the best value.

When a rebuild is justified

• The platform is end-of-life or cannot do what the business now needs.
• The site is built in a way that makes every change risky or expensive.
• Security problems keep returning.
• The business has changed so much that the site's structure no longer fits.
• You are paying more to keep it limping along than a new site would cost.

Be careful if someone insists you need a rebuild before they have actually looked at your site and your numbers. A good developer starts with an audit, not a quote.

If you rebuild: protect your Google rankings

This is where rebuilds most often go wrong. A new site can lose years of search visibility if it is launched carelessly. Before launch:

1. List every current page address that brings traffic or has links to it. Your analytics and Google Search Console will show you which.
2. Keep the addresses where you can. If an address must change, set up a permanent redirect (a 301) from the old one to the most relevant new page. Every one.
3. Keep the content that ranks. Rewrite it if it is weak, but do not delete pages that bring visitors without a plan.
4. Carry over titles, descriptions and headings, then improve them.
5. Check the new site is not blocked from search engines. Sites are sometimes left set to "do not index" after testing.
6. Submit the new sitemap and watch Search Console for errors for several weeks after launch.

Questions to ask any developer before you agree

• What exactly is wrong, and how do you know? (Ask for the evidence.)
• What would you fix first, and what difference would it make?
• Is the price fixed? What is included and what costs extra?
• Who owns the code, the design and the domain when you finish?
• How will you protect our current search rankings?
• What happens after launch: support, updates, backups?

Spend the money where it earns the most

Whatever you choose, tie it to a result. If the aim is more enquiries, start with the clarity of your message, your calls to action and your proof, covered in our guide to why visitors do not contact you. If you want a rough idea of what a better site could be worth for your own numbers, our homepage calculator lets you try it with only the figures you enter.