What a Website Redesign Actually Costs (and What You Are Paying to Protect)

A website redesign rebuilds an existing site's design, structure or platform while keeping the business it serves, which is a different starting point from what a new build costs when no site exists yet to redesign. The price depends far more on what you are changing than on who you hire, which is why published ranges for the same three words start in the low thousands and run past $200,000. If you run marketing or growth at a B2B software company and the site you are considering replacing already earns organic traffic, that traffic is the asset a rebuild can quietly destroy. This piece covers the published ranges and what they actually mean, the six drivers that move the number, which of four scopes you are buying, and how to price the organic traffic you are putting at risk before you sign.

The short version

• A visual refresh that leaves every URL in place carries almost no search risk. It should not be quoted at migration prices.
• What the published tiers are actually pricing is scope: how many unique page templates you need, how much functionality is custom, and how much content has to move.
• The number worth calculating is not what the migration work costs. It is what your own organic traffic is worth across the weeks a botched migration would take from you.
• You can compute that exposure yourself from Search Console and GA4 data you already own. Every input is first-party, which is why it is worth holding next to a quote.
• Ask which of the four scopes you are buying before you ask for a price. The scope decides both numbers.

What does a website redesign cost?

There is no single market rate, and the two pricing guides we read in full for this article do not agree with each other. Their tiers overlap at the edges and diverge by roughly three times at the entry level, which tells you more about the question than either table does alone.

Published tier	Range	Source
Basic redesign (50 to 150 hours)	$10,000 to $25,000	Innowise
Mid-range redesign (200 to 600 hours)	$30,000 to $80,000	Innowise
High-end redesign (800 to 2,000+ hours)	$100,000 to $200,000+	Innowise
Basic	$3,000 to $15,000	Tenet
Moderate	$15,000 to $40,000	Tenet
Advanced	$40,000 to $80,000	Tenet
Enterprise	$80,000 to $160,000+	Tenet

Those figures are published by Innowise in its own redesign cost guide and by Tenet in its breakdown of redesign pricing. They are other firms' numbers, not ours, and neither is a quote for your site.

The useful reading is that these are not two estimates of the same thing. Innowise expresses its tiers in hours, which is the honest unit: a basic redesign is 50 to 150 hours of work, and a high-end one is 800 to 2,000 or more. Tenet's tiers are labeled by complexity instead. Both are describing a default scope and then pricing it, so a disagreement between them is a disagreement about what the word redesign assumes, not about hourly rates.

Which is why the first question is never the price.

Why do redesign prices vary this much?

Scope, and scope is six specific things rather than one impression of complexity. Ordered by how much of the spread each one explains:

• Unique page templates: the real unit of a build. A marketing site with six templates and a site with thirty are different projects even at identical page counts, because design and development are both priced per template.
• Custom functionality: calculators, gated content, in-page search, interactive product tours, authenticated areas. Each one is a small product with its own edge cases.
• Integrations: CRM, marketing automation, billing, documentation, support. Every integration is a dependency on someone else's API and someone else's release schedule.
• Content migration volume: how many pages move, and how many need new copy because the new template asks for fields the old one did not have.
• Platform choice: the decision about which CMS you build on sets both the build cost and the ongoing cost of publishing into it.
• Approval structure: revision rounds consume design and development time whether or not the quote names them as a line.

Notice what is absent from that list: how good the agency is. Craft changes the outcome and it changes the rate, but it does not explain an order of magnitude. Scope does.

One driver is different in kind, because it is the only one that can cost you money you already have. Content migration is not just a labor line. It is the point at which your existing search performance is either carried across or dropped. Our guide to what makes a website search-ready covers the foundations a rebuild has to preserve.

Which of the four redesign scopes are you buying?

One of four, and the answer decides the price and the risk at the same time. The four are not marketing tiers. They are defined by what changes in the layer search engines actually read.

