Rebuild or repair: an honest test for an ageing website
A rebuild is sometimes necessary and often sold unnecessarily. The useful question is not how old the site looks, but which of its parts are structural and which are cosmetic.
Five checks before you commit
Load time on a mid-range phone. Percentage of traffic on mobile versus desktop conversions. How long a content change takes. Whether the tracking matches your actual sales process. How many plugins or dependencies are past end of life.
If mobile speed and the content workflow are both acceptable, a new visual layer and a handful of fixes will usually outperform a full migration for a fraction of the cost.
When the foundation genuinely has to go
Rebuild when the platform cannot render a modern page quickly, when the content model actively prevents the pages you need, or when the codebase cannot be updated safely. These are structural problems that a redesign will not solve.
Rebuild also when the site is a product surface rather than a brochure: booking flows, account areas and pricing configurators are expensive to bolt onto a site that was never designed for them.
Protecting search traffic during a migration
Map every existing URL to its new destination before launch, keep the high-performing pages on the same slugs where possible, and monitor indexing daily for the first two weeks. A migration without a redirect map is a self-inflicted traffic loss.
Common questions
- How often should a business website be rebuilt?
- There is no fixed interval. Most sites need a visual refresh every three to five years and a platform change less often, when the technology or the content model genuinely stops serving the business.
- Can we keep our existing URLs after a rebuild?
- Usually yes, and you should where the pages still exist. Where structure changes, a one-to-one redirect map preserves both rankings and inbound links.
Next step
If this question is live in your business right now, describe the situation and you will get a written view on the options, including whether you should build at all.
Discuss your projectRelated notes
All insightsCustom software or off-the-shelf: how to decide
A practical framework for choosing between configuring an existing product and commissioning custom software, based on where your process actually differs.
ReadStrategyHow to write a technical brief that gets accurate quotes
The brief structure that separates a project that can be estimated from one that cannot, with the eight sections worth writing before you talk to any developer.
ReadStrategyPlanning a technology budget that survives the year
How to split spend between build, maintenance and improvement so that the second year of a platform is funded before it starts.
Read