Comparison · Redesign vs. Rebuild
One of these changes how your site looks. The other changes what it is.
Redesigns restyle existing sites; rebuilds replace the platform and carry content across. Both are valid and often quoted under one name, causing businesses to pay twice within three years. Compare changes, five-year costs, and when a surface redesign makes rebuilding wasteful.
Redesign vs. rebuild, side by side
Both columns favor accuracy over persuasion, and where redesign wins a dimension, the table says so. It assumes the common case: a three-to-six-year-old small business site on a template-and-add-on platform, four to ten pages, with search traffic worth protecting.
| Factor | Redesign (same foundation) | Rebuild (hand-coded foundation) |
|---|---|---|
| What changes | Look, layout, often the copy. The platform, add-ons, and underlying code stay exactly as they are | The code underneath. Content moves across, web addresses are preserved, the old platform is gone |
| Upfront cost | Redesign wins. $1,500–$5,000 from a designer or small shop; $500–$1,500 if it is a premium theme plus configuration | $3,000–$7,500 reusing your content; $2,800–$5,000 for a from-scratch multi-page build |
| Time to launch | Redesign wins. One to three weeks; no migration to plan because nothing moves | Three to five weeks for a 4–8 page site; six to ten weeks with structural changes or new functionality |
| Page speed after | Roughly unchanged. A new skin does not remove the page-builder code that loads on every visit | Under a second on a phone by default; there is nothing left in the page to strip out |
| Google's speed checks | Usually still fails on mobile unless a separate tuning project runs alongside | Passes from day one without a caching add-on propping it up |
| Ranking risk | Low if addresses and page content are left alone; real if the new template rewrites headings or drops pages | Low with a mapped address plan; the migration is the part that has to be done properly |
| Address structure | Normally untouched, which is the honest advantage: nothing to forward, nothing to lose | Preserved wherever possible; anything that has to change gets forwarded before launch, not after |
| Upkeep afterward | Identical to before. Same platform updates, same add-on renewals, same compatibility surprises | No add-ons to patch, no theme to renew, no update treadmill; the server software is the only item |
| Security exposure | Unchanged, and a new theme can add to it if it ships its own bundled add-ons | No login page, no add-ons, nothing under the hood for automated attacks to find |
| Editing your own content | Redesign wins. The admin area you already know stays exactly where it is | Edits go through the developer; the $100 and $180 hosting tiers include monthly edit hours |
| Accessibility | Depends entirely on the new theme; fixes are retrofits fought against the template's own markup | Built into the markup from the start, which is dramatically cheaper than remediating it later |
| Ownership | Unchanged. If the site was rented before, it is rented after, with a nicer front end | Plain PHP on any standard host; the files are yours on final payment with no platform to keep paying |
| How long the result lasts | Two to four years on a sound foundation; 18 months on a foundation that was already the problem | Five to ten years. Content ages, the code does not, and nothing forces a rebuild on someone else's schedule |
The one question that decides it
It comes down to one question: is the problem on the surface, or underneath it? A fast, current, structurally sound site that just looks like 2019 has a surface problem, fixed cheaply by a redesign. A slow, add-on-heavy site that's awkward to change and quietly losing leads has a symptom, not a cause: restyling it just buys a better-looking version of the same problem, and you're back here in 18 months.
Six questions that settle this before anyone quotes you
Most people arrive here with a feeling ("the site looks old"), not a diagnosis. The feeling is usually right that something's wrong and usually wrong about what. These six questions turn feeling into decision, and each one is free to answer in about twenty minutes.
- How fast does it load on a phone right now? Run your home page and busiest service page through Google's free PageSpeed Insights, mobile setting. Under a second is healthy; two to four is normal for template-and-add-on builds and costs leads on weak signal; above four, design isn't the problem. No redesign changes that number, since the weight comes from the page-building tool loading its own code every visit.
- How many add-ons are installed, and how many need updating? Open the admin area and count. Zero to five, all current, is a healthy foundation. Fifteen with six updates pending is a deferred maintenance bill, and each add-on is a bet its developer patches quickly. A redesign doesn't reduce that count; premium themes often bundle more.
- What does the site earn? Check Google Search Console for clicks over the last twelve months and which pages bring them. This doesn't decide redesign versus rebuild, it decides how carefully the move must be handled: 4,000 clicks a month needs a mapped address plan; 40 clicks needs an honest conversation about whether the site was ever built to rank.
- Who has to be able to edit it, and how often? Be specific. If three people post weekly and can't touch code, the admin area is doing real work. If you log in twice a year to change the hours, you're paying platform overhead for something a monthly block of edit hours covers.
- Do you own the foundation you're about to spend money on? On a hosted platform, a redesign buys a nicer interior in a rented building — still a valid call, but make it on purpose, not discover it later when moving means a rebuild anyway and the redesign money is gone.
- Where does this money sit in three years? Expecting to replace the foundation eventually makes a redesign a payment made twice. Expecting the current platform to last another five years makes redesign the correct, cheaper answer. Answer honestly — it's the one question a salesperson has a stake in.
When a redesign is the right call and a rebuild is a waste
These are the cases where you should spend less money elsewhere. They aren't rare, and mistaking them for rebuild candidates is how businesses spend five figures solving a typography problem.
A redesign on your existing site
- The foundation is sound and the look is the only complaint.
- A hard date is coming and three weeks is all you have.
- The budget is capped below the rebuild floor.
- An editing workflow with several people is working today.
- The site is a bridge to something that is already changing.
A rebuild on hand-coded code
- The page takes more than two seconds to appear on a phone.
- Add-on and platform upkeep has become a recurring cost.
- The structure fights every change you ask for.
- You want to own the asset instead of renting access to it.
- You expect to keep this site for five years or more.
The foundation is sound and the design is the only problem
This is the clearest case, more common than the rebuild industry admits. A site built three years ago by someone competent, running current add-ons, loading in about a second, with sensible structure, doesn't need its code replaced. It needs better typography, spacing, photography, and a hero that says what the business does — design work, which is what a redesign buys. Spending $3,000+ to rebuild code that already works is money on the layer that wasn't broken.
You have a hard date and three weeks
A trade show, funding announcement, franchise deadline, seasonal peak starting in a month. A surface redesign lands in one to three weeks — no migration, no address map, no launch cutover. A rebuild of a 4–8 page site runs three to five weeks, longer if content isn't ready. When the date is real and immovable, fast is correct, and the rebuild conversation keeps until the pressure's off. Just don't let an artificial deadline decide a five-year question: "live by the first" is a date; "biggest revenue month starts October 1" is a constraint.
The budget is capped below the rebuild floor
Cash flow is a constraint, not a failure of ambition. If $3,000 isn't available this quarter and $2,000 is, it's a redesign now or nothing now. Using a redesign to stay presentable while growing into a rebuild is reasonable, if it's a sequence you chose, not a story after the fact. The trap: spending $4,000 redesigning a foundation you already know is failing — that's most of a rebuild spent on the wrong layer.
An editing workflow with several people is working today
If three people publish weekly with their own logins and the admin area genuinely runs the business, that capability has value worth keeping. A hand-coded site has no admin panel — changes go through the developer, and the $100/$180 hosting tiers include monthly edit hours because most small businesses only update a few times a year. That covers a service business fine, not a publishing operation. If you're the latter, keep the platform, redesign the surface, put the savings into content.
The site is a bridge to something already changing
A rebrand in progress, a merger under discussion, a product line about to be cut, a business model still being tested. When what the site describes will change inside 18 months, building a durable five-to-ten-year asset on a soon-to-be-wrong description is premature. Make it presentable, keep the money, rebuild once the business settles into shape.
Where a rebuild outperforms a redesign
These are cases where the visible problem and the actual problem sit on different layers: redesign money gets spent, the site looks better briefly, and the original complaint is still there twelve months later.
Speed is a structural property, not a styling choice
A drag-and-drop page pulls in that tool's own code on every visit whether the page uses it or not. Add a form add-on, slider, popup, analytics wrapper, and a caching add-on trying to undo the damage, and the page is heavy before your content even exists. A new theme changes colors, fonts, spacing — nothing about load time. A hand-coded page carries only what it needs, which is why a rebuild lands under a second with no tuning project attached. If speed is the complaint, only two things move the number: stripping the existing site down, or replacing what's underneath.
The structure is what is holding the rankings back
Many sites that "need a redesign" were never structured to be found: one combined services page competing for eight searches, addresses that read like database entries, no page for the question customers type, headings describing layout instead of topic. Those are architecture problems, and architecture is exactly what a surface redesign leaves alone — same pages, same addresses, same words in a nicer font. A rebuild puts architecture on the table anyway, making it the cheapest time to fix it. As a standalone project on the existing site it runs $800–$1,500, but if a rebuild's coming regardless, it belongs inside the rebuild.
Maintenance debt does not get redesigned away
Every add-on is a standing bet: that its developer patches quickly, that the patch plays nice with everything else installed, that someone notices the update before an attack does. Twenty add-ons is twenty bets. A redesign doesn't reduce that count and often raises it, since premium themes bundle their own. A hand-coded rebuild removes the category entirely: nothing to patch or renew, no compatibility chart, just server software that gets a major refresh every couple of years.
Accessibility is cheap to build in and expensive to retrofit
Contrast ratios, keyboard navigation, form labels, focus states, and heading order are nearly free when built into the markup from the start. They're slow and expensive as corrections layered onto a template, since a page-builder generates its own structure that you're then fighting. If accessibility matters at all — compliance, a public-sector contract, or simply customers using screen readers — a rebuild is where it costs almost nothing and a retrofit is where it costs the most.
The three-year math on paying twice
The arithmetic almost nobody runs: a $3,000 redesign on a template-and-add-on foundation carries $500–$1,000 a year in overhead (hosting, theme renewal, licenses, maintenance). If that foundation gets replaced in year three, the realistic outcome when it was the problem to begin with, the five-year total is $3,000 + $1,500–$3,000 overhead + a $3,000–$7,500 rebuild + two years at $60/month hosting — roughly $9,000–$15,000. Rebuilding now costs $3,000–$7,500 plus $720/year flat hosting: $6,600–$11,100 over the same five years, fast the whole time instead of only after year three. Redesign is cheaper in exactly one scenario: the rebuild never happens.
A redesign is cheaper than a rebuild. Two redesigns and a rebuild are not.
The short version
Ownership does not change with the paint
A redesign on a hosted platform improves what you're renting without changing the fact you're renting it: the subscription continues, exports only run on that platform, and leaving still means a rebuild. Renting is the right trade for some businesses — this isn't an argument that platforms are bad, just that you should know which one you bought. A hand-coded site runs on any standard server, transfers to you on final payment, and hands off to any developer with no onboarding. If the business is ever sold, that's a saleable asset, not an account someone has to be talked into transferring.
The reasons people pick a redesign anyway, addressed directly
Some of these are good reasons. All deserve a straight answer, since the wrong call here costs money in both directions.
"A redesign is cheaper"
On day one, yes, by a real margin: $1,500–$5,000 against $3,000–$7,500. If cash flow is this quarter's binding constraint, that gap decides it. What it leaves out is the annual overhead that continues after the redesign, and the odds the foundation gets replaced anyway. Run the five-year total with an honest guess at when. Never? Buy the redesign. Year three? You already know which number's smaller.
"I'll lose my rankings if I rebuild"
This fear keeps more businesses on bad foundations than budget does, and it's based on real but avoidable failures: nobody mapped old addresses, content got trimmed for a cleaner look, or the site launched with search engines still blocked from staging. Handled properly, rankings hold and often improve within 60–90 days as the faster site kicks in. Worth knowing: a careless redesign carries the same risk — a template swap that rewrites every heading and drops three pages does identical damage, just without anyone calling it a migration.
"I just paid for this site two years ago"
That payment bought two working years, content, photography, structural decisions, and search position — all carried forward. Only the old platform choice stays behind. The spent invoice shouldn't decide the next move; compare what new spending delivers three years out.
"I don't want to lose my admin panel"
The most legitimate objection here, and it deserves a real answer. The question isn't whether you could edit the site, it's whether you do, and how often. Most owners who believe they'll update regularly actually log in twice a year to change the hours — that's platform overhead for something a monthly block of edit hours covers. If you can name the real workflow, who edits what, how often, and it adds up to more than a few changes a month, the admin panel is earning its keep and that's a genuine reason to stay.
"The site works, it just looks tired"
Then a redesign is likely right; you'll hear that on the call. But define "works" first: a site loading in three seconds on a phone isn't working, it's failing quietly, showing up as leads that never arrive rather than an error message. Check the speed number and add-on count first. Both healthy, only complaint aesthetic? Buy the design work — good outcome, smaller invoice.
The bottom line
The verdict
Fast, current, structurally sound, edited regularly by people who need the admin panel? That's a design problem, and a redesign solves it cheaply. Buy that, keep the savings, and don't let anyone talk you into replacing code that works. Slow on a phone, carrying add-on debt, awkward to change, or built on a platform you'd rather not rent? The look is a symptom, and restyling it spends money on the wrong layer.
The deciding factor isn't budget or looks, it's whether the visible problem sits on the surface or underneath. Run the speed check, count the add-ons, pull the twelve-month traffic number before anyone quotes you anything. Twenty free minutes turns this from opinion into a decision.
Pricing
A hand-coded rebuild carrying your existing content across runs $3,000–$7,500, one-time, fixed-scope. The lower end covers a focused replacement with content and addresses largely preserved; the higher end reflects re-architecture, added functionality, or a larger page set with more migration work. A from-scratch multi-page build runs $2,800–$5,000, a single-page site starts at $1,200. Every build includes full technical SEO at no extra cost: search-result headlines and summaries, the labels that tell Google what your business is, duplicate-page prevention, a site map, and Google Search Console registration.
Optional managed hosting starts at $60/month (Core): uptime monitoring, nightly backups with 30-day retention, SSL, DNS, server-level security patching, no edit hours included. Care ($100/month) adds application-level patching and one hour of edits monthly. Priority ($180/month) adds three hours of edits, same-day critical response, a test environment, and monthly analytics reports. No tier includes add-on licenses or theme renewal, since there are no add-ons or theme.
Two smaller options cost a fraction of either path and are the right answer for some sites. If speed is the only problem, a performance pass runs $600–$2,000. If it's just not getting found, technical SEO on an existing site runs $800–$1,500. Neither touches the design, and if one solves your actual complaint, you'll hear that instead of a rebuild quote.
What's not on offer: theme customization or page-builder restyling inside your existing platform. Plenty of people do that well, but it's not what ArdinGate builds. If a surface redesign fits your situation, someone who lives inside your current platform is the better fit, and saying so costs me nothing.
Common questions
What is the difference between a website redesign and a rebuild?
A redesign changes the surface; a rebuild changes the foundation. In a redesign, the platform stays (same software, add-ons, page-builder, code) and the visual design, layout, and often the copy change. In a rebuild, the code underneath gets replaced: content moves across, addresses are preserved, and the old platform is gone. The term gets used loosely, which is where most quote confusion comes from — two shops can both say "redesign" and mean very different amounts of work. Ask this before comparing quotes: is the site still on the same platform when it's done? Yes is a redesign; no is a rebuild, and it should cost more and take longer because it's more work.
How much does a redesign cost compared to a rebuild?
A surface redesign commonly runs $1,500–$5,000 from a designer or small shop, or $500–$1,500 for a premium theme plus configuration. A hand-coded rebuild carrying your content across runs $3,000–$7,500 at ArdinGate; a from-scratch multi-page build runs $2,800–$5,000; a single-page site starts at $1,200. The rebuild is higher on day one, and that's real — but it leaves out what the old foundation keeps costing you every year, and if the foundation is why you're unhappy, a redesign doesn't fix that. Run the five-year number, not the deposit.
Will a rebuild hurt my Google rankings?
Not if planned properly — this fear keeps more people on bad foundations than it should. The rules are boring and they work: keep every address with traffic or rankings exactly as is; forward any address that has to change so visitors and Google carry across automatically; keep each page's substantive content rather than trimming it; hand Google a fresh site map within a day or two of launch. Done right, rankings hold and often improve within 60–90 days as the faster site kicks in. The horror stories trace to three mistakes: unmapped addresses, content cut for a cleaner look, or launching with search engines still blocked from staging — all process failures, not rebuilding itself. Worth knowing: a careless redesign risks the same damage, since a template swap can rewrite every heading and internal link too.
My site is on WordPress and just looks dated. Do I need a full rebuild?
Not necessarily. If it loads in about a second on a phone, the add-on count is low and current, the structure makes sense, and your team edits it without pain, the only real problem is that it looks like 2019 — a design problem, solved by a redesign. A well-built theme, cleaner typography and spacing, and a reworked hero and service pages get you most of what you want for a fraction of a rebuild. That stops being true when the look is a symptom, not the disease: three-or-four-second load times, a dozen add-ons you're afraid to update, or a structure that fights every change. Restyling that just gives you the same problem, prettier.
Can I keep my existing content in a rebuild?
Yes, all of it — that's the most common shape of this work, priced as its own service at $3,000–$7,500 rather than a from-scratch build. Copy, images, downloads, testimonials, and page structure are all portable. Rewriting copy is optional, not required: some clients use the rebuild to sharpen descriptions and fill gaps, others move the words verbatim and put the budget into speed, structure, and search. Both work. Decide which before the project starts — "we'll figure out the copy as we go" is the surest way to turn a five-week project into a four-month one.
How long does each one take?
A surface redesign generally runs one to three weeks: theme change, styling pass, image work, revisions, no migration since nothing moves. A hand-coded rebuild of a four-to-eight page site runs three to five weeks kickoff to launch; larger sites or new functionality push that to six to ten. In both cases the timeline killer isn't code, it's content: copy still being written, photography still being shot, a four-person review cycle. Neither requires downtime — the new version is built and tested alongside the live site and swapped in at launch.
I paid for this site two years ago. Does rebuilding mean that money was wasted?
No — sunk cost keeps more businesses on a failing site than budget ever does. That money bought two working years, plus the content, photography, structure decisions, and search rankings the site earned, all of which carry forward into a rebuild. Only the platform choice stays behind, and that made sense with the information you had then. The real question isn't whether the last invoice was justified, it's which option gives you a better site three years from now. The previous spend is gone either way; it doesn't get a vote.
Can you redesign my site without rebuilding it?
Not usually. ArdinGate builds hand-coded PHP sites, not theme customization inside WordPress, page-builder restyling, or template edits on Squarespace or Wix. That's a real service, plenty of people do it well, and if a surface redesign fits your situation, someone who lives inside your current platform daily is the better fit. What you get is the rebuild: your content on a hand-coded foundation, migration planned so rankings survive. There's also a middle option: if the problem is speed, that's $600–$2,000 on your existing site; if it's search visibility, that's $800–$1,500. Neither touches the design.
What if my site does not look bad, it is just slow?
Then don't buy a redesign, it won't fix it. Speed problems on a template-and-add-on site come from structure: the page-builder loads its own code on every page regardless of use, and every add-on piles more on top. A new coat of paint changes nothing about load time. Two honest paths: a speed pass on the existing site at $600–$2,000 (image work, caching, deferred loading, cutting dead-weight add-ons), which reliably takes a four-second page to near two and is money well spent on an otherwise fine site; or a rebuild at $3,000–$7,500, which starts with nothing to strip out and lands under a second with no tuning. Which one's right depends on how bad the number is and whether you like the site otherwise.
How do I tell which one I need before I spend any money?
Start with three free checks:
- Test the homepage and busiest service page in Google PageSpeed Insights on mobile and record results. Under a second is healthy; two to four seconds is normal for templates and add-ons; above four loses leads.
- Count installed admin add-ons or extensions and pending updates. Zero to five, all current, suggests health; fifteen with six pending means a maintenance burden.
- Use Google Search Console to measure traffic and identify earning pages. That determines migration care, not whether to migrate.
Buy a redesign if a fast, current, sound site merely looks wrong. For slow, add-on-heavy sites that resist changes, redesign only gives the same problems a nicer font.
Not sure whether yours needs paint or a foundation?
Send the URL. You'll get the mobile speed number, a look at what it's built on, and which of the two you need, including when the answer is a redesign I don't sell.
Get a straight read