What each one means
The two words are often used as if they meant the same thing. They describe different work, with different costs and different risks.
| Redesign | Full rebuild | |
|---|---|---|
| What changes | Layout, visual design, content and navigation | The platform, the code and usually the content model |
| What stays | The CMS, the hosting and most page addresses | The domain and, if you plan it, the addresses and the content |
| Main skills | Design, content and front-end work | Engineering, data migration and design |
| Typical trigger | The site looks dated or does not convert | The site is slow, fragile or cannot do what you need |
| Risk to search traffic | Low to medium, from changed content and structure | Medium to high, from changed addresses and templates |
| Relative cost | Lower | Higher |
Diagnose the platform before you decide
A common wrong decision here is to treat a platform problem as a design problem, or the reverse. A new design on a failing platform is money spent twice. A new platform for a site whose only fault is its appearance is risk taken for nothing.
- 01
Can your team publish and change pages without a developer?
What the answer tells youIf not, and the CMS cannot be fixed, the platform is part of the problem
- 02
Are pages fast on a phone, measured, not guessed?
What the answer tells youSlowness caused by the theme or page builder can sometimes be repaired. Slowness in the platform itself cannot
- 03
Is the software supported and updated?
What the answer tells youAn unsupported CMS or a tangle of outdated plugins is a security risk that design does not touch
- 04
Can the site do what the business needs next?
What the answer tells youNew languages, accounts, integrations or a catalog may be beyond the current platform
- 05
Do visitors find what they want and act?
What the answer tells youIf this is the only failure, the work is content, structure and design
- 06
Does the site reflect the brand?
What the answer tells youA visual gap alone is a redesign, or less
When each one fits
Choose a redesign when
- The CMS is sound and your editors are comfortable in it
- Speed and security are acceptable, or fixable within the platform
- The problems are appearance, messaging, navigation or conversion
- Page addresses can stay largely as they are
- You need a visible improvement soon
Choose a rebuild when
- Editors cannot work without developers, or avoid the CMS altogether
- The platform is unsupported, insecure or held together by plugins
- Performance problems come from the foundation
- The business needs features the platform cannot provide
- You are merging several sites or changing how content is structured
There is a third option that is smaller than both. A refresh updates colors, type and imagery on the existing templates. If the structure and the content work, it may be all you need.
What each option puts at risk
| Risk | In a redesign | In a rebuild |
|---|---|---|
| Search traffic | Removing or rewriting pages that ranked | Changed addresses without redirects, and lost metadata |
| Content | Good pages cut because they do not fit the new layout | Content lost or damaged in migration |
| Integrations | Forms and tracking broken by template changes | Every integration must be rebuilt and tested |
| Schedule | Content written late | Migration and edge cases found late |
| Editors | A new layout to learn | A new system to learn |
Every risk in this table is manageable with an audit before the work and a plan for redirects, content and tracking. Our website redesign planning checklist sets out the five stages, and they apply to a rebuild as much as to a redesign.
A worked example
Two companies with a site that looks dated
Both companies are invented. Each began by asking for a redesign.
- A law firmThe site is on a current, supported CMS. Staff publish articles weekly. Pages load quickly. The design is ten years old and the service pages are thin.
- Its decisionA redesign. New templates, rewritten service pages, the same platform and the same addresses.
- A training providerThe site runs on an outdated system with a page builder nobody understands. Editors email changes to a freelancer. Course pages are slow, and the firm now wants online booking and a second language.
- Its decisionA rebuild, with design and content in the same project. A new design on the old system would have left every real problem in place.
Both sites looked dated. Only one of them had a design problem.
A checklist to decide
Tick what is true. Two or more ticks suggest that a redesign alone will not solve the problem.
Signs you need a rebuild
0 of 7 checkedWhat to do next
Answer the six diagnostic questions with evidence, then run the checklist. If you are unsure what is wrong, a UX audit answers the design side, and a short technical review answers the platform side.
Our website redesign and website design pages explain how we approach each. You can also send us your address, and we will tell you which of the two we think you need.
Common questions
Is a rebuild always more expensive than a redesign?
Usually, because it includes engineering and migration on top of design. The comparison changes if a redesign on a weak platform has to be followed by a rebuild a year later. Then the cheaper option was the more expensive one. Diagnose the platform first, and price the full path.
Can we redesign now and rebuild later?
You can, when the platform is sound enough to carry the new design for a few years. If the platform is already failing, most of the redesign work will be thrown away at the rebuild, since templates rarely move between systems. Content and brand work do carry over.
Will either option hurt our search rankings?
Both can, and both can be done safely. The causes of loss are the same, namely removed pages, changed addresses without redirects and dropped metadata. A rebuild touches more of these at once, so it needs a more careful plan. Neither needs to cost traffic if the move is mapped page by page.
Can we keep our current design and only rebuild the platform?
Yes. A like-for-like rebuild keeps the appearance and replaces what is underneath. It suits sites whose design still works. In practice most teams use the occasion to fix the worst design problems too, since the templates are being rebuilt anyway.
