Website Redesign Cost: What Changes the Price & How to Budget

Two businesses each ask for a redesign of their 10-page website.

Project A keeps its current CMS, keeps most of its URLs and reuses most of its content. It needs a few reusable page templates and has no complicated integrations.

Project B rewrites most of its content and restructures its navigation. It needs several custom templates and a new CRM connection. Its URLs will change, so existing content has to be migrated, existing search visibility has to be protected and launch testing is heavier.

Both can truthfully be described as “a 10-page website redesign.” They are not the same project, and they shouldn’t be expected to cost the same.

That’s the starting point for understanding website redesign cost. The honest answer to “how much should a website redesign cost?” depends less on page count than on what happens to the existing site: what’s kept, changed, added, moved and tested. Published ranges differ because each source bundles different combinations of that work into “redesign.”

This guide organizes redesign scope into five parts:

Keep → Change → Add → Migrate → Verify

It’s a planning framework for this guide, not an industry standard, and other providers may describe the same work in different terms.

For the same reason, there’s no reliable universal figure. An average website redesign cost blends small visual refreshes with complex rebuilds, so it rarely describes any one project well. NogaTech doesn’t publish a standard redesign price here. Instead, this guide shows you how to read a proposal: what’s inside it, what changes the effort, and how to compare scope before price.

What Does Website Redesign Cost Actually Mean?

Website redesign cost is what it takes to meaningfully improve an existing website. The scope behind that number can range from mostly design and template work to a project that also involves content, development, migration and launch.

Depending on the provider and the project, a redesign may include different combinations of:

• • Planning and discovery
• • Information architecture
• • Content editing or writing
• • UI and UX design
• • Front-end and back-end development
• • CMS changes
• • Integrations with other business tools
• • Content and data migration
• • URL redirects
• • Quality assurance and testing
• • Launch support

One proposal might cover a few of these; another, all of them.

That’s why the most useful principle in this guide is simple: a quote is only meaningful when the responsibilities inside it are clear.

Why Website Redesign Price Ranges Vary So Much

Published pricing guides show how differently “redesign” gets defined. Two current examples:

• • WebFX’s redesign pricing page gives an overall range of $3,000–$75,000. It then breaks that down by site size and by whether the work is done by an agency, a freelancer or in-house.
• • Clique Studios’ redesign cost FAQ says small business websites of 10–20 pages typically cost $15,000–$40,000. It gives higher ranges for mid-market, enterprise and ecommerce projects.

These are each source’s own published figures, shown only to illustrate variation, not as an industry standard or NogaTech pricing. They shouldn’t be averaged: each source groups projects, counts work and frames site size differently, so a blended number would describe nobody’s project.

The two ranges are not directly comparable because each source defines and groups redesign work differently. The gap itself shows that “website redesign” isn’t a standardized package. Until you know what a range assumes, you can’t tell where your project fits.

The Five Parts of Website Redesign Scope

Sorting redesign work into five areas makes scope visible, whether or not a proposal names them:

Keep is where budgets are often won or lost. Identifying what can be reused can remove a lot of unnecessary work. But keeping something only because it’s already paid for can be false economy. If the current navigation confuses customers, preserving it to save money may simply carry the problem into the new design.

Change covers the visible redesign most people imagine. It’s also where scope tends to grow informally, as one adjusted template leads to another.

Add is easy to underestimate because it hides inside the word “redesign.” A new booking flow or CRM connection is new capability, not just new styling.

Migrate and Verify grow with everything else: the more a project changes, adds and moves, the more has to be transferred safely and tested.

Visual Refresh vs Deeper Website Redesign

Redesign scope isn’t a set of fixed packages. It’s a continuum, and most projects sit somewhere along it.

At the lighter end, a primarily visual redesign may keep the platform, URLs, content structure and functionality largely as they are. The work changes how the site looks and presents information: typography, visual hierarchy, components, layouts and responsive presentation.

