“Our website needs work.” It sounds simple until you realize it can mean two completely different projects.

A redesign refreshes what’s already there: new visuals, tighter copy, reorganized pages—all sitting on the same foundation. A rebuild replaces that foundation—the structure underneath—not necessarily the platform itself. Think of it like converting a bungalow into a duplex: same plot, same address, but you’re rebuilding the structure to hold more than it was ever designed to. Sometimes that means reinforcing what’s already there (new hosting resources, a heavier codebase). Other times it means adding a new floor on a structure that can already handle the load (a new interface layered over existing features). In both cases the structure itself changes so the site can do more than it could before. A redesign never touches that structure; it just repaints what’s already standing.

Confuse the two and you either overpay for a fresh coat of paint on a cracked foundation, or tear down something that only needed a refresh. Here’s a practical way to tell which one you’re actually dealing with.

When a redesign is genuinely enough

If the platform underneath is solid, current, and reasonably well-built, but the site looks dated or has grown messy through years of small edits, a redesign usually does the job. The same is true if the core structure—your main pages and how visitors move between them—still makes sense and only needs a visual and content refresh.

A redesign is faster, cheaper, and lower risk because you’re working with what already exists instead of replacing it wholesale.

When you actually need a rebuild

A rebuild becomes necessary when the problems go deeper than the surface:

• The site runs on an outdated or unsupported platform that breaks every time you try to update it.
• It was never built with performance or accessibility in mind, so the code fights every optimization instead of supporting it.
• Security is a recurring issue—frequent compromises or old, unpatched software with known vulnerabilities.
• The business has changed significantly (for example, a service business pivoting to e-commerce) and the existing structure simply can’t support what you need now, no matter how you redesign the surface.

What is the middle ground for website projects: the partial rebuild?

Not every project is purely one or the other. You can keep your content management system and most of your content while rebuilding only the weak spots—swapping an outdated page builder for a lighter, faster one, or rebuilding just the e-commerce section while leaving the rest alone. This is often the most cost-effective path when only part of the site is actually causing the problem.

Questions worth asking before you decide

• Is the platform still receiving security updates?
• Does the site actually work well on mobile, or is it fighting the code the whole way?
• Would a redesign fix the real complaint, or just make the same structural problem look nicer?
• Has the business changed enough that the site’s structure genuinely no longer fits?

What should you do if you're still not sure whether to redesign or rebuild?

Start with a redesign. It’s cheaper and lower risk. If it turns out the platform genuinely can’t support what you need, that becomes obvious quickly—and you’ll have concrete evidence for a rebuild conversation instead of a guess.