Comparison · Redesign vs. Rebuild
One of these changes how your site looks. The other changes what it is.
A redesign restyles the site you have. A rebuild replaces what it runs on and carries your content across. Both are legitimate, both get quoted with the same word, and picking the wrong one is how businesses end up paying for the same website twice inside three years. This page lays out what each one actually changes, what each costs on a five-year horizon, and the specific situations where a surface redesign is the right call and a rebuild would be a waste of your money.
Redesign vs. rebuild, side by side
Both columns are written to be accurate rather than persuasive. Where a redesign wins a dimension outright, the table says so. The comparison assumes the most common real-world case: an existing small business site on a template-and-add-on platform, three to six years old, four to ten pages, with some 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
Everything above collapses into a single question: is the thing you dislike about your website on the surface, or underneath it? If the site is fast, current, structurally sound, and simply looks like it was built in 2019, that is a surface problem and a redesign fixes it for a fraction of the money. If it is slow, add-on heavy, awkward to change, or quietly costing you leads, the look is a symptom. Restyling it buys you a better-looking version of the same problem, and you will be having this conversation again in 18 months.
Six questions that settle this before anyone quotes you
Most people arrive at this decision with a feeling ("the site looks old") rather than a diagnosis. The feeling is usually right that something is wrong and usually wrong about what it is. These six questions turn the feeling into a decision, and every one of them can be answered for free in about twenty minutes before you talk to anybody.
- How fast does it load on a phone right now? Run your home page and your busiest service page through Google's free PageSpeed Insights on the mobile setting. Under a second is healthy. Two to four seconds is the normal range for a template-and-add-on build and is costing you leads on any search done outside on a weak signal. Above four seconds, the design is not your problem. No redesign changes that number, because the weight comes from the page-building tool loading its own code on 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 worth keeping. Fifteen installed with six updates pending is a maintenance bill you have been deferring, and each one is a separate bet that its developer patches quickly when a flaw turns up. A redesign does not reduce that count. It usually adds to it, because premium themes routinely ship bundled add-ons of their own.
- What does the site actually earn? Open Google Search Console and look at clicks over the last twelve months and which pages bring them. This number does not decide redesign versus rebuild. It decides how carefully the move has to be handled. A site pulling 4,000 clicks a month needs a mapped address plan and a careful launch. A site pulling 40 needs an honest conversation about whether the structure was ever set up to rank.
- Who has to be able to edit it, and how often? Be specific: who, what, how many times a month. If the answer is that three people post weekly and none of them can touch code, the admin area you already have is doing real work and losing it has a real cost. If the answer is that you log in twice a year to change the hours, you have been paying platform overhead for a workflow that a monthly block of edit hours covers.
- Do you own the foundation you are about to spend money on? If the site lives on a hosted platform, the redesign buys a nicer interior in a rented building. That can still be the right call. It should be a decision you make on purpose rather than one you discover later, when moving means a rebuild anyway and the redesign money is gone.
- Where does this money sit in three years? If you expect to replace the foundation eventually, a redesign on top of it is a payment you make twice. If you expect the current platform to serve you for another five years, the redesign is the cheaper and correct answer and a rebuild is a solution looking for a problem. Answer this one honestly. It is the only question on the list that a salesperson has a stake in.
When a redesign is the right call and a rebuild is a waste
These are the situations where I would tell you to spend less money with someone else. They are not rare, and mistaking them for rebuild candidates is how businesses end up spending five figures to solve 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 genuinely 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, and it is more common than the rebuild industry admits. A site built three years ago by someone competent, running a handful of current add-ons, loading in about a second, with a structure that makes sense, does not need its code replaced. It needs better typography, better spacing, better photography, and a hero section that says what the business does. That is design work, and design work is what a redesign buys. Spending $3,000 or more to rebuild code that is already doing its job is spending money on the layer that was not broken.
You have a hard date and three weeks
A trade show, a funding announcement, a franchise deadline, a seasonal peak that starts in a month. A surface redesign lands in one to three weeks because there is no migration to plan, no address map to build, and no launch-day cutover to rehearse. A rebuild of a 4–8 page site runs three to five weeks and longer if the content is not ready. When the date is real and immovable, the fast option is the correct option, and the rebuild conversation keeps until the pressure is off. What is worth avoiding is letting an artificial deadline decide a five-year question. "We want it live by the first" is a date. "Our biggest revenue month starts October 1" is a constraint.
The budget is genuinely capped below the rebuild floor
Cash flow is a real constraint, not a failure of ambition. If $3,000 is not available this quarter and $2,000 is, then the choice is between a redesign now and nothing now. A redesign that makes the site presentable while the business grows into a rebuild is a reasonable sequence, provided it is a sequence you chose rather than a story you tell yourself afterward. The trap to avoid is spending $4,000 on a redesign of a foundation you already know is failing, because that is most of a rebuild spent on the wrong layer.
An editing workflow with several people is working today
If three people publish content weekly, each with their own login, and the admin area is a working part of how the business runs, that capability has real value and losing it has a real cost. A hand-coded site has no admin panel. Content changes go through the developer, and the $100 and $180 hosting tiers include monthly edit hours precisely because most small businesses update a few times a year. That arrangement covers a service business comfortably and does not cover a publishing operation. If your site is genuinely a publishing operation, keep the platform, redesign the surface, and put the savings into content.
The site is a bridge to something already changing
A rebrand in progress, a merger in discussion, a product line about to be cut, a business model still being tested. When the thing the website describes is going to change inside 18 months, building a durable five-to-ten-year asset on top of a description that is about to be wrong is premature. Make it presentable, keep the money, and rebuild once the business has settled into the shape it is actually going to hold.
Where a rebuild outperforms a redesign
These are the cases where the visible problem and the actual problem are on different layers. Every one of them is a situation where the redesign money gets spent, the site looks better for a while, and the original complaint is still there twelve months later.
Speed is a structural property, not a styling choice
A page built with a drag-and-drop tool pulls in that tool's own code on every single visit, whether the page uses any of it or not. Add a form add-on, a slider, a popup tool, an analytics wrapper, and a caching add-on trying to undo the damage the others caused, and the page is heavy before your content exists. A new theme sits on top of all of that. It changes the colors, the fonts, and the spacing, and it changes nothing about how long the page takes to appear. A hand-coded page carries only what the page needs, which is why a rebuild lands under a second without a tuning project attached to it. If speed is the complaint, only two things move the number: stripping the existing site down, or replacing what is underneath.
The structure is what is holding the rankings back
A lot of sites that "need a redesign" are actually sites that were never structured to be found. One combined services page competing for eight different searches. Addresses that read like database entries. No page for the question customers actually type. Headings that describe the layout instead of the topic. Those are architecture problems, and architecture is exactly what a surface redesign leaves alone: it restyles the same pages, at the same addresses, saying the same things in a nicer font. A rebuild is the moment the architecture is on the table anyway, which makes it the cheapest time in the site's life to fix it. Doing that work as a separate project on the existing site is possible and runs $800–$1,500, but if a rebuild is coming regardless, it belongs inside the rebuild.
Maintenance debt does not get redesigned away
Every add-on on the site is a standing relationship: a bet that its developer patches quickly when a flaw is published, that the patch works with everything else installed, and that someone notices the update before an automated attack does. Twenty add-ons is twenty bets. A redesign does not reduce the count and frequently raises it, because premium themes bundle their own. A hand-coded rebuild removes the category. Nothing to patch, nothing to renew, no compatibility chart to keep in sync, and the only recurring upkeep item is server software that gets a major refresh roughly 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 close to free when they are part of how the markup gets written. They are slow and expensive when they are corrections layered onto a template's own markup, because a page-builder generates its structure and you are working against it rather than with it. If accessibility is on your list at all, whether for a compliance requirement, a public-sector contract, or the straightforward reason that some of your customers use screen readers, a rebuild is the point where it costs almost nothing and a retrofit is the point where it costs the most.
The three-year math on paying twice
Here is the arithmetic almost nobody runs. Take a $3,000 redesign on a template-and-add-on foundation, carrying $500 to $1,000 a year in platform overhead: hosting, theme renewal, add-on licenses, maintenance time. If that foundation gets replaced in year three, which is the realistic outcome when the foundation was the problem to begin with, the five-year total is the $3,000 redesign, plus $1,500 to $3,000 of overhead, plus a $3,000–$7,500 rebuild, plus two years of hosting at $60 a month. That lands somewhere around $9,000 to $15,000. Rebuilding now costs $3,000–$7,500 plus $720 a year in flat hosting, which is $6,600 to $11,100 over the same five years, for a site that was fast the whole time instead of only after year three. The redesign path is genuinely 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
If the current site lives on a hosted platform, the redesign improves what you are renting without changing that you are renting it. The subscription continues, the export still produces something that only runs on that platform, and the day you decide to leave is still a rebuild. There are businesses for which renting is the right trade, and this is not an argument that platforms are bad. It is an argument for knowing which one you bought. A hand-coded site runs on any standard web server, transfers to you on final payment, and can be handed to any competent developer without an onboarding period. If the business is ever sold, that is a saleable asset rather than 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 of them are worth taking at face value rather than arguing past, because the wrong answer here costs real money in both directions.
"A redesign is cheaper"
On day one, yes, and by a meaningful margin: $1,500 to $5,000 against $3,000–$7,500. That gap is real and if cash flow is the binding constraint this quarter, it decides the question by itself. What the day-one number leaves out is the annual overhead that continues unchanged after the redesign and the probability that the foundation gets replaced anyway. Run the five-year total with an honest guess at when the rebuild happens. If the answer is never, buy the redesign with confidence. If the answer is year three, you already know which number is smaller.
"I'll lose my rankings if I rebuild"
This fear keeps more businesses on bad foundations than budget does, and it is based on real horror stories with a specific and avoidable cause. Sites lose traffic in a migration when nobody mapped the old addresses, when content got trimmed for a cleaner look, or when the site went live with search engines still blocked from the staging setup. Handled properly, rankings hold and commonly improve inside 60 to 90 days because the new site is faster. Worth knowing too: a careless redesign carries the same risk. A template swap that rewrites every heading, changes internal links, and drops three pages nobody thought were important does exactly the same damage, without anyone calling it a migration.
"I just paid for this site two years ago"
That money bought two years of a working website, plus content, photography, structure decisions, and whatever search position the site earned. All of it carries forward. What does not carry forward is the platform choice, which was made with the information available at the time. The previous invoice is spent either way and it should not get a vote in what happens next. The only question that matters is which option leaves you better off three years from now for the money you are about to spend.
"I don't want to lose my admin panel"
This is the most legitimate objection on the list and it deserves a specific answer rather than a dismissal. The question is not whether you could edit the site yourself. It is whether you do, and how often. Most small business owners who believe they will update regularly open the admin twice a year to change the hours. If that is you, you are paying platform overhead for a capability that a monthly block of edit hours covers. If instead you can name the workflow, who edits what, how often, on what schedule, and it adds up to more than a few changes a month, the admin panel is doing real work and that is a genuine reason to keep the platform.
"The site works, it just looks tired"
Then a redesign is very likely the right answer, and I will say so on the call. "Works" is worth defining before you accept it, though. A site that loads in three seconds on a phone is not working; it is failing quietly, and the failure shows up as leads that never arrive rather than as an error message. Check the speed number and the add-on count first. If both come back healthy and the only complaint is aesthetic, buy the design work. That is a genuinely good outcome and a much smaller invoice.
The bottom line
The verdict
If your site is fast, current, structurally sound, and edited regularly by people who need the admin panel, then what you have is a design problem and a redesign solves it for a fraction of the money. Buy that, keep the savings, and do not let anyone talk you into replacing code that is doing its job. If the site is slow on a phone, carrying add-on debt, awkward to change, or built on a platform you would rather not be renting, the look is a symptom and restyling it is money spent on the wrong layer.
The deciding factor is not budget and it is not how the site looks. It is whether the problem you can see sits on the surface or underneath it. Run the speed check, count the add-ons, and pull the twelve-month traffic number before anyone quotes you anything. Twenty minutes of evidence turns this from a matter of opinion into a decision, and the evidence is free.
Pricing
A hand-coded rebuild that carries your existing content across runs $3,000–$7,500 as a one-time, fixed-scope cost. The lower end covers a focused replacement where the content and address structure are largely preserved. The higher end reflects structural re-architecture, added functionality, significant content restructuring, or a larger page set with more migration work attached. A from-scratch multi-page build with new content architecture runs $2,800–$5,000, and a single-page site starts at $1,200. Multi-page builds include full technical SEO setup at no extra cost: the headlines and summaries Google shows in search results, the behind-the-scenes labels that tell it what your business is, the signals that prevent duplicate-page confusion, a site map, and registration with Google Search Console.
Optional managed hosting starts at $60/month for Core: uptime monitoring, nightly backups with 30-day retention, SSL, DNS, and server-level security patching, with no content-edit hours included. Care, at $100/month, adds application-level security patching and one hour of content edits a month. Priority, at $180/month, adds three hours of edits, same-day response on critical issues, a test environment, and monthly analytics reports. There is no add-on license or theme renewal inside any tier, because there are no add-ons and no theme.
Two smaller options are worth naming, because for some sites they are the correct answer and they cost a fraction of either a redesign or a rebuild. If the only real problem is speed, a performance pass on your existing site runs $600–$2,000. If the only real problem is that the site does not get found, technical SEO work on an existing site runs $800–$1,500. Neither requires touching the design, and if one of those solves your actual complaint, I will tell you so rather than quote you a rebuild.
One thing I do not offer: theme customization or page-builder restyling inside your existing platform. That is a real service and plenty of people do it well, but it is not what ArdinGate builds. If a surface redesign is what your situation calls for, someone who works inside your current platform every day is a better fit than I am, and saying that 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: the same site software, the same add-ons, the same page-building tool, the same underlying code. What changes is the visual design, the layout, sometimes the way pages are organized, and often the copy. In a rebuild, the code underneath gets replaced. Your content moves across, your web addresses are preserved, and the site comes back on a new foundation with the old platform gone. The words get used loosely in the industry, which is where most confusion about quotes comes from. Two shops can both say "redesign" and mean completely different amounts of work. Before you compare any two quotes, ask this exact question: is the site still running on the same platform when you're done? If yes, that's a redesign. If no, that's a rebuild, and it should cost more and take longer because it is more work.
How much does a redesign cost compared to a rebuild?
A surface redesign on an existing platform commonly runs $1,500 to $5,000 from a designer or small shop, and $500 to $1,500 if it is really a premium theme purchase plus configuration. A hand-coded rebuild that carries your existing content across runs $3,000–$7,500 at ArdinGate. A from-scratch multi-page build with new content architecture runs $2,800–$5,000, and a single-page site starts at $1,200. The rebuild number is higher on day one and that difference is real, not a rounding error. What the day-one comparison leaves out is that a redesign does not reduce what the old foundation costs you every year afterward, and if the foundation is the reason you are unhappy with the site, the redesign does not fix it either. The five-year number is the one worth running, not the deposit.
Will a rebuild hurt my Google rankings?
Not if the move is planned properly, and this is the fear that keeps the most people on a bad foundation for years longer than they should be. The rules are boring and they work: keep every web address that has traffic or rankings exactly as it is; where an address has to change, point the old one at the new one so both visitors and Google get carried across automatically; keep the substantive content on each page rather than quietly trimming it; and hand Google a fresh map of the site within a day or two of launch. Done that way, rankings hold through the move and frequently improve inside 60 to 90 days because the new site is faster and Google factors speed into rankings. The horror stories come from three specific mistakes: nobody mapped the old addresses, content got deleted in the name of a cleaner design, or the site launched with the search engines still blocked from the staging setup. All three are process failures, not consequences of rebuilding. Worth knowing: a redesign done carelessly can cause exactly the same damage, because a template swap can change every heading and internal link on the site.
My site is on WordPress and just looks dated. Do I need a full rebuild?
Not necessarily, and I would rather say that plainly than sell you something you do not need. If the site loads in about a second on a phone, the add-on count is low, nothing is out of date, the structure makes sense, and you or someone on your team edits it regularly without pain, then the only problem is that it looks like 2019. That is a design problem, and a design problem is solved by a redesign. Swapping to a well-built theme, cleaning up the typography and spacing, and reworking the hero and service pages will get you most of what you want for a fraction of a rebuild. Where that stops being true is when the look is a symptom rather than the disease: pages taking three or four seconds on a phone, a dozen or more add-ons you are afraid to update, a page-building tool nobody wants to open, or a structure that fights every change you ask for. Restyling that gives you a better-looking version of the same problem.
Can I keep my existing content in a rebuild?
Yes, all of it, and on most projects that is exactly what happens. Your copy, images, downloadable files, testimonials, and page structure are all portable. A rebuild that reuses your existing content is the most common shape of this work, which is why it is priced as its own service at $3,000–$7,500 rather than as a from-scratch build. Rewriting copy is an option you can take or leave, not a requirement of moving platforms. Some clients use the rebuild as the moment to sharpen service descriptions and fill in missing pages. Others move the words across verbatim and put the entire budget into speed, structure, and search. Both work. The one thing worth doing regardless is deciding which it will be before the project starts, because "we will figure out the copy as we go" is the single most reliable way to turn a five-week project into a four-month one.
How long does each one take?
A surface redesign on an existing platform generally runs one to three weeks: a theme or template change, a styling pass, image work, and a round of revisions. There is no migration to plan because nothing is moving. A hand-coded rebuild of a four-to-eight page business site runs three to five weeks from kickoff to launch. Larger sites, real structural changes, or new functionality on top push that to six to ten weeks. In both cases the variable that blows up timelines is not code, it is content: copy that still needs writing, photography that still needs shooting, or a review cycle with four people who each want a turn. Neither option requires downtime. The new version is built and tested alongside the live site and swapped in at launch, so your current site keeps working the entire time.
I paid for this site two years ago. Does rebuilding mean that money was wasted?
No, and this is worth separating carefully, because sunk cost keeps more businesses on a failing site than budget ever does. The money you spent two years ago bought you two years of a working website, plus the content, the photography, the structure decisions, and whatever search rankings the site earned in that time. All of that carries forward into a rebuild. What does not carry forward is the platform, which was a decision that made sense with the information available at the time. The question in front of you is not whether the last invoice was justified. It is which option gives you a better site three years from now for the money you are about to spend. The previous spend is gone either way, and it should not get a vote.
Can you redesign my site without rebuilding it?
Not usually, and I would rather tell you that up front than take the project and do it badly. ArdinGate builds hand-coded PHP sites. I do not do theme customization work inside WordPress, page-builder restyling, or template edits on hosted platforms like Squarespace and Wix. That is a real service, plenty of people do it well, and if a surface redesign is what your situation calls for, the honest answer is that someone who lives inside your current platform every day is a better fit than I am. What I do build is the rebuild: your content on a hand-coded foundation, with the migration planned so the rankings survive. There is also a middle option people forget about. If the site's real problem is speed, that is a $600–$2,000 piece of work on your existing site. If it is search visibility, that is $800–$1,500. Neither one requires touching the design at all.
What if my site does not look bad, it is just slow?
Then do not buy a redesign, because a redesign will not fix it. Speed problems on a template-and-add-on site come from the structure: the page-building tool loads its own code on every page whether the page uses it or not, and every add-on adds more on top. A new coat of paint over that arrangement changes nothing about how long the page takes to appear. There are two honest paths. The first is a speed pass on the existing site at $600–$2,000: image work, caching, deferring what does not need to load first, cutting add-ons that are not earning their weight. That reliably takes a four-second page to somewhere near two, and on a site that is otherwise fine it is money well spent. The second is a rebuild at $3,000–$7,500, which starts from a page that has nothing to strip out and lands under a second without any tuning. Which one is right depends on how bad the current number is and whether you like the site otherwise.
How do I tell which one I need before I spend any money?
Three checks, none of which cost anything. First, run your home page and your busiest service page through Google's free PageSpeed Insights on the mobile setting and write down the numbers. Under a second is healthy, two to four seconds is the normal template-and-add-on range, and above four is a lead-losing problem. Second, open your site's admin area and count the add-ons or extensions installed, and note how many are flagged as needing an update. Zero to five with everything current is a healthy foundation. Fifteen with six updates pending is a foundation with a maintenance bill attached. Third, open Google Search Console and look at how much traffic the site actually gets and which pages earn it, because that number decides how much care the migration needs, not whether it should happen. If the site is fast, current, and structurally sound and you simply dislike how it looks, buy a redesign. If it is slow, add-on heavy, and painful to change, a redesign gives you the same problems in a nicer font.
Not sure whether yours needs paint or a foundation?
Send me the URL. I'll check the mobile speed number, look at what it's built on, and tell you which of the two you actually need — including when the answer is a redesign I don't sell.
Get a straight read