Website Redesign vs New Website: Which Do You Need?
A rebuild is the more expensive answer and it is not always the better one. The deciding question is whether the problem is the surface or the structure.
The decision is usually made before it is examined. Someone concludes the site looks dated, a rebuild is scoped, and nobody asks whether the appearance was the problem. Frequently it was not.
What Each One Means
A redesign changes how the existing site looks and is arranged while keeping the underlying platform, content and URLs. Website redesign covers the scope.
A new website replaces the platform, the templates, and usually the URL structure. It is a larger project with a larger set of risks attached.
The Question That Decides It
Is the problem on the surface or underneath it? Appearance, layout, messaging and structure are surface problems, and a redesign fixes them. Platform limitations, unfixable performance, an unmaintainable codebase or an inability to add functionality are structural, and a redesign does not.
The complaint that usually starts these projects — "it looks dated" — is a surface complaint. But it is frequently a proxy for "it is not producing enquiries", which may have nothing to do with either the surface or the structure.
What a Rebuild Puts at Risk
Two things, and neither usually appears in a proposal.
The first is your URLs. A new platform imposes a new structure, and every old URL becomes a 404 unless a complete redirect map is built. Sites lose years of accumulated search visibility this way — see SEO migration.
The second is content. Pages that do not fit the new templates get shortened, and it is frequently the substantial ones — the detailed service pages — that were doing the ranking.
When a Rebuild Is Genuinely Right
- The platform cannot do what the business now needs, and no amount of design changes that.
- Nobody can maintain the codebase, and changes are expensive or impossible.
- Performance problems are server-side and unfixable within the current setup.
- The information architecture is fundamentally wrong and cannot be corrected within the existing structure.
When a Redesign Is Enough
- The site works, is maintainable, and simply looks out of date.
- The structure is broadly right and some pages need rewriting.
- Conversion is the problem, which is usually about specific pages rather than the whole site.
- Budget is limited and the current platform is adequate.
The Third Option Nobody Proposes
Frequently the answer is neither: three specific changes. Faster pages, clearer service information, a contact route that works on a phone. That is a fortnight of work rather than a project, and it is not what anyone in the process is incentivised to recommend.
Establishing what is actually failing — through analytics, search data and a look at the funnel — takes a few hours and regularly redirects a large budget toward a much smaller change. A website design consultation is that exercise.
The Decision Rule
Rebuild only if the platform or the codebase is genuinely blocking you. Everything else is a redesign or smaller.
And before either, find out what is actually wrong. "It looks dated" and "it produces no enquiries" have different causes, and only one of them is fixed by a new design.
Frequently asked questions
If the platform cannot do what the business needs, or the codebase is unmaintainable, or performance problems are server-side and unfixable. Everything else is a redesign or smaller.
It can, badly, if URLs change without a complete redirect map or content is shortened to fit new templates. Both are preventable and both are common.
Often yes, and it is worth insisting on. Many platforms allow custom URL patterns; accepting the platform default is a choice rather than a requirement.
Usually, because it retains the platform, content and URLs. But a redesign that does not fix a structural problem is money spent on the wrong thing, which is the more expensive mistake.



