A redesign changes what your website looks like and how it is organized while keeping the same platform underneath; a rebuild replaces that foundation, the platform, code, and structure, usually with a new design on top. Choose a redesign when the problem is the surface, like a dated look, weak conversion, or off-brand pages, and a rebuild when the platform itself is blocking the business, because no amount of new design fixes a foundation you have outgrown.
There are really three sizes of website project, not two. A refresh tweaks the surface of the site you have. A redesign rethinks how it looks and how it is organized. A rebuild goes deeper still and replaces the foundation underneath. This is the decision between the last two, which is where most of the money and most of the confusion sits.
The line between them is simple once you name it: a redesign changes the surface, a rebuild changes the foundation. A redesign gives you a new look, layout, and content structure on the same platform. A rebuild replaces the platform, the code, and the architecture, and almost always ships a new design along with it.
The expensive mistake runs in both directions. Companies buy a redesign to fix a problem that lives in the foundation, then wonder why the new site still can't do what they need. Others pay for a full rebuild when a redesign would have done the job. The way to avoid both is to diagnose the real problem before you pick the size of the project.
A redesign changes what visitors see and how the site is structured while keeping the platform it runs on. New visual design, new layouts, reorganized navigation and content, often new copy. The CMS, the code, and the hosting stay where they are.
It is the right call when the problems are on the surface. The site looks dated next to competitors, it is off-brand after a rebrand, the messaging no longer fits, or pages simply aren't converting. If the foundation is sound and only the surface has aged, a redesign fixes it faster and cheaper than tearing everything down.
A rebuild replaces the foundation: the platform, the code, and the information architecture. It is effectively a replatform with a redesign riding along, since you rarely rebuild the structure and keep the old look.
You rebuild when the platform has started blocking the business rather than serving it. You can't add the integration or feature you need, the maintenance and security burden has crept up, or the accumulated technical debt makes every change slow and risky. Past that point, patching the surface again just delays the real fix.
A redesign that keeps its URLs and content usually carries the rankings straight over. A rebuild is where traffic gets lost, because changing URLs without redirects, or dropping content and metadata in the migration, is exactly how a site falls out of search results.
That risk is manageable, not a reason to avoid rebuilding. A serious rebuild plans the URL map, the redirects, and the content migration up front, so the new foundation launches without surrendering the equity the old site earned.
List the three things that are actually wrong with your current site, then match them to the size of the project.
A redesign changes the surface (the look, layout, and content structure) while keeping the same platform. A rebuild replaces the foundation: the platform, code, and architecture, usually with a new design on top. One changes appearance; the other changes capability.
A rebuild costs more and takes longer, because you are replacing the foundation and not just the surface. A redesign is faster and cheaper. If budget is tight and the foundation is sound, a redesign is the efficient choice.
A redesign that keeps its URLs and content usually preserves rankings. A rebuild can hurt SEO if URLs change without redirects or content isn't migrated faithfully. Planned properly, with a URL map and redirects, a rebuild can carry rankings over intact.
List the three things wrong with your site. If they are about how it looks or converts, that's a redesign. If they are about what it can't do (integrate, scale, be maintained or secured), that's a rebuild, and a redesign won't fix them.
Closely related. Replatforming is moving to a new platform or CMS; a rebuild is that plus rebuilding the architecture and, typically, the design on top. In practice most rebuilds are a replatform and a redesign done together.
A 30-minute call. We'll listen, dig into the details, and tell you honestly whether we're the right partner, or point you to someone who is.
Book Intro Call ↗