Rebuilding a website is a significant decision, and it should be made with evidence rather than frustration. Submit your site and we will review its condition — technical debt, platform health, speed, mobile experience, search footprint and usability — then frame the repair-versus-rebuild question honestly.
Sometimes the right answer is two specific fixes. Sometimes it is a rebuild. Often it is neither.
Most owners arrive at this decision after a run of frustrations: a change that cost more than expected, a plugin update that broke a page, a developer who says the theme cannot be updated, or a site that simply feels tired next to competitors.
None of those on its own answers the question. The useful framing is whether continued spending on the existing website buys you progress or just keeps it standing. Patching is sensible while the underlying structure is sound. It stops being sensible when each fix is fragile, expensive and blocked by something older underneath it.
This review is diagnostic. It is designed to give you enough evidence to make the decision deliberately, including the possibility that the honest answer is to leave the site alone and spend the money on something else entirely.
Whether the problem is appearance and arrangement, or the way the site is built underneath it.
Layers of theme, builder and override code that make every future change slower and riskier than it should be.
Public clues about whether the components your site depends on still appear to be maintained.
Whether slowness comes from hosting, page weight or the build itself — which changes the answer considerably.
Whether mobile problems are limited to a few templates or systemic across the site.
Which pages appear to be doing real work, so a rebuild does not quietly discard them.
Whether your team can realistically maintain the site, since a site nobody can edit tends to go stale regardless of its condition.
Recurring breakages and visible risk factors that make ongoing patching a poor investment.
Tell us what is making you consider the decision. If you have been quoted for a rebuild, or know roughly what the site has cost to maintain, mention it — it helps frame the answer.
Neither column is a verdict on its own. The pattern across them is what tends to make the decision obvious.
There is also a legitimate third answer: keep the site as it is, fix two specific things, and spend the rest of the budget on visibility or content instead.
We will not quote industry averages at you, because they would be invented. The pattern worth watching is your own spending over the past two years.
If most of that money produced improvements — better pages, faster loading, new functionality — the platform is serving you. If most of it went on keeping things working, restoring what broke, or working around something that cannot be changed, that is maintenance spending on a structure that is no longer earning it.
The same logic applies forwards. If the next twelve months of planned work would each be complicated by the same underlying constraint, replacing the constraint may cost less than repeatedly working around it.
Most visibility lost in a website migration is lost to avoidable mistakes rather than to the rebuild itself.
Changing addresses for the sake of a tidier structure is one of the most common self-inflicted wounds in a rebuild. Every URL that changes needs a redirect, and every redirect is a small loss of clarity.
Where a change is genuinely warranted, map each old address to its closest new equivalent rather than sending everything to the home page.
Pages that were already attracting visitors have earned their position. Rewriting them from scratch in a new tone can undo that quietly.
Improve them by all means, but start from what exists rather than from a blank page.
Titles, descriptions and accurate schema are easy to lose in a platform change, and they are what search results and AI-assisted summaries actually read.
Record them before the migration so that anything missing afterwards is obvious.
A staging copy lets you check important pages, forms and enquiry routes before anyone else sees them. It also prevents an unfinished site being indexed while it is still being assembled.
Check that forms actually deliver email after launch. It is the single most commonly missed item.
Carry over analytics and Search Console so you can compare like with like, and watch for crawl errors, missing pages and dropped queries for a few weeks after launch.
Problems caught in the first month are usually trivial to correct. Problems noticed six months later are not.
You tell us the website address and what is making you consider fixing or rebuilding.
We review the site's condition, technical debt clues, performance, mobile behaviour and search footprint.
You receive a plain-English assessment framed as repair, targeted improvement or rebuild, with the reasoning.
If a replacement does turn out to be sensible, we can talk about options — including managed approaches — but the review itself is diagnostic and carries no obligation.
Separating a dated appearance from genuine technical age.
WordPress Website AuditThe technical health picture behind the decision.
Website Speed TestWhether slowness is the build, the hosting or the content.
Free SEO AuditWhat search visibility you would need to protect in a rebuild.
Not sure which one fits? Browse all website checks.
Submit your website and get a clear, diagnostic read on whether it is worth repairing, improving in specific places, or replacing.