What is a website redesign?
The website redesign vs rebuild question sounds like jargon-splitting, but the two words describe genuinely different projects with different costs, different risks, and different problems they can solve. Getting the label right before you brief anyone is the cheapest decision you will make all year.
A redesign changes what visitors experience while keeping the machinery underneath. New visual design, new copy, new page layouts, better photography, a clearer enquiry journey: all of it applied to the existing platform, templates, and page structure. Think of repainting and refitting a house whose walls and wiring stay where they are. Done well, a redesign fixes problems of perception and persuasion: a site that looks five years older than the business, messaging that no longer matches what you sell, pages that never asked properly for the enquiry. Our website design service lives at this layer.
What is a website rebuild?
A rebuild replaces the machinery. The code, the templates, often the platform, and usually the page structure are built again from a clean base, informed by everything the old site got wrong. The visible design usually changes too, which is why the two terms blur together, but the defining feature of a rebuild is that the foundations are new. Walls and wiring, not just paint.
Rebuilds exist because some problems cannot be styled away. A theme carrying two hundred kilobytes of scripts nobody uses will be slow in any colour scheme. A page structure that buries services three clicks deep stays buried no matter how good the typography is. A platform your developer dreads touching gets more expensive to maintain every year. When the faults are in the structure, the honest fix is structural, which is exactly what a focused rebuild is for.
Redesign or rebuild: three questions that decide it
Strip the sales language away and the choice comes down to locating the problem in one of three layers. Ask the questions in order, because the deeper layers gate the shallower ones.
Is the problem visual or persuasive?
Symptoms: the site works and loads acceptably, but it looks dated next to competitors, the messaging is stale, visitors browse without enquiring, and you hesitate before sending a prospect the link. If the faults are all in what people see and read, a redesign addresses them. Test it honestly: if the site were beautiful tomorrow, would every complaint on your list be gone?
Is the problem structural?
Symptoms: the sitemap grew by accretion and no longer matches how customers buy, key services have no page of their own, adding a new page means bending a template that was never meant for it, and navigation needs local knowledge. Structure sits under design. A redesign on top of a broken structure is decoration on a maze, and this is where redesigns most often disappoint: the site looks new and behaves exactly as before.
Is the problem technical?
Symptoms: pages fail Core Web Vitals even after image compression and caching, the mobile experience is broken in ways the desktop theme cannot express, the platform is out of support, or every small change needs a developer and a prayer. Technical faults are the clearest rebuild signal of all, because no amount of surface work touches them.
Decision table: matching the fault to the fix
The pattern of symptoms usually points at the right project. These are the pairings we see most often across sites we audit:
| What you observe | Layer | Usually calls for |
|---|---|---|
| Dated look, weak messaging, low trust, sound build | Visual / persuasive | Redesign |
| One weak page, poor form, missing proof, unclear CTA | Visual, localised | Targeted fixes, no project |
| Navigation confuses visitors, services buried, pages missing | Structural | Rebuild (or restructure within one) |
| Slow after optimisation, fails Core Web Vitals, fragile templates | Technical | Rebuild |
| Platform unsupported, edits need a developer, plugins fighting | Technical | Rebuild |
| Looks dated AND slow AND structure is wrong | All three | Rebuild, with design inside it |
Notice the second row. A surprising share of sites that feel like they need a big project actually have two or three localised faults, which is why the table has an exit that costs days rather than months. More on that below.
Cost, effort, and risk: the honest trade-offs
Across the UK market, a redesign is typically the smaller project: less time, less money, less disruption, because the platform and content structure carry over. A rebuild costs more and takes longer because it includes most of the design work plus everything underneath it. Those are generalisations, and the ranges overlap; a light rebuild of a five-page site can cost less than a heavy redesign of a fifty-page one. For the actual UK price bands and how a redesign project breaks into stages, see our guide to website redesign cost and process.
Risk is the more interesting comparison. A redesign carries persuasion risk: you can spend the budget and change nothing that was actually broken. A rebuild carries execution risk, and the sharpest edge is search: URLs, content, and internal links changing at once is precisely the scenario Google's site move documentation exists to manage, and handled carelessly it costs rankings the site took years to earn. Neither risk is a reason to avoid the right project. Both are reasons to avoid the wrong one.
There is also a case for deliberate incrementalism. Nielsen Norman Group has long argued, in its comparison of radical versus incremental redesign, that evolving a working site usually beats replacing it, because each small change can be measured and reversed. The exception they allow is when the current foundation cannot support where you need to go, which is a fair one-sentence summary of when a rebuild is justified.
When neither is needed: the case for targeted fixes
The option the industry rarely leads with: do neither. If the build is sound and the structure works, but enquiries are weak, the cause is usually a short list of specific faults, the same ones we catalogued in why websites fail to convert: an unclear headline, a demanding form, proof that is missing or anonymous, one slow template, a buried call to action. Every one of those ships as an individual fix on the existing site, in days, at a fraction of project cost, and each can be measured against the month before.
The trap that pushes people past this option is boredom. You look at your own site every day; your visitors see it once. "We are tired of it" is a real feeling and a poor brief. Fix the faults the evidence shows, and if the tiredness remains, at least the redesign that follows will be built on a site that already converts.
How to decide with evidence instead of opinion
The wrong way to choose is to ask a seller, because redesign shops diagnose design problems and rebuild shops diagnose build problems with impressive consistency. The right way is to score the site's layers independently, then read the scores. Speed and technical health are measurable with free tools. Structure and persuasion take a more deliberate look, which is what a structured review provides; we wrote up the twelve signs a website needs a redesign as a self-assessment you can run in an afternoon, and our free scored CRISP audit grades the layers in about a minute.
Then let the layer with the failing grade choose the project. Surface failing, foundations sound: redesign. Foundations failing: rebuild, and fold the design work into it rather than paying for it twice. Everything sound except two or three specifics: fix the specifics and bank the difference. The label on the invoice matters far less than whether the project you buy touches the layer that is actually broken.
Frequently asked questions
Is a website rebuild more expensive than a redesign?
Usually, because a rebuild includes most of the design work plus the structural and technical work underneath it. But the comparison that matters is against the problem, not between the two options. A cheap redesign applied to a structural problem costs more in the end, because the problem survives it and you pay twice. Match the spend to the actual fault before comparing prices.
Can I redesign my website without losing SEO?
Yes, if URLs, page content, and internal links are preserved and the new templates load at least as fast as the old ones. A visual redesign that keeps structure intact carries modest SEO risk. The risk climbs sharply when a redesign quietly becomes a restructure: URLs change, pages merge or vanish, and redirects are an afterthought. Decide which project you are running before it starts.
How do I know if my website needs a rebuild rather than a redesign?
Look at where the problems live. If the site is slow after optimisation, breaks when edited, cannot support the pages or features you need, or sits on a platform nobody wants to maintain, the fault is under the surface and a rebuild addresses it. If the site works but looks dated or persuades badly, that is redesign territory. An audit that scores both layers tells you which case you are in.
When is neither a redesign nor a rebuild the right choice?
When the evidence points at a small number of specific faults: a weak call to action, a demanding enquiry form, missing proof, or a handful of slow pages. Those are targeted fixes that ship in days on the existing site. Sites we audit often need exactly this, not a project. Reach for a redesign or rebuild only when problems are spread across the whole site or baked into its foundations.