Rebuild when the underlying platform, code, or CMS blocks growth—slow load times you can't fix, broken integrations, or a stack no developer wants to touch. Redesign when the foundation is sound but the visuals, messaging, or conversion path are dated. Rebuild fixes structure; redesign fixes surface. If the site works but underperforms, redesign first.
A redesign keeps your existing platform, URLs, and data model. You change layouts, copy, imagery, and components—but the plumbing stays. Typical scope: 3-6 weeks, one designer plus light dev. Choose this when Core Web Vitals are green, your CMS is fine (Shopify, Webflow, WordPress you control), and the real problem is that the site looks like 2019 or doesn't convert.
A rebuild replaces the foundation: new platform, new codebase, or new information architecture. Scope is 8-16 weeks and involves migration, redirects, and QA. Choose this when the platform itself is the ceiling—a custom PHP site no one can maintain, a Wix build you've outgrown, or a Shopify theme so hacked that every edit breaks two other things.
Use the numbers to decide, not gut feel. Run PageSpeed Insights or Lighthouse: if mobile LCP is over 4 seconds and it's the theme or hosting, that's a rebuild signal. If it's just heavy images and unminified assets, that's a redesign fix. Pull GA4 and your heatmaps (Hotjar, Microsoft Clarity): high traffic with a sub-1.5% conversion rate usually means messaging and layout, not code.
Watch for the maintenance tax. If small changes take days, plugins conflict, or you're paying a developer a retainer just to keep the lights on, the code is the problem—rebuild. A clean sign: you can't add a new page type or CMS field without breaking the build. No amount of visual redesign fixes a stack that fights you.
Protect your SEO either way, but especially on a rebuild. Redesigns usually keep URLs, so risk is low. Rebuilds change structure—map every old URL to a new one with 301 redirects, keep your title/meta patterns, and preserve schema markup. Crawl the old site with Screaming Frog first so nothing gets orphaned. Most post-rebuild traffic drops come from skipped redirects, not Google penalties.
Cost and risk scale with scope. A redesign is cheaper, faster, and lower-risk because you're not touching data or URLs—you can even ship it section by section. A rebuild is a bigger bet: budget for migration, staging, and a two-week overlap where both sites can be checked. Never rebuild and rebrand in the same sprint; you won't know which change moved the numbers.
When both are tempting, redesign first and measure. Ship a stronger homepage and key landing pages on your current platform, watch conversion for 4-6 weeks, then decide if the platform is still holding you back. This staged approach often reveals that the foundation was fine all along—and saves you a five-figure rebuild you didn't need.
Frequently asked
Is a redesign cheaper than a rebuild?
Usually yes—redesigns keep your platform and URLs, so they're faster and lower-risk. Rebuilds add migration, redirects, and QA, which typically doubles or triples the timeline and cost.
Will a rebuild hurt my SEO?
Only if you skip the migration basics. Map every old URL to a 301 redirect, preserve titles, meta, and schema, and crawl the old site with Screaming Frog first to catch orphaned pages.
How do I know if my platform is the real problem?
If simple edits take days, plugins conflict, or you can't add a page type without breaking the build, the platform is the ceiling—that's a rebuild signal, not a redesign one.
Can I redesign and rebuild at the same time?
You can, but it's risky. Change one variable at a time so you know what moved your metrics—redesign first, measure for 4-6 weeks, then rebuild only if the platform still limits you.
Free, concrete, yours to keep
Want this done for you — properly?
Get a free audit of your rankings and AI-answer presence. Real findings within days, no sales deck.