Further along, a deeper redesign may also change the information architecture, content, navigation, templates, functionality, integrations and URLs. Each of those additions pulls in work from the Add, Migrate and Verify areas, not just Change.

Many projects start light and drift deeper as stakeholders spot problems, which is a common reason estimates and final scope diverge. Deciding early where the project sits makes quotes far easier to compare.

At some point, the scope can move beyond redesign into replacing the site’s foundation. Whether that’s the right path is a separate decision, covered in NogaTech’s guide to website redesign vs. rebuild.

What Actually Changes Website Redesign Cost?

The five scope areas describe what happens to the site. The drivers below are a website redesign cost breakdown by type of work. A project can be light in some and demanding in others.

Strategy and Discovery

Agreeing what the redesign is for: stakeholder requirements, business goals, a current-site assessment, customer needs and technical constraints. A clear brief for a modest refresh may need little discovery. When goals are unclear or several departments have a stake, skipping it tends to push cost into later rework.

Information Architecture

Navigation, page hierarchy, consolidating overlapping pages and mapping customer journeys. Restructuring how a site is organized affects design, content and often URLs, so it ripples into other parts of the budget.

Content

Reusing, editing, rewriting or creating copy, and preparing images. Who does that work matters as much as how much there is.

Unique Templates

A template is a reusable page layout. A site with 50 pages built from 4 templates may involve less design and development than a site with 15 pages that each need a distinct layout or workflow.

UX and Visual Design

Existing design system or new visual direction; reusable components or bespoke interactions; behavior across screen sizes.

Development and CMS

Retaining the CMS, building templates and components, adding custom features or changing platform.

Integrations

CRM, booking, payment, email marketing, forms and other business systems, each with its own dependencies.

Migration

Pages, media, files, data, URLs and redirects.

QA and Launch

Responsive and device testing, form and workflow checks, analytics verification, redirect testing and production checks at launch.

Why Page Count Alone Is a Weak Pricing Measure

Page count does matter. More pages can mean more content to prepare, more to review and more to test.

But it’s a weak measure on its own. Compare two projects:

• • 50 content pages sharing a handful of templates: articles, service pages and location pages that follow consistent layouts.
• • 10 pages with unique interfaces, multi-step forms, integrations and custom workflows.

The first has five times the pages. The second may well involve more design, development and testing, because almost nothing in it can be built once and reused.

That’s why the number of unique page types or templates is usually a better indicator of effort than total URL count. When a proposal is priced “per page,” it’s worth asking what kind of page that rate assumes, and what happens when a page needs its own layout, form or integration. There’s no reliable universal cost per page for exactly this reason.

Content: Reuse, Rewrite or Create?

Content can be a major variable in a redesign budget because the amount of work changes significantly depending on what can be reused, what needs refinement and what must be created. A practical way to plan it is to sort every page into one of three groups:

• • Reuse: the existing content is still suitable and can move across largely as is.
• • Refine: the content is useful but needs editing, restructuring or updating.
• • Create: the content doesn’t exist yet and has to be written.

For each group, agree who is responsible for:

• • Writing new copy
• • Editing existing copy
• • Supplying photos and other media
• • Moving copy from the old site
• • Entering content into the CMS
• • Approving the final version

Content readiness also affects the schedule. Design and content often progress in parallel, but designing around content that doesn’t exist yet can mean revisiting layouts later. A proposal that assumes you supply final content is pricing a different project from one that includes writing it.

Design and UX Complexity

Design effort depends on how much needs to be invented versus applied. Factors that change it include:

• • Existing brand system vs new visual direction. Applying established colors, type and components is different from developing a new look.
• • Reusable templates vs highly custom pages. A consistent system reduces repeated work.
• • Simple vs custom interactions. Bespoke interface behavior needs design, development and testing.
• • Responsive states. Every component has to work across screen sizes and input methods.
• • Navigation complexity. Large or layered menus take more planning and testing.
• • Accessibility requirements. These shape decisions about color, structure, focus and interaction from the start.
• • Component or design-system creation. Building a documented, reusable system costs more upfront and can make later work more consistent.

