Separate the interface from the foundation
A visual redesign changes how the website presents information. A rebuild changes the system that stores, generates and delivers it. Many projects need elements of both, but the distinction matters because it changes migration risk, cost and long-term flexibility.
If the content model is sound, editing is reliable and technical performance is acceptable, replacing the platform may add risk without enough value. If the structure blocks every meaningful improvement, a surface redesign will only disguise the problem.
A redesign may be enough when
Improve the existing system when its fundamentals are dependable and the main problem is communication or interface quality.
- Editors can create and maintain the required content reliably
- Templates can support the new information architecture
- The platform is secure, supported and performant
- Metadata, structured data and redirects can be controlled
- Accessibility issues can be fixed without fighting the framework
A rebuild is more likely when
Rebuilding becomes rational when the current foundation creates persistent cost, risk or strategic constraint.
- Core content is trapped in inflexible or duplicated templates
- The platform is unsupported, insecure or difficult to update
- Performance problems come from architecture rather than content alone
- Multilingual or structured content cannot be modelled correctly
- Critical integrations and measurement cannot be implemented safely
- Maintaining the existing system costs more than replacing it responsibly
Protect what already has value
A rebuild does not mean starting from zero. Existing search equity, useful content, media, data, integrations and familiar editorial workflows should be inventoried before anything is removed.
Every existing URL needs a deliberate decision: keep, improve, consolidate, redirect or retire. This content and redirect map is one of the most important migration controls.
Use a decision matrix, not a platform preference
Score the current system against business fit, content flexibility, accessibility, security, performance, SEO control, integration needs, editor experience and maintenance cost. Weight the criteria based on the organisation’s actual priorities.
The decision is then explainable: retain what works, change what blocks the strategy and accept only the migration risk that creates meaningful long-term value.