When You're Live · 30 September 2026 · 2 min read
Fix, Improve or Rebuild? What Your Existing Website Actually Needs
When a website starts to feel like a problem, the instinctive answer is often to rebuild it. Sometimes that's right. Often it isn't, and it's the most expensive way to solve a problem that a few targeted fixes would have handled.
Three different answers to three different problems
Fix is for specific faults: pages that load slowly, forms that fail, plugins that are months out of date, something that broke after an update. The foundations are sound; something particular is wrong. That's website maintenance: diagnosing the cause, fixing it, and keeping the site healthy so it doesn't recur.
Improve covers sites that work but underperform. Performance tuning, cleaner structure and metadata so search engines understand your pages, better mobile usability, or a missing capability such as bookings or payments. This is usually the best value per dollar because you keep everything that's working. New capabilities are feature implementation; speed work is website performance.
Rebuild is for fundamentally outdated systems: an unsupported platform, a theme or page builder that fights every change, security issues you can't reasonably patch, or a structure that can't support where the business is going. That's website redevelopment, and it's the right answer less often than agencies selling rebuilds would suggest.
Fix, improve or rebuild?
Tick what's true of your site. The tool shows which direction the evidence leans. It's a thinking aid; the real answer comes from looking at your actual site.
What are you seeing?
Fix
For small technical problems.
When: Broken forms, slow pages, out-of-date plugins, an error after an update. The foundations are sound; something specific is wrong.
Trade-off: Lowest cost and fastest, but it doesn't change what the site can do, and repeated fixes on a rotten base are a warning sign.
Improve
For working sites that need better performance, UX or functionality.
When: The site functions but underperforms: slow on mobile, weak conversion, missing a booking or payment feature, or poorly structured for search.
Trade-off: Usually the best value per dollar because you keep what works. The limit is the platform: some things can't be improved past what it allows.
Rebuild
For fundamentally outdated systems.
When: Unsupported platform, unpatchable security issues, a structure that blocks the business, or costs of change that exceed the cost of starting over.
Trade-off: Highest cost and risk (rankings, tracking, content migration) but the only honest answer when foundations fail. Needs careful migration planning.
Tick one or more items to see the direction.
Questions worth asking before you decide
- Is the problem specific (something is broken) or general (everything is hard)? Specific problems usually point to fix or improve.
- Can the platform still be updated and supported? If it can't, every fix is temporary.
- What would a rebuild change that an improvement couldn't? If the answer is 'the look', consider a redesign on the existing foundation.
- What would a rebuild put at risk? Rankings, tracking, forms and content can all be lost in a careless migration.
- Who will maintain it afterwards? A site nobody can safely edit will be back in the same position in three years.
If you'd like a second opinion, the website health check gives you a structured self-assessment, and our process explains what a proper diagnosis involves.
Tell us what's not working.
You don't have to know what you need. Describe the problem and we'll help figure out what comes next.
Tell us what's not working