More animation or visual complexity doesn’t automatically mean better design; decorative effects add build and testing effort.

Development and CMS Scope

Development effort depends heavily on how much of the existing technical foundation stays in place. Four common scenarios:

1. 1. Same platform, most structure retained. Work concentrates on templates, styling and components, so development is usually the most contained.
2. 2. Same platform, substantial template or component changes. The CMS stays, but many templates are rebuilt or new components are created. Effort rises with the number of unique pieces and how they interact.
3. 3. Platform or CMS change. This adds setup, template rebuilding in the new system and migration work. It doesn’t automatically make the project a full rebuild, but it widens the scope.
4. 4. Custom functionality added. New features that the current site doesn’t have need to be specified, built and tested, whichever platform is used.

Changing platforms should be driven by a real limitation: the current CMS can’t support what the business needs, or it’s become unreasonably hard to manage. Moving simply because a newer option exists adds cost without necessarily adding value.

Features and Integrations

New functionality is where a redesign can quietly turn into a much larger project. Common examples include:

• • Advanced or multi-step forms
• • Booking and scheduling
• • Ecommerce and payments
• • CRM integration
• • Email and marketing platforms
• • Customer login areas
• • Directories and searchable listings
• • Third-party APIs

Each one brings design, configuration, testing and an ongoing dependency on another system. A “website redesign” can become significantly more complex when it also introduces new business functionality.

If the project starts to look more like an authenticated business system, with accounts, permissions and workflows, than a marketing website, it may need a different project scope. Better to recognize that early.

Migration Can Be a Project of Its Own

Migration is the work of making sure nothing valuable is lost between the old site and the new one. On a website redesign, that can include:

• • Page content and CMS entries
• • Images, media and downloadable documents
• • URL mapping and redirects
• • Analytics and tracking setup
• • Forms and where their submissions go
• • Integrations that the old site relied on
• • Historical content, such as older articles or archives

A small site may be migrated by hand. Larger sites, or structured content like product records or directory entries, may need mapping, scripted import and checking. Either way, scope migration explicitly rather than assuming it happens during development.

SEO Migration and Analytics Work

When a redesign changes URLs, content, navigation, internal links, metadata, rendering, the sitemap or tracking, there’s additional migration and verification work to protect what the current site has built up.

Google Search Central’s guidance on site moves with URL changes outlines what’s involved. It recommends mapping old URLs to new ones and using server-side permanent redirects. It also recommends updating internal links, canonicals and sitemaps, then monitoring the results. It also notes that search visibility may fluctuate temporarily during a move. No redesign can promise that rankings will stay exactly as they were, but planning this work reduces avoidable risk.

For budgeting, the key point is that this is real scope. It should appear in the proposal, with clear ownership. The full process is covered in NogaTech’s guide to website redesign SEO.

Accessibility and QA Scope

Accessibility and testing responsibilities are best defined during scoping, not assumed at the end. Retrofitting structural fixes after launch can mean reworking templates that are already built.

The W3C publishes the Web Content Accessibility Guidelines (WCAG) as a technical standard for web accessibility. WCAG 2.2 is the latest WCAG 2 version W3C encourages organizations to use. WCAG 3 is still an incomplete draft and is expected to change before becoming a W3C Standard. Not every redesign involves a formal conformance audit, and this guide doesn’t address legal obligations. But a proposal should say what accessibility work is included.

QA work worth defining includes:

• • Keyboard navigation and focus behavior
• • Form labels and error messages
• • Heading structure
• • Color contrast
• • Responsive behavior across screen sizes
• • Browser and device checks
• • Forms and workflows, end to end
• • Performance checks

Agree which of these are in scope before work begins.

Freelancer vs Agency vs Internal Team

Who does the work shapes both cost and risk. None of these options is inherently cheaper. It depends on the scope and how much coordination it needs.

