Website Relaunch vs New Website: When to Restart From Scratch
When your existing website isn't working, the choice is between redesigning it (refresh on same foundation) or rebuilding from scratch. The specific decision framework — with the tradeoffs of each and the situations where the wrong choice creates months of wasted work.

Rebuild from scratch when your current site is over 5 years old, uses abandoned technology (Flash, jQuery-heavy WordPress themes, deprecated builders), or has fundamental structural problems (URL structure, information architecture, mobile handling). Relaunch (redesign on same foundation) when the current site works structurally but looks or reads dated. Rebuilds cost more upfront but produce better long-term outcomes when the foundation is broken.
The specific difference between relaunch and rebuild
These terms get used interchangeably in casual conversation, but they mean specifically different things:
Website relaunch (redesign): Keeping the existing site's foundation — same content management system, same URL structure, same underlying architecture — and updating the visual design, copy, and layout on top. Faster and cheaper. Preserves SEO. Works when the foundation is sound.
Website rebuild: Starting from scratch. New content management system, new URL structure (with redirects from old URLs), new information architecture, new visual design, new copy. Slower and more expensive. Requires SEO migration work. Necessary when the foundation is broken.
The choice isn't primarily about how bad the current site looks — it's about whether the underlying foundation can support what you need to do next. A great-looking site built on abandoned technology needs a rebuild. A dated-looking site on solid technology needs a relaunch.
Signs you need a full rebuild
The specific indicators that a rebuild (not a relaunch) is the right call:
- Site is over 5 years old. The underlying technology stack has usually moved on. Old WordPress themes, old CMS platforms, old builders (Adobe Muse, Adobe Flash, Weebly, GoDaddy Website Builder pre-2020) create structural problems that redesign can't solve.
- Uses deprecated or abandoned technology. Flash-based sites, jQuery-heavy sites without modern optimization, sites built on discontinued platforms (Adobe Muse, Weebly Classic, iWeb). Trying to redesign on top of these makes the underlying problems worse.
- Mobile is fundamentally broken. The current site has a separate mobile version rather than responsive design. Or it responds badly across breakpoints. Or it uses non-standard mobile patterns that hurt UX. Mobile-first design requires structural changes, not surface changes.
- URL structure is a mess. Pages at URLs like /page.php?id=47 or /index.html?section=services. Modern SEO requires clean human-readable URLs, which requires rebuilding rather than redesigning.
- Information architecture doesn't match what your business does now. Site structure reflects an older version of your business — different services, different positioning, different target customer. Redesigning within the wrong architecture perpetuates the wrong architecture.
- You can't easily update it. Making a simple change requires calling your developer, waiting a week, and paying $150/hour. Modern sites should be updatable by non-technical users for content changes.
- Core Web Vitals fail. Google's technical performance metrics (loading, interactivity, visual stability) are below thresholds. On old technology, this is usually not fixable without rebuilding.
If 3 or more of the above apply, rebuild is almost certainly the right call. Redesigning on a broken foundation produces short-term visual improvement followed by the same structural problems reappearing within 12-18 months.
Signs you need only a relaunch (redesign)
The specific indicators that a relaunch (not a rebuild) is enough:
- Site is under 3 years old on modern technology. WordPress with a current theme, Squarespace 7.1, Webflow — these platforms can accept significant visual redesign without needing to change the underlying structure.
- Mobile responsive is already working. Site adapts across breakpoints without major bugs. This is a foundational requirement — if it's working, you don't need to rebuild to get it.
- Core Web Vitals pass or are borderline. Performance is acceptable. Small optimizations during redesign can close borderline gaps.
- URL structure is clean. Human-readable URLs like /services/roof-replacement. If these already exist, preserving them during redesign preserves SEO.
- Content management is workable. You can make content updates without technical help, even if the process is a bit clunky. Redesign can improve the interface without rebuilding the underlying system.
- Information architecture generally reflects your current business. Same core services, same customer, same positioning. Refresh needed on visual design and copy, not on structure.
- Primary issue is 'it looks dated.' Visual design feels 5-year-old-ish. Typography, colors, imagery styles have moved on. This is exactly what redesign solves.
If most of the above apply, relaunch is the efficient choice. Cost is typically 30-60% of a full rebuild, timeline is 40-60% shorter, and SEO impact is minimal because you're preserving URLs and structure.
The specific cost and timeline differences
Rough numbers for small business websites in the OC market (2026):
Relaunch (redesign on existing foundation):
- Cost: $2,000-$5,000 typical for a small business site
- Timeline: 2-6 weeks for standard scope
- SEO impact: Minimal — URLs preserved, structure preserved
- Best fit: Sites 1-3 years old on modern platforms with sound underlying structure
Full rebuild:
- Cost: $4,500-$12,000 typical for a small business site
- Timeline: 1 day to 12 weeks depending on model (same-day flat-rate to traditional agency)
- SEO impact: Requires migration work — old URLs redirected to new URLs, sitemap resubmitted, but generally SEO recovers within 30-60 days if migration is done correctly
- Best fit: Sites 5+ years old, sites on abandoned technology, sites with fundamental structural problems
The specific insight: Rebuilds cost 2-3x more upfront but usually cost less over 5 years because the alternative is repeatedly relaunching on a broken foundation. A $3,000 relaunch every 2 years is $7,500 over 5 years; a single $4,500 rebuild plus modest maintenance is often cheaper and produces better outcomes.
What to do about SEO during a rebuild
The single biggest fear about rebuilding is "will I lose my Google rankings?" The specific answer: not if you handle the migration correctly.
The specific technical steps for preserving SEO during a rebuild:
- 301 redirect every old URL to its new equivalent. Every page that exists on the current site needs a mapping to where it lives on the new site. This tells Google "this content moved here" and preserves the ranking authority.
- Preserve content that ranks. Pages currently ranking well for specific queries — bring the core content over to the new site (rewritten as needed, but the substantive material preserved).
- Submit new sitemap to Google Search Console immediately after launch. Tells Google to re-crawl and re-index the new site quickly.
- Verify redirects work. Use tools like Screaming Frog or a simple redirect checker to confirm every old URL properly forwards to its new home.
- Watch Search Console for 30-60 days. Rankings typically dip briefly (2-4 weeks) then recover. If they don't recover, something in the migration went wrong and needs fixing.
The specific risk is that inexperienced or careless designers skip the redirect work, treat the launch as "just a new site," and effectively delete years of SEO investment. Insist on written redirect plans before signing a rebuild contract.
The decision framework, summarized
Use this specific decision tree:
Step 1: Count the "rebuild signs" that apply. If 3+, rebuild is the right call regardless of what the current site looks like.
Step 2: If 0-2 rebuild signs apply, check the "relaunch signs." If most apply, relaunch is the efficient choice.
Step 3: If the situation is ambiguous (some rebuild signs, some relaunch signs), the tiebreaker is the underlying platform. Modern platform (WordPress 6+, Squarespace 7.1+, Webflow, custom Next.js) = relaunch usually works. Old or abandoned platform (WordPress on abandoned themes, Wix Classic, GoDaddy Website Builder pre-2020, Adobe Muse, iWeb) = rebuild.
Step 4: If cost is a hard constraint, the honest answer is that a bad rebuild is worse than a good relaunch. If you can't afford to rebuild well, relaunch what you have and rebuild later when budget allows. Don't attempt a rebuild on a budget that produces a worse outcome than what you started with.
The specific mistake most business owners make: relaunching a site that needs a rebuild, spending $3,000 on visual refresh, then discovering 12 months later that the underlying problems are still there. The $3,000 becomes wasted spending; the rebuild still needs to happen; total cost is higher than if the rebuild had been done initially.
The reverse mistake — rebuilding a site that just needed relaunch — is less common but wastes 2x the money on unnecessary work. Assessment matters.
Frequently asked questions
How can I tell if my website is on abandoned technology?
Will I lose my Google rankings during a rebuild?
Is same-day rebuild possible, or do I need the traditional 8-12 week timeline?
What if I like some things about my current site but not others?
How often should a website get relaunched or rebuilt?
Ready to launch in one focused day?
A custom website and brand for your business. $4,500 flat — Year 1 of the Care Plan included.
Reserve Your Launch Day →