Website redesign vs rebuild: how to decide

Website redesign vs rebuild: how to decide

A redesign keeps your existing site structure and often your backend, touching mainly the look, feel, and front-end code. A rebuild starts from scratch—new architecture, new technology choices, sometimes a different platform altogether. Redesigns suit businesses that already have solid workflows but look dated; rebuilds suit those whose foundation no longer fits their goals or the way they actually work.

The choice isn't just aesthetic. It touches cost, launch speed, risk to your search traffic, how much of your old site you can salvage, and whether you'll own the finished code. Most small businesses and freelancers assume redesign is the cheaper, faster route—but that's not always true once you factor in what's actually broken underneath.

Price and total cost of ownership

Redesign: often higher hidden costs

A redesign looks cheaper on the surface. You're not rebuilding the database, the server infrastructure, or the authentication layer. Agencies quote it as "surface work," so it sits somewhere between £1,500 and £4,000 for a small business.

But redesigns on old platforms—WordPress with ten years of plugin bloat, a 1990s custom CMS, or a Wix template nobody wants to touch—get expensive fast. You're preserving legacy code while bolting new design on top. Each page design iteration takes longer because the back-end constraints are real and immovable. If your old site runs on PHP 5.6 and you want a modern form integrations, suddenly you're paying for adapters, workarounds, and more revision rounds.

Rebuild: clear upfront cost, no "surprise" legacy debt

A rebuild from scratch (in Next.js, Strapi, whatever modern stack you choose) typically costs more upfront—£487 to £2,797 depending on scope—but the bill is transparent. You're not paying for three sets of revision rounds because the developer is wrestling with ancient code. You're not discovering halfway through that the old WordPress theme can't play nicely with your new payment processor.

For a B2B SaaS business with more than 10 pages, complex user workflows, or multiple integrations, rebuilds often cost less total outlay than trying to maintain and redesign an ageing platform. A non-profit running events, memberships, and newsletter signups on a template builder might spend £800 over the first year keeping it functional; rebuilding to something maintainable costs more initially but saves money in year two and three.

Hybrid approach: redesign the front-end, rebuild the backend

You don't have to choose. Some businesses redesign the visual layer (new design system, new CSS, new fonts) while simultaneously replacing the backend (old custom PHP replaced with a modern API, WordPress swapped for Strapi, legacy database replaced with Postgres). This sits between a full redesign and a full rebuild in cost—typically 15–25% more than a pure redesign, but radically more flexible long-term.

This works well for service businesses (consultancies, agencies, recruitment firms) where the old site has decent information architecture but runs on a tech stack that's becoming hard to hire for or maintain.

Time to launch

Redesign: often slower than promised

Redesigns get held up by the legacy platform's constraints. If your old site is a WordPress installation with 40 plugins, your designer can't test the new design in isolation—they have to keep testing with all that baggage. If you're redesigning a Wix site but want to add a booking calendar that Wix doesn't play nicely with, suddenly you're in scope conversations that weren't on the original plan.

Most redesigns quote 4–8 weeks because they're waiting for approvals on each page redesign before the developer tries to implement it into the old codebase. You'll see "final testing" and "compatibility checking" eating two weeks at the end.

Rebuild: faster to launch, predictable timeline

A rebuild from a blank slate often launches faster than a redesign of a complex old site. There's no legacy code to retrofit new design into. The designer and developer work in parallel: the designer shows you high-fidelity mockups in the first week, you pick a direction, and the developer builds it clean while you're reviewing copy.

Most bespoke rebuilds on modern platforms ship within 1–2 weeks for a brochure site (5–7 pages), and 3–4 weeks for something with integrations or a CMS. That's not because bespoke is magical—it's because you're not fighting an old architecture. Review Sitewright's how-it-works process if you want to see a concrete timeline.

Incremental refresh as a third path

There's also a middle option nobody talks about: the phased redesign. Redesign one page per month, roll it live with proper redirects, monitor traffic, then move to the next page. This spreads cost across quarters, lets you test design changes with real users, and means you don't have a big launch day where everything breaks. It's slower overall but lower risk—especially for businesses that make money directly from their website (e-commerce, lead generation, SaaS signups).

SEO and traffic disruption

Redesign: sneaky SEO risk

Redesigns often damage search visibility because they're done carelessly. You change the URL structure slightly ("new-services" instead of "services"), forget 301 redirects, or rewrite all your page titles for the new design without checking which ones rank. Traffic drops aren't always immediate—sometimes it takes Google 6–12 weeks to recrawl and re-evaluate—but they're real.

The risk is higher if you're moving hosting, changing CMS platforms, or redesigning with a tool (like Wix or Squarespace) that bakes in URL restrictions you can't control. A redesign on WordPress to a WordPress redesign on Squarespace, for example, means losing all your old URLs unless you're willing to pay for redirects elsewhere (a proxy service, which costs £20–50/month and adds latency).