Many projects mix these: an internal team owns content and approvals while an outside partner handles design and development, for example. What matters is that every responsibility in the scope has a named owner.

Fixed-Price vs Hourly vs Phased Website Redesign

The commercial model affects how risk is shared, not just how the invoice looks.

Fixed price is useful when the scope is well understood. You know the total in advance. The tradeoff is that a fixed price depends on clear assumptions and a defined change-control process. Anything outside those assumptions becomes a change request.

Hourly or time-based pricing suits work where the scope is uncertain or iterative. It adapts as needs become clearer. The tradeoff is that the final total is less fixed, so it needs regular visibility into hours used and remaining.

Phased pricing suits projects that need discovery before the rest can be scoped accurately, or that can be split into logical stages. A common sequence is discovery, then design, then build, then migration and launch.

No model is universally best: a well-defined refresh may suit a fixed price, while an unclear project may suit paid discovery followed by a fixed or estimated build.

What Is Commonly Missing From a Website Redesign Quote?

Providers differ in what they include, so rather than assuming anything is excluded, treat these as items worth checking explicitly:

• • Copywriting and content editing
• • Photography and video
• • Premium fonts and stock assets
• • Third-party software and plugin licenses
• • CMS data entry
• • Content migration
• • URL redirects
• • Integrations
• • Analytics and conversion tracking
• • Accessibility testing
• • Browser and device QA
• • Training and documentation
• • Post-launch support
• • Hosting and ongoing maintenance
• • Future feature work

The lesson isn’t that a lower quote is suspicious. It’s that an apparently cheaper proposal may simply contain fewer responsibilities, with the rest left for you to handle or buy later.

Hosting and maintenance are worth separating in particular, because they’re ongoing costs rather than part of the one-time project. NogaTech’s guide to website maintenance cost covers how to budget for that side.

How to Compare Two Website Redesign Quotes

Put every proposal into the same structure before looking at totals. Fill in what each one says, and use the last column for anything unclear:

The rule is simple: normalize the scope before comparing the total. Once both columns are filled in, a price difference usually either makes sense or reveals a gap.

How to Build a Realistic Website Redesign Budget

A realistic website redesign budget starts by identifying responsibilities, not by picking a number. Build it from these areas:

Discovery / strategy + content + design / UX + development + functionality / integrations + migration + QA / launch + post-launch needs + third-party costs

• Discovery and strategy: the goals, requirements and decisions that define the rest of the project.
• Content: how much is reused, refined or created, and who does each part.
• Design and UX: information architecture, templates, components and responsive layouts.
• Development: CMS work, template and component build, and any platform change.
• Functionality and integrations: new features and connections to other systems.
• Migration: content, media, data, URLs and tracking moving to the new site.
• QA and launch: testing, launch checks and fixes.
• Post-launch needs: a support period, training, early fixes and a plan for ongoing care. Ongoing maintenance is a separate, recurring budget from the one-time redesign.
• Third-party costs: licenses, fonts, stock assets, plugins and subscriptions.

A simple worksheet turns that into decisions:

Any row without an owner is a gap. Any row marked “not included” either needs its own budget or a deliberate decision to leave it out.

15 Questions Before Approving a Website Redesign Quote

When Professional Website Redesign Help Makes Sense

A simpler redesign may be manageable internally or with focused freelance help when:

• • The site is small and relatively simple
• • Content is ready or needs little work
• • URLs will largely stay the same
• • Functionality is straightforward
• • The team has the relevant skills and time

Broader professional support becomes more useful when:

• • The customer journey needs restructuring
• • Content and information architecture both need work
• • The site has many templates
• • Integrations matter to how the business runs
• • Existing search visibility is valuable
• • Migration is substantial
• • Custom functionality is involved
• • Several disciplines need coordinating

NogaTech’s website redesign services can help work through that scope: what to keep, change, add, migrate and verify before committing to a plan. For ongoing care after launch, website growth and support covers that separate need.

Frequently Asked Questions