Scope	What changes	Migration work it justifies
1. Visual refresh, URLs unchanged	Color, type, imagery, component styling. Every URL, every heading and every page's content stay as they are.	A rendering and Core Web Vitals check before and after launch. Not a migration project.
2. Template rebuild, URLs unchanged	Page templates, layout, navigation placement, internal link positions. Paths stay.	Content parity checks per template, an internal link audit, and a crawl of staging against production.
3. Information architecture change	URL structure, navigation hierarchy, category and cluster organization.	A full redirect map, canonical tag review, a regenerated XML sitemap, and an internal link rebuild.
4. Platform or CMS replatform	Rendering, templates and often URL patterns at once, on a new system.	Everything in rows 2 and 3, plus rendering verification and a staging environment that proves parity before anyone flips DNS.

From my experience working on rebuilds and migrations, the scope mispriced most often is the first one. A visual refresh gets a migration line attached to it because the word redesign appears in the brief, not because anything in the search layer is moving. If no path changes, no template rewrites its content and no navigation is restructured, the honest migration line is a check before launch and a check after it.

Scope 2 carries the opposite risk. Nothing about the URL changes, so it reads as safe, but a template rebuild rewrites the internal link graph and can silently drop content blocks that were carrying a page's coverage of a subject. The risk is parity, not redirects, and it needs a different test. Our guide to how to redesign without losing rankings sets out that benchmarking sequence.

Scopes 3 and 4 are where the migration budget is genuinely earned. Once paths change, the redirect map stops being paperwork and becomes the mechanism that carries ranking signals across. Google's documentation instructs you to map old URLs to new ones from your sitemaps, logs and analytics, to update internal links to the new paths, and to keep the redirects in place for at least a year, and it states that permanent redirects do not cause a loss in PageRank. That is the work a scope 3 or 4 quote is paying for, and a site migration checklist is the right reference when you get there.

When the matrix does not apply: if you are moving to a new domain, you are in a migration that happens to include a redesign, not a redesign. Sequence them. Change the design or change the domain, but never in the same release: ship both and a traffic drop has two candidate causes and no way to separate them.

What are you actually paying to protect?

The organic traffic the current site already earns, and you can put a ceiling on that exposure in about five minutes.

Two page-one results for this query were read in full for this article, and both of them cover SEO migration. Tenet goes further and prices it, listing technical SEO strategy and implementation at $2,500 to $8,000 or more as its own quote line. Innowise warns that a rushed redesign "can erase years of SEO progress overnight." What neither of them does is give you a way to size that downside on your own site. That figure is the one worth computing, because it is the only number in the conversation that is about you.

The exposure calculation: monthly organic sessions, multiplied by the share of those sessions landing on URLs whose path will change, multiplied by the number of months you assume recovery would take.

Input	Where it comes from	The part people get wrong
Monthly organic sessions	GA4, or clicks in Search Console for the last 28 days	Use the whole site, then repeat it for the sections that matter most
Share of sessions on changing paths	Export landing pages with sessions, mark each path as staying or changing, sum the changing ones	Weight by sessions, not by URL count. Ten changed URLs carrying 60% of your organic traffic are not 10% of your exposure
Months to recover	Your own assumption, or your own history if you have migrated before	Run it at one, three and six months rather than picking one. It is the input you know least about

The output is session-months at risk. If you already have a value per organic session, multiply once more and you have a dollar figure you can set beside the migration line in the quote.

What this number is not: a forecast. It assumes every changed path loses all of its traffic for the entire window, which is the worst case and not the expected one. Executed properly, with the redirect map Google's guidance describes, the real loss is a fraction of the ceiling. The ceiling is still the right figure to carry into the conversation, because it is what the migration line is insuring you against.

We supply no benchmark inputs for this calculation on purpose. A traffic-loss percentage handed to you by a vendor was measured on someone else's site, and the whole point of the frame is that all three inputs are yours, first-party, and free.

What should you inventory before anyone quotes you?

Four things, and all four are free to produce. In our implementation work the pre-scope inventory is the step that changes the quote, because it converts a conversation about taste into a conversation about counts.

The URL list: every indexable URL on the site, exported from your CMS or a crawl. This is the denominator for everything else, and it is the document a scope argument should be settled against.

The template inventory: group those URLs by the page template that renders them. A site with 400 URLs and seven templates is a seven-template build. Quotes priced per page rather than per template are pricing the wrong unit.

