What this can look like in practice
A single symptom rarely tells the whole story. These are some of the signs worth checking before deciding what needs to change.
- The business has changed but the website structure cannot represent it
- Important pages are difficult to publish, measure or improve
- Mobile journeys or enquiry paths are structurally weak
- The platform creates persistent performance, security or maintenance constraints
- Repeated surface-level fixes do not address the underlying problem
What to check next
Start with the parts that can be verified. This helps avoid expensive changes based on assumptions.
- Define the commercial problem before choosing a redesign
- Preserve useful URLs, content and search equity where possible
- Separate cosmetic changes from structural requirements
- Identify what must become measurable after the rebuild
- Set success criteria before development starts
Decision point
The practical takeaway
A redesign should solve a defined business constraint, not merely make the website look newer.