Website Redesign Cost in 2026: Pricing and Scope

Ask three providers to quote a website redesign and you will often get three numbers that are nowhere near each other. That is usually not a difference in margin. It is a difference in what each of them thinks a redesign is.

One quote covers new visuals on the existing structure. Another includes sitemap work, messaging, SEO migration, and analytics. Both are honest. They are describing different projects.

This article explains what sits inside a redesign, which factors move the price, and what to clarify before asking for a quote.

What "redesign" can mean

Two quite different projects share the name.

A cosmetic refresh keeps the existing structure, pages, and content. New visual design, updated typography and imagery, tidier components. Faster and cheaper, and it makes sense when the site works but looks dated.

A structural redesign revisits what the site is for. Pages change, the navigation changes, the messaging changes, URLs may change, and the technical setup may be rebuilt. It costs more because it is a different project.

What a proper redesign includes

Not every project needs every item, but a quote should state which are in and which are out.

Strategy. What the site is for, who it serves, and which actions matter. Without this the project becomes a matter of taste, and taste has no stopping point.

Sitemap. Which pages exist, how they relate, and what each is for. Structural decisions constrain everything downstream.

UX. How people move through the site — journeys, page structure, what leads to what.

Messaging. What the site says about the business and in what order. Frequently the highest-impact part of a redesign and the most often skipped.

Copy support. Whether the provider writes copy, edits yours, or expects it delivered. This is the single most common cause of stalled projects — get it explicit.

Design. Visual design across templates and states, not just a homepage mockup.

Development. Building it, including components, CMS integration, and edge cases.

Responsive work. Making it work across screen sizes. This is real effort, not a checkbox.

SEO migration. Preserving what already ranks: URL mapping, redirects, metadata, structured data, internal linking. Skipping this is how redesigns lose traffic.

Analytics. Tracking that records the actions tied to the site's goal, configured and verified.

QA. Testing across browsers, devices, and forms before launch.

Redirects. Every changed URL mapped from old to new. Tedious, unglamorous, and the difference between keeping and losing search visibility.

CMS. How your team edits content afterwards, and how much they can safely change.

Integrations. CRM, booking, payments, marketing tools.

Post-launch review. Checking behaviour after real traffic arrives, then one focused round of refinement.

What moves the price

Factor	Lower cost	Higher cost
Number of pages	Few pages, repeating templates	Many unique layouts
Design complexity	Clean, system-driven	Bespoke layouts per page
Content	Supplied and final	Needs writing, editing, or migration
CMS	Straightforward setup	Custom fields, complex editing model
Animation	Minimal	Considered motion throughout
Integrations	None or simple	CRM, booking, payments, custom APIs
SEO requirements	Small site, few rankings at risk	Large site with established rankings
Existing technical problems	Clean codebase	Legacy issues to unpick first
Migration	Same platform	Platform change, content migration
Timeline	Reasonable	Compressed, requiring parallel work
Team size	One or two specialists	Strategy, design, build, SEO, QA

Two are underestimated most often. Content stalls more redesigns than any technical factor — design cannot finish while copy is undecided. And existing technical problems: a site with years of accumulated fixes takes longer to work with than a clean one.

Who does the work

Option	Typically suits	Trade-offs
Freelancer	Smaller sites, defined scope, one main discipline needed	Limited capacity across strategy, design, build, and SEO; single point of failure
Small studio	Sites needing several disciplines and a coordinated process	Less capacity than a large agency; usually more direct contact
Large agency	Large or complex sites, multiple stakeholders, ongoing programmes	Higher cost, more process, often less senior time on your project
Template-based redesign	Tight budgets, standard requirements, speed	Constrained by the template; customisation can cost more than starting properly
Custom redesign	Specific requirements, differentiated positioning	Higher cost and longer timeline

Template-based work deserves a fair hearing. For a small business with straightforward needs, a well-chosen template implemented properly is a reasonable outcome. The trap is buying a template and then paying to fight it into a shape it was not built for.

Typical project phases

1. Discovery. Goals, audience, current performance, constraints.
2. Structure. Sitemap, page purposes, URL planning.
3. Content. Messaging and copy, in parallel with design.
4. Design. Templates and components, reviewed against the structure.
5. Build. Development, CMS, integrations, responsive work.
6. SEO and analytics. Redirect mapping, metadata, tracking setup.
7. QA. Cross-browser, device, form, and accessibility checks.
8. Launch. Deployment, redirects live, monitoring.
9. Post-launch review. Behaviour checked against expectations, one refinement round.

Phases 2 and 3 are where projects are won or lost. They are also the phases clients are most tempted to compress, because nothing visible is produced.

What affects timeline

• Content readiness — the largest variable by a distance
• Approval process — how many people review, and how quickly
• Scope changes mid-project
• Integration complexity and third-party dependencies
• Migration volume — how much existing content moves
• Availability on both sides

A realistic timeline assumes your team's review time, not just the provider's build time. Projects usually slip on the client side.

Questions to ask before requesting a quote

Answer these internally first — they determine the price more than the provider does.

1. Is this a cosmetic refresh or a structural redesign?
2. What is the site's primary job — enquiries, bookings, demos, sales?
3. Who writes the copy?
4. How many pages, and how many need unique layouts?
5. Does the platform change, or stay?
6. What currently ranks, and what traffic is at risk?
7. Which integrations are required?
8. Who edits the site afterwards, and what must they be able to change?
9. What is the actual deadline, and what is driving it?
10. Who approves, and how many rounds are realistic?

Then ask providers:

• What is included and explicitly excluded?
• Is SEO migration and redirect mapping in scope?
• Is analytics configuration included?
• How many revision rounds?
• What happens after launch?
• Who owns the design files, code, and accounts?

Judging value rather than price

A redesign is worth paying for when the current site is measurably getting in the way — visitors cannot find what they need, the structure does not match how you sell, it performs badly on mobile, or your team cannot update it without help.

It is worth less when the site works and the motivation is that it looks dated to people who work there every day. That is a real feeling, and it is not always a business case.

Before commissioning, look at what the current site actually does: which pages get traffic, where people leave, which pages produce enquiries. A redesign informed by that evidence is a different project from one informed by opinion.

Website & Landing Page Design & DevelopmentWe plan the structure around what the site is for before designing anything, and handle SEO migration as part of the project.→

Related reading: How Much Does a Business Website Cost in 2026? and Web Design Agency vs Freelancer.

Frequently asked questions

How long does a redesign take?

It depends on scope and, more than anything, on content readiness. A small template-based refresh can be weeks; a structural redesign with new messaging and migration runs considerably longer. Ask any provider what assumption they made about content delivery.

Will a redesign hurt our search rankings?

It can, if URLs change without redirects, page structure loses the content that ranked, or metadata is not carried over. Handled properly — with URL mapping, redirects, and preserved content — the risk is manageable. Ask specifically how migration will be handled.

Should we change platforms at the same time?

Only if there is a real reason. A platform change adds migration work, retraining, and risk. If the current platform is genuinely limiting you, do it. If the frustration is really about the design, changing platform will not fix it.

Can we redesign in stages?

Yes, and it can reduce risk. A common approach is to fix the highest-traffic templates first, then work outward. It requires the old and new designs to coexist for a period, which needs planning.

What should we prepare before approaching a provider?

Your goals, current analytics, a rough sitemap, a view on who writes the copy, and your real deadline. Providers can quote far more accurately with those, and you will get comparable quotes instead of three different projects.

---

If you are weighing a redesign and want an honest read on whether it is worth it, request a website review. We will look at what your current site does well and what is genuinely holding it back.