Choosing between a website redesign or rebuild is not primarily a visual decision. The right answer depends on the condition of the current site, how well its structure supports the business and whether its technical foundation is still worth keeping.
What is the difference?
A redesign can range from a visual refresh to substantial changes in structure, content and user experience while preserving useful parts of the existing system. A rebuild replaces much more of the underlying implementation and is appropriate when the current foundation creates more constraints than value.
A redesign may be enough when…
- the CMS and technical setup are stable and maintainable;
- the main problem is hierarchy, visual design or content clarity;
- important integrations already work well;
- performance issues can be resolved without replacing the architecture;
- the current content model still fits the business.
A rebuild is usually worth considering when…
- editing the website is fragile or unnecessarily difficult;
- the theme, plugins or custom code are obsolete or heavily constrained;
- mobile UX requires structural rather than cosmetic changes;
- the site has accumulated technical debt that affects performance or security;
- the business model, information architecture or required functionality has changed substantially.
Do not choose the platform first
Moving to a new platform does not automatically solve poor content, unclear journeys or weak positioning. Likewise, staying on the current platform is not a virtue if it prevents the website from doing its job. Start by defining the problems and then decide how much of the current site deserves to remain.
Audit before you commit
A focused review can separate what should be kept, improved or replaced. That makes the redesign brief more accurate and reduces the risk of paying to reproduce old problems in a newer visual style.
Explore our website redesign service or start with a website audit if the right level of intervention is still unclear.
