Website Rebuild Cost: Scope, Tiers and Decisions

How much does a website rebuild cost in 2026?

The table below describes PandaCodeGen's own planning tiers and nothing else. We do not publish a market-wide rebuild range, because any single band has to average brochure sites, commerce platforms, regulated journeys and multi-market systems together. Price your own rebuild by writing the scope first, then asking two or three providers to quote that same scope.

When the rebuild question becomes urgent

Urgency should follow evidence: security exposure, unsupported dependencies, inaccessible journeys, broken editing, recurring incidents, platform sunsets, failed integrations, content constraints or a business change the current system cannot support. A news event or platform critique does not make every site an urgent rebuild.

"A rebuild is not a redesign with new colours. It changes the platform and reworks the structure underneath it.

Rebuild vs redesign vs migration

Two questions tell you which one you need. First, is the platform itself the problem? Second, has the business outgrown what the site says and how it is organized? If only the first is true, that is a migration. If both are true, that is a rebuild. If neither is true and only the look has gone stale, that is a redesign, and it costs a fraction of the other two.

The fastest way to tell which one you need is to ask two separate questions. First: is the platform itself the problem, through speed, security, lock-in or an editing model nobody can use? Second: has the business outgrown what the site says and how it is organized? If only the first is true, that is a migration: move it and keep it recognizable. If both are true, that is a rebuild: new foundation, new structure, new design on top of it. If neither is true and only the look has gone stale, that is a redesign.

Each of those three projects carries its own cost model, so read the one that matches the work you actually need before you compare quotes. We break down the visual-only path in the website redesign cost guide and the platform-move path in the website migration cost guide.

Seven line items that drive rebuild cost

Two rebuild quotes for the same page count can sit a long way apart and both be honest. The distance is almost always in these seven variables. Ask any provider to point at the ones driving their number, and ask what each would look like if it were scoped smaller.

• ✓
  Research, positioning, information architecture and measurement. This is the line a rebuild has and a migration does not: deciding which pages should exist, how they connect and what the site should say now. If a quote jumps from discovery straight to development, your old structure is being reused by default.
• ✓
  Brand application, UX, responsive UI and design-system depth. Reusing an approved design is the cheapest path. A light refresh sits above it. A full design system with type scale, tokens and component states is a separate body of work that happens before development starts.
• ✓
  Copywriting, content migration, media and data cleanup. Migrating existing copy and writing new copy are different jobs, and deciding which pages get merged, split or cut is a third. Missing photography, source files and messy exports all land here.
• ✓
  Frontend, backend, CMS, search, forms and integrations. A hard-coded static build is the smallest scope. A structured CMS adds a content model and editor training. Each CRM, email, analytics, chat or payment integration adds its own build, test and failure-handling work.
• ✓
  Commerce, membership, applications and complex business workflows. Anything with accounts, permissions, transactions or state costs more than a page that only renders content, and it carries more acceptance testing.
• ✓
  Accessibility, security, privacy, SEO, analytics and performance acceptance. Building to a performance and accessibility target from day one is a design constraint on every decision. Retrofitting it after launch is a second project.
• ✓
  Project governance, launch, rollback, handoff, support and maintenance. Number of approvers, review cycles, environments, training and what happens in the first weeks after launch all sit in this line.

Freelancer vs boutique studio vs agency vs enterprise firm

Provider labels do not determine quality or price. A freelancer can fit a focused scope when the buyer owns direction and QA. A boutique can coordinate a small senior team. A larger agency can provide more disciplines and governance. An enterprise firm may fit regulated or multi-stakeholder programs. Compare the assigned team, scope and evidence. The trade-offs hidden behind an unusually low quote are covered in what a cheap web developer actually involves, and the questions to put to a shortlist are in our guide to choosing a web development agency.

Published market rates cluster in fairly predictable places: freelancers are usually quoted somewhere around $25 to $100 per hour, and agencies around $100 to $250 or more. Those numbers are worth knowing and close to useless on their own. You are buying rate multiplied by hours, and the buyer can see the rate but not the hours. A $40 per hour engagement that needs constant direction, redoes work after each review round and has no defined acceptance can cost more in fees and considerably more in your own time than a $150 per hour team that scoped the work properly and finished it. Compare total quoted cost against a written scope. A rate card compared against nothing tells you which provider is cheaper per hour, which is not the question you are trying to answer.

Why published rebuild ranges are higher than our packages

What it costs to leave WordPress, Webflow, Squarespace, Wix or Shopify

The platform changes extraction and replacement work. WordPress may require theme and plugin mapping; Webflow has documented export exclusions; Squarespace's export is partial; Wix features require inventory and feature-specific extraction; Shopify adds commerce continuity. Use the platform-specific inventory, not a generic multiplier.

We keep a separate breakdown for each starting point: WordPress, Webflow, Squarespace, Wix. For stores, Shopify compared with a custom build covers what commerce continuity adds to the scope. Our WordPress migration service page describes how we run the extraction and replacement steps in practice.

Proposal red flags without accusing a quote of padding

A high quote may simply include more work or more risk. Six things in a proposal signal a scope problem rather than a pricing one, and the correct response to all six is the same: call the quotes non-comparable until the statements of work are normalized. Do not claim a provider padded it without evidence.

• ✓
  No route, template, content, feature or integration inventory.
• ✓
  Undefined acceptance, assumptions or exclusions.
• ✓
  A price that excludes essential vendor fees or migration work.
• ✓
  No named team or disclosure of subcontracting.
• ✓
  Guaranteed rankings, revenue, AI citations or permanent performance.
• ✓
  Unclear change-order, ownership, account, handoff or termination terms.

A high quote may include more work or risk. Call it non-comparable until the statements of work are normalized; do not claim the provider padded it without evidence.

