Redesign or rebuild usually gets asked as a question about looks. The answer is underneath the looks. A redesign changes the surface. A rebuild changes the machine that makes it. Ugly but easy to edit? Redesign. Gorgeous, but every small change means a developer and a two-week wait? Rebuild, and no font pairing is going to save you.
Below are the five tests we run before quoting anything. About an hour. I share them because a client who knows which project they need never gets sold the wrong one.
Redesign, refresh, rebuild, replatform: what each word means on a quote
They get used interchangeably, including by people selling websites. The blur is convenient if you’re quoting and expensive if you’re buying.
| Word | What actually changes | What stays |
|---|---|---|
| Refresh | Colors, fonts, photos, copy | Structure, platform, URLs, how you edit |
| Redesign | Layouts and visual system, site-wide | Platform, content structure, URLs (usually) |
| Rebuild | Code, templates, how content is stored and edited | Platform, domain, URLs if anyone maps them |
| Replatform | The whole system moves (Wix to WordPress, HubSpot to anything) | Your domain. Your content, if it exports cleanly. |
They fix different problems. You can rebuild a site and keep its design almost exactly. Honestly, one of my favorite projects.
The five-test diagnostic that settles it in an hour
Run them in order. Scoring at the bottom.
Test 1: Can you edit a page without breaking it?
The test: log in, open a real page, change one sentence, save, then check that page on your phone. Did anything move that you didn’t ask to move?
The follow-up that matters more: name three small changes you wanted and skipped. New hours, a dropped service, a photo of the truck you sold. Skipped because asking was a whole production? That’s the “every change needs a developer” tax, paid monthly.
Fail means: rebuild territory. Editability gets decided the day a site is built, by whoever builds it. No restyling reaches it later. Designing that tax out is deliberate on every build we do.
Test 2: Does your content live in fields, or in a builder blob?
The test: find something that repeats (staff bios, service pages, locations) and add a new one. Do you fill in labeled boxes and get something that matches the others? Or duplicate an old page and hand-place text until it looks close?
The first is structured content: information stored as data, design applied on top. That’s what Advanced Custom Fields does on WordPress, and it’s why such a site can be redesigned without touching the content.
The second is a builder blob, where words, images and layout are welded into one object. Nothing underneath to re-skin, because the design is the content. Decides more projects than anything else here, and nobody checks it before collecting quotes.
Fail means: rebuild. A “redesign” quoted on blob content is someone rebuilding every page by hand and calling it a redesign.
Test 3: Do you have a design system, or 40 individual opinions?
The test: open five pages in five tabs. Count your button styles, then count your heading sizes.
If the answer is “buttons are three colors and the About page headings are bigger for some reason,” you don’t have a design system. You have decisions made on different Tuesdays. That changes the math: with no system, redesign labor looks a lot like rebuild labor, because someone redraws every page either way.
Fail means: the pricing gap just narrowed. Get both numbers from the same person so you’re comparing scope, not sales pitches. Ours are in the pricing calculator.
Test 4: Is the platform underneath you still supported?
The test: find what your site runs on, then check whether those things are still maintained. Theme still sold and updated? Builder still shipping releases? PHP version your host still supports? Is the company that made your theme still, you know, a company?
A fail here overrides everything else. Software that stops getting updates stops getting security patches, and an unpatched site is a liability on your domain. WordPress core is almost never the abandoned part. It’s usually a theme, builder or plugin nobody has touched in years, which is what ongoing maintenance catches before it becomes a rebuild.
Fail means: rebuild, and stop weighing it. Paint on a condemned structure.
Test 5: Do you have URL and analytics history worth protecting?
The test: open your analytics, set the range to the last 12 months, sort pages by traffic, save the top 30.
This one doesn’t pick a verdict, it sets how careful the project has to be. Eight years of posts pulling steady traffic is an asset, and protecting it takes real hours from someone who has done it before.
Scoring it
- Test 4 failed: rebuild or replatform. An unsupported platform overrides the other four.
- Test 1 or 2 failed: rebuild. The problem is structural, and design work doesn’t reach it.
- Tests 1, 2 and 4 passed, 3 failed: redesign. Good bones, inconsistent surface.
- Everything passed and you still hate it: it’s probably the writing. Still a real project, and we quote it as one.
Can’t I just have AI rebuild it?
New question this year, and a fair one. If you haven’t gone down this road: there are tools that generate a whole website from a description. You type what your business does, pages come back. And it isn’t garbage.
It’s also a starting point, not a finished business asset. A draft of a surface, and all five tests above are about what sits underneath. They don’t decide how your content gets structured so you can still edit it next year, which URLs survive launch, whether a screen reader can use your nav, or why the page takes six seconds to load on a phone.
Tried it already? Then you know the wall. Most of the way there, then something you couldn’t name. Spacing that felt off. Copy that sounded like every other company. A page that broke somewhere else the second you touched it. That wall isn’t a prompting problem, and you aren’t one tutorial away from clearing it. The last stretch is judgment, and judgment is the job.
We use these tools daily. They take the tedious parts from hours to minutes, part of why our Launch build is $2,400 and not five figures. What they don’t replace is the person deciding what’s correct. A nail gun didn’t replace carpenters. Just fewer sore thumbs.
What does each verdict cost?
Our numbers, so you have something real to anchor against.
- Content work only: full-service pages (research, writing, build, on-page SEO) run $275 to $375 each. If the words are the problem, that’s the project, and we scope it as one.
- Full rebuild: our Launch package is $2,400 flat: brand kit, custom design, the build, ten pages populated, on-page SEO, training. With real functionality it climbs: booking from $5,500, stores from $8,500, courses from $12,000. See services.
- Moving somewhere new: migrations run $700 to $1,800 depending on content volume and how ugly the export gets.
- Keeping it healthy after: maintenance starts at $300 a month, no contract. Trimming a budget? Trim elsewhere. Updates, backups and security decide whether the site you just paid for is still standing next year.
One number never shows up on a quote: your hours. A project you run yourself gets paid for in evenings, the most expensive thing a business owner has. If your read is “I know what needs to happen, I just don’t have a Saturday to give it,” that’s the most common reason people call us. Price yours in the pricing calculator, or read what a small business website costs.
Will a rebuild kill my Google rankings?
Not if the URL work gets done. Rebuilds lose rankings when redirects, titles and analytics get treated as launch-day afterthoughts. Rankings attach to URLs, not to the design sitting on them, so you can replace every pixel and keep every position. Redirect mapping is the biggest way a rebuild loses traffic, and the easiest thing to skip when nobody owns it.
The work:
- Export the full URL list before anything changes. Sitemap, crawl and analytics export.
- Decide the fate of each URL: stays, moves (301), or goes (301 to the closest surviving page). Dumping dead URLs on the homepage wastes the signal.
- Keep the titles and meta descriptions on pages that already earn traffic. Rewriting them on launch day for style reasons loses positions for nothing.
- Keep the same analytics property. Starting fresh throws away the baseline right when you need it to prove the rebuild worked.
- Test every redirect after launch, then watch Search Console for 404s. And check nobody left the staging noindex tag on. It happens.
None of it is exotic, just tedious, and tedious is where projects quietly lose money. I did exactly this moving a 177-post blog off HubSpot onto WordPress, checking every URL for parity. It’s the difference between a rebuild Google never notices and a bad quarter.
When is a redesign a waste of money, and when is a rebuild?
Two failure modes, opposite directions.
A redesign that should have been a rebuild. The site failed tests 1, 2 and 4 and got a visual refresh anyway. Six months later nothing about your week has changed, and the sunk cost makes the next conversation harder. Paint on a site you can’t edit.
A rebuild that should have been three pages of writing. Say you run a commercial cleaning company. Site is fast, editable, current, fine on mobile. It also opens with “Welcome to our website” and never mentions you specialize in medical offices or work overnight. The build is fine. The message is broken. Rebuilding gets you a beautiful site saying the same nothing. Fix the words first, at $275 to $375 a page. Smaller invoice, and we’ll happily write those instead.
Common questions
Does using a page builder automatically mean I need a rebuild?
No. Plenty of builder sites pass tests 1 and 2. Trouble starts when the builder is why you can’t change anything, or when content is so fused to layout that a redesign means rebuilding each page by hand. Judge the site, not the logo in the admin bar. Not sure which side you’re on? Send us the URL and we’ll tell you.
How long does a rebuild take compared to a redesign?
The schedule is set by content, not code. Development finishes when pages are ready to fill, and pages are ready when somebody has written and approved them. Want it fast? Hand the writing to us with the build so it’s never what everyone waits on.
Can I keep my domain and my host?
Yes to the domain, assuming it’s registered in your name. If a past developer registered it for you, sort that out first and treat it as a warning about the rest of that relationship. Usually yes to the host too. You should own your domain, code, design and content no matter who builds for you, and a proposal that makes any of that conditional on staying has told you something about the agency.
What to bring so this takes one call
Turn up with these and it’s fifteen minutes:
- A screen recording of you editing one page (worth more than any description)
- Your top 30 pages by traffic, last 12 months
- The last five changes you wanted and skipped
- What you want the site to do that it doesn’t
So, next step. Run the five tests this week and send us what you found. We’ll tell you which project you’re actually looking at, what it costs and what it doesn’t include. Haven’t run them? Send the URL and we’ll run them ourselves. Want a number first? The pricing calculator gets close, and how we handle small business sites is written out in full.
Because the sites that stay good aren’t the ones redesigned most recently. They’re the ones built by somebody who thought that far ahead on purpose.