A rebuild is not a redesign with a bigger invoice.
It solves a different problem.
A redesign says:
The foundation can stay, but the experience needs to change.
A rebuild says:
The foundation itself is now part of the problem.
For 2026 planning:
| Rebuild | Planning budget |
|---|---|
| Small professional website | $3k–$8k |
| Growth-focused business website | $8k–$20k |
| Complex / ecommerce rebuild | $20k–$60k+ |
| Application-like website | Scope as software |
When is a rebuild actually justified?
Common reasons include:
- fragile CMS;
- inaccessible source code;
- security problems;
- repeated performance failures;
- major platform migration;
- difficult deployment;
- ownership problems;
- technical debt that makes small changes expensive;
- new business workflows that do not fit the current architecture.
Age alone is not enough.
A five-year-old website that performs well and remains maintainable may need very little.
A one-year-old site can already need rebuilding if the foundation is wrong.
Start with an audit
Before approving a rebuild, inspect:
- domain/DNS;
- hosting;
- CMS;
- repository/source;
- performance;
- forms;
- analytics;
- Search Console;
- security;
- content;
- rankings;
- backlinks to important pages;
- integrations;
- editability.
The point is to classify assets into:
keep / repair / replace.
A responsible rebuild preserves useful value.
What should be salvaged?
Domain
Usually yes.
Useful URLs
Preserve them where practical.
Search history
Do not discard it casually.
Strong content
Keep or improve it.
Analytics/Search Console
Maintain continuity.
Brand assets
Reuse what still fits.
Customer data
Migrate carefully if required.
Integrations
Retest them rather than assuming they work after the move.
A “fresh start” should not mean throwing away everything the business has already earned.
SEO migration belongs in the budget
Google recommends permanent server-side redirects such as 301 or 308 for pages that permanently move. See Google’s redirect guidance.
A rebuild scope should therefore account for:
- URL inventory;
- redirect map;
- canonical URLs;
- metadata;
- internal-link updates;
- sitemap;
- crawl testing;
- post-launch monitoring.
Use my website migration SEO checklist before changing an established URL structure.
What pushes rebuild cost up?
Content volume
Migrating 12 pages is different from 1,200.
Unique templates
Six reusable page types are easier than 40 bespoke layouts.
Ecommerce
Products, payments, tax, shipping and inventory create more state to preserve.
Integrations
CRM, booking, marketing and payment systems all need to survive the transition.
Custom functionality
Calculators, accounts, dashboards and portals can turn the rebuild into a software project.
Content rewriting
Sometimes the old information architecture is part of the problem.
SEO risk
A site with substantial organic visibility deserves a more careful launch plan.
What should $3k–$8k buy?
This band can be sensible for a smaller business website where:
- scope is controlled;
- content volume is manageable;
- custom functionality is limited;
- design requirements are moderate;
- migration is straightforward.
I would still expect:
- responsive implementation;
- working forms;
- analytics;
- technical SEO basics;
- launch QA;
- clean ownership/handover.
What changes above $8k?
The project may include:
- deeper UX work;
- custom design system;
- content restructuring;
- copywriting;
- more flexible CMS;
- many templates;
- CRM/booking integrations;
- complex migration;
- more extensive SEO preservation.
At that point, the job is rebuilding a digital business asset, not reproducing old pages.
Rebuild versus repeated repair
Repeated repair becomes expensive when every fix exposes another structural problem.
Imagine paying separately for:
- mobile repair;
- form repair;
- plugin repair;
- security cleanup;
- performance repair;
while the same weak platform remains underneath.
At some point, one deliberate rebuild can be cheaper than another year of patches.
But that threshold should come from evidence.
Use repair vs redesign vs rebuild before deciding.
What should a rebuild quote include?
At minimum:
- discovery/audit;
- content responsibility;
- design;
- CMS/platform;
- development;
- migration;
- integrations;
- forms;
- analytics;
- SEO migration;
- responsive/browser testing;
- deployment;
- ownership;
- training;
- support period.
Also ask what is explicitly excluded.
Do not rebuild into the same dependency
After launch, the business should control:
- domain;
- hosting/cloud;
- repository/source;
- analytics;
- Search Console;
- CMS;
- critical third-party accounts.
Use my website handover checklist before final payment.
The rebuild should leave the business easier to operate, not more dependent on one person.
If your website keeps consuming repair money and you are unsure whether the next fix is sensible, send me the current URL and the problems that keep recurring. I can help separate what should be kept, repaired, migrated and rebuilt.
