Fix or rebuild? How to decide what your website actually needs

Fix your website if the platform is still supported, the structure still fits how your business works, and the problems are a defined list of bugs, slow pages or dated sections. Rebuild if the platform is end-of-life or unmaintainable, if every small change breaks something else, or if the business has changed so much that the site’s structure no longer makes sense. Most sites sit closer to the fix end than their owners expect.

The trouble is that “it feels old” is not a diagnosis. Before you decide, it helps to separate what is broken from what is merely unfashionable, and what is the site’s fault from what is the content’s.

Start by listing what is actually wrong

Write down every problem you have with the site, one per line. Be specific: “the contact form sometimes does not arrive”, “the mobile menu covers the phone number”, “we cannot edit the homepage without calling someone”. Then sort each line into one of four groups:

• Bugs. Something is broken and should work. These are almost always fixable on the current site.
• Performance. Pages are slow, especially on phones. Usually fixable, often by dealing with images, scripts and hosting.
• Content and design. Copy is out of date, photos are poor, a section looks dated. Often fixable section by section.
• Structural. The platform cannot do what you need, the site is hard to edit, or the information architecture no longer fits the business. This is where rebuilds are justified.

If most of your list is in the first three groups, you probably need fixes, not a new site. If the structural group is long, keep reading.

Signs a fix is the right call

• The site runs on a platform that is still maintained, such as current WordPress, Shopify or Webflow.
• You can still log in and edit most content yourself.
• The pages and navigation still match what you sell and how customers buy.
• The problems are a list you could write on one page.
• The site brings in enquiries or sales, and you do not want to risk disrupting that.

That last point matters more than people expect. A working site has history: pages Google has indexed, links from other sites, and URLs customers have bookmarked. A rebuild can protect all of that, but only with care. We explain how in moving to a new website without losing your Google traffic.

Signs a rebuild is worth considering

• The platform or a core component is no longer supported, or depends on software versions that cannot be updated safely.
• Small changes regularly break unrelated parts of the site.
• No developer can work on it efficiently because the code is undocumented or highly unusual.
• You need features the platform cannot reasonably support, such as proper online booking or a store.
• You have changed what the business does, and the site structure no longer makes sense.
• You cannot get control of the hosting or code. See who owns your website before assuming this is permanent.

What about WordPress sites that keep breaking?

WordPress gets blamed for a lot that is really about how a site was put together. A site with dozens of plugins, an abandoned theme and years of skipped updates can feel hopeless, yet often it can be stabilised by removing what is not needed, replacing what is abandoned and updating carefully. Our guide to updating WordPress without breaking it covers the process. If, after that, the theme itself is the problem, a rebuild on a cleaner theme can be a middle path rather than a new platform.

The middle options people forget

Fix and rebuild are not the only choices. Some of the most cost-effective work sits in between:

• Rebuild one section. Replace the homepage or a key landing page, and leave the rest alone.
• New template, same content. Keep the platform and content, and replace the theme or design.
• Separate the hard part. Move bookings, a quote tool (common for trades businesses) or a store to a dedicated service or a small app, and link to it from the existing site.
• Fix now, rebuild later. Stabilise the site so it is safe and working, then plan a rebuild on your own timeline instead of in a panic.

Questions to ask before you spend

1. What specific problems will this solve, and how will we know they are solved?
2. What does the site do for the business today, and what would we lose if it went offline for a week?
3. Which URLs, forms and integrations must keep working after any change?
4. Who will maintain the site afterwards, and can they actually work on what is being proposed?
5. If we fix rather than rebuild, how long would the fixed site realistically last?

Be cautious of anyone who recommends a rebuild before looking at the site, or who cannot explain the reasons in plain language. A rebuild is a bigger, longer job, and the person proposing it often benefits most. The same applies in reverse: a developer who patches indefinitely without saying the platform is past its use-by date is not doing you favours either.

If your site was built with an AI app builder, the decision has some extra angles. Your vibe-coded MVP works. Should you fix it or rebuild it? covers those.

If you only do three things

Write down what is actually wrong and sort it into bugs, performance, content and structure. Check the platform is still supported. Get one honest, written opinion that explains its reasoning before committing to either path.

If your list turns out to be mostly bugs, our bug fixes are priced per defined fix, and we will tell you plainly if a fix is not worth doing. From $250 for a defined fix. Most bug jobs land between $250 and $1,200.