Recovery is 8–12 weeks of careful monitoring—resubmitting your sitemap to Google Search Console, checking for crawl errors, and hoping Google re-indexes at the same authority level.

Rebuild: controllable, but requires planning

Rebuilds aren't automatically safer, but you have more control. If you're rebuilding in Next.js with a clean architecture, you can map every old URL to its new equivalent before launch. You can set up your redirects at the server level (fast, no latency penalty), and Google crawls the new site cleanly.

The risk comes if you change your URL structure unnecessarily. Don't rename "services" to "our-offerings-and-solutions" just because you redesigned. Keep old slugs, redirect old URLs, and only restructure if your old URL scheme was genuinely broken.

A 301 redirect migration plan takes 2–3 days to plan properly (mapping old URLs to new ones, testing redirects, monitoring crawl in Search Console). It's non-negotiable. Skip this and your rebuild will tank your rankings, whereas a well-managed rebuild often sees traffic recover to pre-launch levels within 4–6 weeks.

Post-launch monitoring: the same for both

Whether you redesign or rebuild, you need to monitor Search Console, check your core Web Vitals, and watch your organic traffic closely for the first 6–8 weeks. Bad design choices (heavy images, render-blocking JavaScript, slow third-party scripts) will tank your Lighthouse scores faster in a rebuild because the old site probably had equally bad Lighthouse scores and you'll be compared to your own historical baseline.

Plan for a Core Web Vitals audit after launch if you're rebuilding, or redesigning with any platform change.

Code ownership and tech debt

Redesign: inherited complexity

When you redesign, you keep the old platform's constraints. If your WordPress site has a proprietary plugin that your previous agency built, you can't ditch it—only work around it. Your redesign designer has to learn that plugin's quirks, test within its limitations, and hope it's compatible with the new design.

You're also inheriting the old site's tech debt. If it was built on PHP 5.6 and hasn't been updated, your new design layers modern JavaScript on top of legacy server code. That creates maintenance headaches: small edits take longer because the platform is old, security patches lag, and when you eventually want to migrate off it, you'll have to migrate the redesigned version too.

Rebuild: you own the new foundation

A bespoke rebuild gives you clean code and (ideally) full ownership. If you choose the "Own It" tier with Sitewright, you receive the full GitHub repository and can deploy it anywhere, edit it yourself, or hand it to another developer—no vendor lock-in. Even on a recurring plan, you're not trapped in proprietary builder syntax; the code is Next.js and Tailwind, which any developer can work with.

You're also building on a modern stack from day one. No PHP 5.6 ghosts, no plugin dependencies, no "we have to keep this old library because too much code depends on it." If you want to add a new integration next year, it's a straightforward API call, not a plugin hunt.

When to change tech stack during a rebuild

Rebuilding is the moment to ask: do I still need WordPress? Should we move from Wix to something I control? Do we need a full e-commerce platform or just Stripe Checkout?

The answer depends on your actual workflow. If you're a photographer and Squarespace's portfolio tools genuinely save you hours per month, redesigning within Squarespace makes sense even if an agency would rather rebuild. If you're a SaaS with 50 integrations and Shopify keeps forcing you into their ecosystem, a rebuild with a headless CMS (like Strapi) gives you freedom Shopify never will.

For hiring, consider what developers you'll want long-term. WordPress skills are ubiquitous but saturated; Next.js developers command higher fees but are easier to retain if you're scaling. A non-profit with a small, committed tech volunteer? WordPress redesign. A B2B agency building a design portfolio? Bespoke rebuild.

Ongoing support and maintenance

Redesign: stuck with the old platform's support model

A redesigned WordPress site needs ongoing maintenance—plugin updates, security patches, PHP version upgrades. That's built into the cost of WordPress ownership. You either do it yourself (risky) or pay your agency £50–150/month for managed care.

Redesigns on proprietary builders (Wix, Squarespace, Webflow) include support by default—the platform handles updates—but you're paying monthly for a closed ecosystem. If you want to change something, you're locked into the builder's tools and pricing. Webflow, for example, charges £12–165/month just to host your site; add design work, and you're at £3,000+ annually for a small brochure site.

Rebuild: support depends on your choice

A bespoke rebuild on a modern stack has lower overhead. You're not patching plugins or chasing WordPress updates. Security patches come from your host (Vercel, Netlify, Cloudflare Pages) and your database provider—not from dozens of third-party plugins.

Ongoing edits are predictable too. Sitewright includes ~30 minutes of minor edits per month on every plan (copy changes, image swaps, price updates, team member additions). Bigger work—new pages, redesigns, integrations—is quoted upfront as a one-off, not a "surprise" when you discover your page builder doesn't support what you need.

