Website redesign cost is decided mostly by which kind of redesign you are buying: a visual refresh on the same platform, a redesign that also restructures content and UX, or a full rebuild on a new platform with content migration. Each step up adds design, development, migration and testing work, and the platform change is usually the biggest jump. Before you ask for quotes, decide which of the three you need, list what has to be migrated, and know which pages earn your traffic today.
When a client tells us "we need a redesign", we spend the first call working out which of those three projects they mean. Often the honest answer is a smaller one than they expected. Sometimes it is bigger.
What kind of redesign are you actually paying for?
Agencies use "refresh", "redesign", "rebuild" and "migration" loosely, which is one reason quotes are hard to compare. Lean Labs draws the line clearly: a redesign keeps the existing CMS, code and URL structure and works within it, while a rebuild replaces the technology stack and produces a fundamentally new site, and takes months rather than weeks (Lean Labs).
We use four levels:
| Level | What changes | What stays | Typical effort driver |
|---|---|---|---|
| Visual refresh | Colours, typography, imagery, some layouts | Platform, URLs, most content, sitemap | Number of templates restyled |
| UX and content redesign | Navigation, page structure, key copy, new templates | Platform and most URLs | Research, wireframes, copywriting |
| Rebuild on the same platform | Theme or codebase rewritten, content model cleaned up | CMS (for example WordPress), domain | Development and content re-entry |
| Replatform rebuild | New CMS or framework, new hosting, new content model | Domain and brand | Migration, redirects, integrations, training |
Each level includes the work of the one above it. A replatform rebuild still needs the visual and UX design work, so it is the largest project by some distance.
What drives website redesign cost?
These are the drivers we see move redesign estimates most, ordered roughly by impact:
- Platform change. Moving from one CMS to another means a new content model, rebuilt templates, data migration and staff training.
- Content volume and migration. Hundreds of blog posts, product sheets or PDFs take time to move, clean up and check. Manufacturing and B2B sites with large document libraries are hit hardest.
- Integrations to recreate. CRM forms, booking tools, ERP feeds, payment gateways and marketing automation each need rebuilding and retesting.
- Templates to design. The number of unique page layouts matters more than the number of pages.
- Copywriting. A new structure usually exposes old copy that no longer fits. Rewriting is often bigger than anyone planned.
- SEO protection. Redirect mapping, metadata transfer and post-launch monitoring. Skipping it is how redesigns lose traffic.
- Accessibility and performance targets. Meeting WCAG AA or specific Core Web Vitals thresholds needs dedicated testing time.
- Stakeholders and approvals. More decision-makers means more revision rounds.
Is a redesign cheaper than building a new site from scratch?
Not always. A redesign avoids some decisions because the platform and content already exist, but it adds work a new site does not have: auditing what is there, mapping old URLs to new ones, migrating content and protecting rankings. A brand-new business with no traffic has none of those costs.
For an established site, the right comparison is the total over the next three years, not the launch quote. A cheap visual refresh on top of a slow, plugin-heavy or outdated codebase keeps paying the old maintenance and incident costs. A rebuild costs more up front and less to run if the old technical debt is the real problem.
When is a refresh enough?
We advise a refresh, not a rebuild, when most of these are true:
- The site is on a supported, updated platform with no serious security or speed issues.
- Your team can already edit pages without calling a developer.
- The sitemap still matches your services and audience.
- Traffic and enquiries are stable, and the complaint is mainly that it "looks dated".
- Mobile layouts work but need polish.
A refresh can usually keep URLs intact, which removes most of the SEO risk.
When do you need a full rebuild?
A rebuild is usually justified when several of these apply:
- The CMS or theme is unsupported, heavily customised or can no longer be updated safely.
- Simple changes need a developer and take days.
- Pages are slow on mobile and the cause is the theme or builder itself.
- The business has changed (new services, markets or languages) and the structure cannot stretch to fit.
- Integrations break regularly or are held together with workarounds.
- Security incidents have happened more than once.
If three or more apply, patching the old site is likely to cost you more over time than starting clean.
What should a redesign quote include?
Use this list to check a quote. If an item is missing, ask whether it is excluded or simply unlisted.
| Line item | Why it matters | Question to ask |
|---|---|---|
| Content and SEO audit | Shows which pages earn traffic and leads | Which pages will you keep, merge or remove, and how will you decide? |
| Discovery and UX | Prevents redesigning the wrong things | Will you interview users or review analytics before wireframes? |
| Wireframes and design | Sets template count and revision rounds | How many templates and how many rounds are included? |
| Development | Theme or front-end build | Are you rebuilding or modifying the existing code? |
| Content migration | Often underestimated | Who moves content, how many items, and who checks it? |
| Redirect map | Protects rankings and bookmarks | Will every old URL with traffic or links get a 301? |
| Integrations | Forms, CRM, analytics, payments | Which integrations are rebuilt and retested? |
| QA and accessibility | Prevents launch-day bugs | Which devices, browsers and accessibility checks? |
| Launch and monitoring | Catches crawl errors and broken forms | How long do you monitor Search Console and analytics after launch? |
| Training and handover | Lets your team run the site | Do we get documentation and admin training? |
How do you protect SEO during a redesign?
Most lost traffic after a redesign comes from changed URLs without redirects, deleted pages that had links, and content that was cut or rewritten without checking what it ranked for. Google explains how to handle site moves with URL changes, including mapping each old URL to its new equivalent with 301 redirects.
Our step-by-step process is in how to redesign your website without losing SEO rankings, and the common failures are covered in website redesign mistakes that lose Google traffic. Budget time for this work; it is not optional.
How can you keep a redesign under control?
These steps keep redesigns from growing as they go:
- Start with data. Pull the top pages by traffic and by conversions from analytics and Search Console. Those pages define the minimum the new site must protect.
- Run a UX review first. A short UX audit shows whether the problem is layout, content or speed, which tells you the right redesign level.
- Prune before you migrate. Remove or merge thin, outdated pages before migration so you are not paying to move content nobody reads.
- Freeze scope after wireframes. New ideas go into a phase-two list, not into the current build.
- Write copy early. Content arriving late is the most common cause of slipped launches in our projects.
- Name one decision-maker who collects feedback from everyone else.
- Keep the old site running until the new one passes QA on a staging server.
How long does a website redesign take?
Timeline follows the level. A visual refresh is measured in weeks. A replatform rebuild with content migration and integrations is measured in months. The things that stretch it most are late content, slow approvals and integration surprises found during testing. Ask vendors for a phase-by-phase timeline and the client tasks attached to each phase, so delays on your side are visible early.
What surprises come up halfway through a redesign?
In our redesign projects, the surprises are rarely about design. They tend to be one of these:
- Content nobody owned. Pages, PDFs or landing pages created years ago by someone who has left. Somebody now has to decide whether to keep, rewrite or delete each one.
- Hidden integrations. A form that also posts to an old CRM, a script that feeds a partner portal, a tracking pixel the sales team relies on. Ask your current developer for a list before the project starts.
- Licences tied to the old developer. Premium plugins or theme licences registered to a freelancer's account, which stop updating once you move.
- Hosting limits. A new site that needs a newer PHP or Node version than the current host supports.
- Legal and consent changes. Cookie banners, privacy policy updates and accessibility statements that need sign-off from someone outside marketing.
None of these are expensive on their own. Together they are why redesigns overrun. Listing them in the discovery phase turns surprises into scoped tasks.
Bottom line
Redesign cost depends on which level you need: a refresh, a UX and content redesign, a rebuild, or a replatform. Platform change, content migration, integrations and SEO protection drive the estimate far more than visual design does. Audit first, pick the smallest level that solves the real problem, and compare quotes against the same line items.
If you want help deciding between a refresh and a rebuild, our website development and UI/UX design teams can review your current site. Book a free consultation and we will tell you which level we would recommend and why.