Organic sessions by template: join your landing-page report to the template groups. This is what tells you whether the blog, the docs or the solution pages are carrying the traffic, and therefore which template's parity matters most.

Current coverage: what Google actually has indexed today, not what the sitemap claims. Search Console's URL Inspection tool reports the indexed version of a page and when it was last crawled. A page that is not indexed before the rebuild is not a migration risk, and it should not be priced as one.

Produce those four and the scope question answers itself. You will know which of the four rows you are in before a vendor tells you.

What does the build timeline cost you?

Whatever your content program would have earned during the freeze, which is a real cost even though it never appears as a line item.

The mechanism is simple. If templates are being replaced, anything published into the old ones has to be migrated a second time, so the choice is to freeze publishing or to pay for the same page twice. Where content is a live acquisition channel, that decision belongs in the budget conversation, not the project plan.

Three ways to handle it, and what each one costs:

• Freeze completely: simplest to manage, and you forfeit the compounding for the length of the build. Tolerable on a short refresh, expensive on a long replatform.
• Publish and re-migrate: keeps the channel running and adds migration labor per page published during the window. Price it per page, because that is how it will be billed.
• Ship the content templates first: release the blog or docs templates as their own phase, then keep publishing into the new system while the rest of the build continues. More coordination, and it removes the tradeoff entirely.

The third option only exists when templates are being replaced independently of the URL structure, which means scopes 2 and 4. On a scope 3 information architecture change it does not help, because the path changes have to land in one release.

What must an itemized redesign quote contain?

Enough separate lines that you can delete one and know exactly what you gave up. A quote with three lines is not a quote, it is a number with a narrative attached.

Lines that should always be present: discovery and architecture. Design, priced per template. Development, priced per template. Content migration, with the page count named. Integrations, listed individually rather than as one word. Training and handover.

Lines that should be present only in scopes 3 and 4: the redirect map as a reviewable deliverable. Internal link rebuild. Canonical and sitemap regeneration. Pre-launch parity QA on a staging environment. Post-launch coverage monitoring, with the window stated in weeks.

Lines that sit outside the headline figure and are still real costs: copywriting for fields the new templates introduce, photography or illustration, accessibility remediation, and hosting or CDN changes. Tenet's guide names a comparable set, including team training on the new CMS and analytics event tracking, as expenses that sit outside the headline figure.

Three questions worth asking on the call, in this order:

1. Which of the four scopes is this, and what happens to the price if we keep the URL structure exactly as it is?
2. Who owns the redirect map, and can we review it as a deliverable before launch rather than after?
3. What does post-launch monitoring cover, for how many weeks, and who pays to fix what it finds?

The first question is the one that moves money. A vendor who cannot price the same project with and without URL changes has not separated the build from the migration, and you cannot tell which one you are funding. The same reasoning applies to the retainer that follows a build, and our breakdown of what SEO retainers cost covers that side of the spend.

When is a redesign the wrong purchase?

When the problem you are trying to solve does not live in the design. Four cases where the money is better spent elsewhere:

• The site converts but does not rank: that is a content and technical problem. Rebuilding the same pages in a nicer template does not add coverage of the subjects you are missing.
• The site ranks but does not convert: test the pages you already have first. A rebuild replaces every variable at once, which means you learn nothing from the result.
• Nobody can name the failing page: if the case for the project is "the site feels dated" and no one can point at a template that is costing money, the inventory above is the cheaper first step.
• The trigger is a new brand guideline: that is scope 1. Buy scope 1.

The cases where a rebuild genuinely is the right purchase are narrower and easier to recognize: the templates cannot express what the business now sells, the platform blocks work you need to do, or performance problems are structural rather than fixable page by page. Those are the projects our web development work is built around.

Carry one rule into every scoping call: name which of the four rows a project sits in before you approve a budget for it. Price, timeline, migration line and risk all fall out of that single answer, and none of them can be argued sensibly before it. This week, export your landing-page report, add a column marked path changes: yes/no, and fill it in. That column is the difference between a quote you can read and a quote you can only accept.