When should you redesign a website instead of rebuilding it?
Do not start with how old the website looks. Start with what is actually failing: the message, the journey, the technical foundation, the content model or all four.
A redesign is worth keeping when the foundations still work. A rebuild makes more sense when the structure, technology or editing model keeps getting in the way.
Separate the surface problem from the structural one
Some websites are fundamentally sound but no longer represent the business well. The navigation still makes sense, the CMS is usable and the technical setup is stable, but the visual direction, copy hierarchy or key pages need to catch up. That can be a redesign problem rather than a rebuild problem.
Other sites fight every useful change. The content model is brittle, important journeys are buried, integrations are patched together or mobile behavior is difficult to repair without touching everything else. In that situation, preserving the old foundation can create more work than replacing it deliberately.
Audit what still earns its place
A good rebuild does not mean throwing away everything. Keep the parts that are accurate, maintainable and useful. Replace the parts that limit the business or make the customer journey harder to understand.
- Keep content that is still accurate and genuinely helps customers decide.
- Keep integrations that are reliable and still fit the workflow.
- Rework navigation or page structure when the offer has changed materially.
- Replace the technical foundation when routine changes have become risky or unnecessarily expensive.
Choose for the next phase, not the last one
The useful question is not whether the current site can be made to look better. It is whether the improved version can support the way the business needs to communicate, publish, measure and convert over the next phase of growth.
That keeps the decision practical. Redesign when the foundation still helps. Rebuild when the foundation itself has become the constraint.