A redesign changes how your site looks. A rebuild changes how it is built. Most small businesses asking this question need the first one, not the second. The exception is when the platform itself is blocking you: slow load times that do not improve, a CMS your team cannot update, security vulnerabilities baked into the architecture. When the platform is fine and the problem is visual, a redesign is faster and costs less.
What each one actually means
A redesign keeps your existing platform and code, then replaces the visual design. New layouts, updated branding, better navigation. Your content management system stays the same. Your URLs stay the same. Your team keeps using the same admin tools they already know. Search engine history carries over with minimal disruption.
A rebuild starts with the technical foundation. You might be switching from WordPress to a headless CMS, from a custom PHP site to a modern framework, or from a proprietary platform that no longer receives updates to something maintainable. The design may come along for the ride, or it may get replaced at the same time, but the core motivation is technical.
The two are not mutually exclusive. Some projects do both. A business that has been running on a 2015 Joomla build with an equally dated design may need to replace the entire thing. But treating them as one package when only one is broken is where projects overshoot their budget.
The case for a redesign
A redesign is usually the right move when:
- The site looks visibly outdated compared to competitors
- Visitors are confused by navigation or cannot find the main call to action
- The brand has evolved and the site no longer reflects it
- Mobile layout is broken or cramped
- Content is out of date and the page structure makes updates feel like a chore
A redesign is not a workaround. It solves real problems. Most businesses that contact me saying they need a "new website" actually need a redesign of the one they have. The bones are fine. The presentation is the issue.
At the Starter level ($4,500), a redesign typically covers a focused site with updated design, revised copy structure, and basic SEO setup. The Growth tier ($8,500 to $15,000) covers more complex sites with custom functionality, stronger content architecture, and performance tuning. More detail at /packages.
The case for a rebuild
A rebuild makes sense when the platform is actively holding you back. Specific signs:
End-of-life software. If your site is running on a version of WordPress, Joomla, Drupal, or a proprietary builder that no longer receives security patches, you are one missed update away from a real problem. Security vulnerabilities that live in the architecture cannot be patched with a redesign.
Performance that does not improve. Some platforms have speed ceilings baked into their architecture. Shared hosting configurations, unoptimized rendering pipelines, and plugin bloat can produce slow sites that do not respond to normal optimization. If your Core Web Vitals are poor and targeted improvements are not moving the numbers, the problem may be structural.
CMS your team cannot use. If updating a page requires a developer every time, or the admin interface is so broken that content goes stale because no one will touch it, the system is costing you money in a way that shows up slowly. A rebuild with a better-fit CMS can pay for itself.
Integrations that do not exist. If your business needs a booking system, a client portal, custom intake forms, or CRM sync that the current platform cannot support, a rebuild opens options the current stack will not.
Vendor lock-in with no exit. Some proprietary platforms export nothing usable. If the company building your site has no clean export and is raising prices, rebuilding on something you own is worth the short-term cost.
Optimizely's documentation on CMS migration triggers lists end-of-life software and performance and security risks as the primary signals. Both show up in the same two or three places for most small business sites.
The layer that most proposals ignore
Your site has two layers: what visitors see, and how it is built underneath.
Most agencies treat these as a package. They are not. You can redesign the front end without touching the back end. You can also rebuild the back end while keeping a design that is still working. The two decisions should be made separately, based on which layer is actually the problem.
FatLab Web Support's breakdown of the refresh, redesign, rebuild spectrum makes this point plainly: understanding the separation between the design layer and the technical layer is often the difference between a $15,000 project and a $60,000 one.
If a developer tells you the site needs a full rebuild because of how it was built, ask them to be specific. What is failing? Is it a security issue? A performance issue? A maintainability issue? If the answer is "it is not how I would have built it," that is not a reason to rebuild.
Side-by-side comparison
| Factor | Redesign | Rebuild |
|---|---|---|
| What changes | Visual design, layout, content structure | Platform, code base, architecture |
| Platform migration | No | Usually yes |
| Timeline | 4 to 8 weeks (small business) | 3 to 6 months |
| Cost range | $3,500 to $20,000 | $15,000 to $50,000+ |
| SEO disruption risk | Low (URLs preserved) | Higher (requires 301 redirects, reindexing) |
| Best for | Outdated look, brand refresh, UX problems | Broken platform, security issues, scale limits |
| When to avoid | When the platform is actively broken | When the design is the actual problem |
How to decide
Start by naming the actual problem. Not "the site feels old" as a feeling, but what specific thing is failing.
If the problem is visual: The site looks dated. Navigation is confusing. Brand identity has changed. Mobile layout is cramped. These are redesign problems.
If the problem is technical: Pages load slowly despite optimization. The CMS is no longer receiving updates. Your team cannot update content without help. A key integration does not exist on this platform. These are rebuild problems.
If it is both: Do them together. A site running on abandoned software with a decade-old design needs a fresh start. But be honest about the order of priority so the project does not balloon.
Most small business sites need a redesign. The platform is almost never the problem for a local service business on a standard WordPress or Squarespace install. The problem is usually that the site was built once and never touched, the design is from 2016, and the content was written by someone who has since left the company.
The SEO question
A redesign with preserved URLs and proper 301 redirects for any structural changes carries minimal SEO risk. Search engines continue to index the same pages with the same authority.
A rebuild with a platform change requires a full redirect map, sitemap resubmission, and monitoring for crawl errors after launch. Organic traffic typically takes several weeks to a few months to restabilize after a rebuild with URL changes. This is a manageable process, not a reason to avoid a rebuild when one is genuinely warranted. It is a cost to factor in honestly when the rebuild is optional.
Not sure which situation applies to your site? A free audit covers what the current site is doing, where it is failing, and whether the problem is design-layer or platform-layer. Get in touch.
Frequently asked questions
- What is the difference between a website redesign and a rebuild?
- A redesign updates the visual layer of your site, look, layout, branding, and navigation, while leaving the underlying platform and code intact. A rebuild replaces the technical foundation, which may or may not involve changing the design. A plumber whose WordPress site looks dated but still loads fast probably needs a redesign. A law firm whose site is built on abandoned software they cannot update probably needs a rebuild.
- How much does a website redesign cost vs a full rebuild?
- A redesign for a small business site typically starts around $3,500 and can run to $20,000 or more, depending on the number of pages and whether content is included. A rebuild, which involves switching platforms or re-architecting the code, generally runs $15,000 to $50,000 or higher for a business site. The overlap is real. A rebuild of a modest site can cost the same as a redesign of a complex one.
- How do I know if the problem is my platform or just my design?
- If the site looks bad but your team can still update content, load times are acceptable, and nothing is broken at a technical level, the platform is probably fine. If you are fighting the CMS every time you post something, pages are slow despite optimization attempts, plugins are no longer maintained, or the site was built on a version of software that no longer receives security patches, the platform is the problem.
- Can I redesign my site without switching platforms?
- Yes, and that is often the better move. The design layer and the technical layer are separate. You can replace the visual identity of a WordPress site without changing a line of backend code. A new theme, updated templates, and revised page layouts are all design-layer changes. No platform migration required.
- How long does a website redesign take vs a rebuild?
- A redesign of a small business site typically takes 4 to 8 weeks. A rebuild, including platform selection, content migration, and QA, typically takes 3 to 6 months. Timeline depends heavily on how much content needs to move, whether new features are in scope, and how quickly decisions get made on the client side.
- What should a Milwaukee small business choose, redesign or rebuild?
- Most local service businesses need a redesign, not a rebuild. The platform is rarely the problem for a plumber, law office, or local retailer with a modest site. The more common issue is that the design is outdated, the content is thin, or the site was never optimized for local search. A redesign with SEO attention usually solves those problems faster and for less money than a platform change.