For e-commerce, this matters a lot. Shopify's "easy to use" checkout comes with 2–3% transaction fees plus £29–229/month platform cost. A rebuild with Stripe Checkout and a basic CMS costs less than Shopify's base tier annually, and the fees stop if you pause or leave.

Launch logistics and traffic continuity

Redesign: simpler traffic management

A redesign usually stays on the same domain and same platform, so traffic doesn't interrupt. You redesign in staging, test it, then flip the switch. DNS doesn't change, SSL certificates don't change, your email routing doesn't change. It's low-friction.

The catch: if you're redesigning a slow site, you might not fix the speed problem. A WordPress site with heavy plugins remains heavy after a redesign. Traffic doesn't drop due to migration, but it might not grow either if your site still takes 4 seconds to load.

Rebuild: plan for dual environments

A rebuild means running old and new sites in parallel briefly. You need both live before you cut over. This requires:

• Cloning your old site's content (pages, blog posts, contact info) to the new platform
• Testing all forms, integrations, and workflows on the new site
• Setting up 301 redirects from old URLs to new ones
• Planning your cutover date (usually a Tuesday or Wednesday, not Friday)
• Keeping the old site live for 2–4 weeks post-launch as a safety net

It sounds complicated, but it takes 3–4 days of actual work spread over 2–3 weeks. The benefit: you can test the new site with real traffic before decommissioning the old one. If something breaks, you flip back without losing customers.

For non-profits managing event registrations or for B2B firms with complex lead workflows, this parallel-running window is invaluable. You spot bugs, validate forms, and check that all your integrations work before you're dependent on them.

Design quality and customisation

Redesign: constrained by the platform

Template-based platforms (Wix, Squarespace) offer preset layouts and colours. You can redesign within those constraints—pick a different template, change fonts, reorder sections—but you can't add a custom interaction that the platform doesn't natively support. Want a sticky navigation that animates on scroll? Squarespace can do basic versions; Wix will fight you.

WordPress with a custom theme has more flexibility, but you're still bound by the theme's HTML structure and CSS architecture. A designer can create a beautiful mockup, but the developer has to fit it into the theme, and sometimes the fit isn't perfect.

Bespoke redesigns (custom CSS for an existing WordPress theme) bridge the gap but multiply complexity. You're now maintaining both the theme's code and your custom overrides, which causes problems when the theme updates.

Rebuild: design-first, no compromises

A bespoke rebuild is designed first, coded to fit the design, not the other way around. If you want a custom micro-interaction—a form that reveals fields based on answers, a hero that parallaxes on scroll, a pricing table that switches between monthly and annual—it's built natively. No workarounds, no "the builder doesn't support that."

Quality also compounds over time. A rebuild on Next.js + Tailwind is easier to maintain and extend. Adding a new page isn't "find a template that's close and adjust it"; it's "build a new component from the design system and drop it in." That saves weeks in year two and year three.

For photographers, creatives, and design-led businesses, a bespoke rebuild often justifies its cost because the site is the portfolio. A template site looks like a template. A bespoke site can be completely unique.

Decision checklist

Redesign makes sense if:

• Your site's backend (database, integrations, hosting) works fine and you're happy with the platform
• Your current tech stack (WordPress, Squarespace, whatever) is something you're willing to stick with for 3+ years
• You need a refresh faster than a rebuild, and you're okay with 4–8 week timeline
• Your budget is under £2,000 upfront
• You don't need new integrations that the platform doesn't support
• Your search traffic is already healthy (no major SEO recovery needed)

Rebuild makes sense if:

• Your site's backend is slow, inflexible, or hard to maintain
• You're switching platforms anyway (WordPress → Next.js, Squarespace → custom, Wix → headless CMS)
• You need new integrations or workflows the old platform won't support
• You want to own your code and design future-proof
• You're willing to spend 1–2 weeks on URL migration planning and search traffic monitoring
• Your industry (B2B SaaS, non-profits with complex workflows, e-commerce) benefits from custom architecture

Phased redesign (incremental refresh) makes sense if:

• You want to test design changes with real users before rolling out site-wide
• Your budget is tight and you can spend £400–600 per month for 3–4 months instead of £2,000 upfront
• Your site's traffic is sensitive to downtime and you can't risk a big launch day
• You have the discipline to stick to a 3–6 month plan (easier said than done)

---

If you're a small service business (consultant, freelancer, therapist) with a stable WordPress site that just looks outdated, a redesign keeps you moving fast. If you're a SaaS, non-profit, or B2B firm with more than 10 pages and complex workflows, or if your old platform is actively getting in your way, a bespoke rebuild with clear ownership often costs less to maintain over three years.