Because a rebuild bundles strategy and design work on top of the technical work, the gaps show up in different places than they do on a straight platform move. Four to check line by line:

• ✓
  Unlimited design revisions with no sign-off gate. Unlimited sounds generous, and it removes any reason for the project to converge. Ask instead for a defined number of structured rounds tied to named milestones, with extra rounds priced in advance.
• ✓
  No separate line for information architecture. A rebuild is meant to rethink structure, not just skin it. If no time is budgeted for a new sitemap and navigation model before design starts, you are paying rebuild prices for migration work.
• ✓
  Content strategy folded into copywriting. Deciding whether a page should still exist, be merged or be cut is a different task from writing the words. If there is no strategy line before the copywriting line, new words are being written for the old structure.
• ✓
  Design deliverables described in adjectives. Ask what artifacts you receive: a sitemap, a design system, and signed-off layouts for the key page types before development starts. If none of that is itemized, the deliverable is undefined.

Deposits are a fair question to ask about too. Tie payments to deliverables you can inspect, and be clear on what you have received at the point each one falls due. Our own terms are 30 percent at onboarding and 70 percent on delivery, set out below.

Will I lose SEO when I rebuild?

A rebuild can create migration risk. Google recommends careful site-move planning, relevant redirects, updated internal links and canonicals, sitemaps and monitoring. Keep valuable URLs stable where practical. Search engines still control crawling, indexing, rankings and timing, so no agency can guarantee retention. Our detailed answer on search visibility during a migration sets out the controls worth insisting on in the scope.

How do you calculate rebuild ROI?

Define the one-time and ongoing cost, then identify measurable cash flow, internal time, risk or capability changes attributable to the rebuild. Use low, central and high scenarios and report uncertainty. A faster site or new design does not establish incremental revenue by itself. Our three-year cost comparison of WordPress and custom code shows one way to lay the ongoing side of that calculation out.

How long does a website rebuild take?

Duration depends on requirements, pages, design, content, data, integrations, review, compliance and acceptance. Plan phases with exit evidence rather than a universal week range. Record client dependencies and change impacts in the schedule. In practice the delays that hurt most are on the buyer's side: late content, late feedback, late sign-offs. Name one decision-maker, agree a turnaround commitment for feedback in writing, and gather the content you already know is missing before kickoff. We walk through how those phases stack up in how long a custom website takes to build.

Hidden costs to make explicit

Because a rebuild reimagines the site instead of porting it, most of the surprises cluster around design and content decisions rather than technical plumbing. Ask about each of these explicitly, and get the answer written into the scope rather than agreed on a call.

• ✓
  Content decisions, missing assets, data cleanup and translation. A new sitemap often calls for pages that never existed on the old site, and writing those from scratch is a different job from migrating copy.
• ✓
  Extra design revision rounds, and what triggers them. A stakeholder who was not in the first reviews asking for changes afterwards is a common cause, and it is a scope change rather than a defect.
• ✓
  Information architecture rework after development starts. If testing or internal feedback moves the navigation model mid-build, agree upfront how that gets re-quoted.
• ✓
  Brand asset gaps. A reimagined design frequently needs photography, iconography or logo files in formats and resolutions the business does not currently hold.
• ✓
  Provider plans, licenses, usage and transaction costs, plus internal review, legal, training and change management time.
• ✓
  Post-launch monitoring, incidents, maintenance and framework upgrades, and whether early fixes are included or billed.
• ✓
  Archive, retention, cancellation and old-system decommissioning.

Two of those have a rough number attached that is worth budgeting against. Content work is commonly quoted somewhere in the region of $100 to $300 per page to rewrite or port existing copy, which is why a 30-page site and a 300-page site diverge on content long before they diverge on build. And ongoing maintenance is usually estimated at 15 to 20 percent of the original build cost per year, covering hosting, security patching, dependency updates and small changes.

Run that second one before you sign anything. A $30,000 build carrying 18 percent annual maintenance is roughly $5,400 a year, which is another $16,000 across three years, and it is the line most often left out of the comparison entirely. If you are weighing options over that horizon rather than at the point of purchase, the three-year cost comparison works the same arithmetic through in full.

When a rebuild does not make sense

The most common wrong reason to rebuild is that the platform is the only real problem while the structure still describes the business accurately. That is a migration, and it is cheaper. Seven other conditions argue against buying a rebuild, and two of them are about you rather than the site: unresolved content or positioning will stall any build, and nobody having capacity for feedback and approvals will stall it twice.

• ✓
  The platform fits and a targeted repair addresses the measured problem.
• ✓
  Content, positioning or operations are unresolved and will stall any build.
• ✓
  The business cannot own the target operating model.
• ✓
  Expected value does not justify cost and migration risk.
• ✓
  A redesign or isolated integration change meets the requirement.
• ✓
  You are heading into your busiest trading period. Launch risk is concentrated in the first days after a cutover, and that is the worst week to spend on it.
• ✓
  Nobody internally has the capacity to supply content, feedback and approvals on the project timeline. Rebuilds need more of this than migrations, because structure and design are genuinely being decided rather than carried across.
• ✓
  The platform is the only real problem and the structure still describes the business accurately. That is a migration, and it gets you the same speed and security outcome without paying for design and IA work you do not need.

PandaCodeGen terms

A common payment option is 30 percent at onboarding and 70 percent at the delivery milestone, and another written schedule may be agreed. Refund is tied to failure to deliver the signed scope, not a change of preference after starting. Starter includes 15 business days of launch defect support and Growth and Scale carry 30, where the accepted terms include it. Ownership, licenses, accounts, acceptance and remedies follow the signed project terms. Work that falls outside the standard tiers is scoped through our custom engineering service.

Frequently asked questions

Primary sources

• WCAG 2.2
• OWASP ASVS