Back to blog
Web Redesign: How to Plan One That Lifts Conversions

Web Redesign: How to Plan One That Lifts Conversions

Marketer testing redesigned website navigation

A web redesign rebuilds the foundation of a site: its structure, navigation, layout and functionality. It is not a new coat of paint. Done well, it fixes the things that cost you conversions. Done badly, it burns months and can erase the traffic you already have. This guide covers how to tell whether you need one, how to plan it, what drives time and cost, what to check before launch, and how to prove afterward that the new site beats the old one.

TL;DR

  • A redesign changes structure, navigation and functionality. A refresh changes surface elements such as images, copy and minor styling. Pick the smaller job if it solves your problem.
  • Redesign when data says the site fails you: falling conversions, slow pages, poor mobile experience, or goals the current site cannot support. A dated look alone is not enough.
  • Record baseline metrics before you start, set measurable targets, and map every 301 redirect before launch.
  • Plan for roughly 3 to 6 months for a typical project, and more for a complex one.
  • After launch, keep testing. A/B tests on your highest-traffic pages show which changes actually earn their keep.

Table of Contents

What a web redesign is, and how it differs from a refresh

GoDaddy describes a redesign as an overhaul of a site's structure, visuals and functionality aimed at better performance, usability and fit with business goals. A refresh, by contrast, focuses on surface changes like images, copy and minor styling.

Clutch adds useful detail. A refresh covers targeted improvements such as updated colors or images, small UX adjustments, image compression, larger type and performance tweaks on a structure that still works. A redesign may recreate page layouts and brand identity, add functionality such as ecommerce or mobile support, and change page hierarchies and menus.

The line is not rigid. Focus Lab notes that there is no hard boundary between the terms: a refresh revises selected aspects, while a redesign reconsiders the site more fundamentally, including how it behaves, not only how it looks.

Two practical consequences follow:

  • Redesign and rebrand are separate decisions. You can rebuild a site's structure and user journey without changing your brand identity, a point the Rebrand Lab makes in its comparison.
  • Scope is the real variable. If the problem is a weak headline or a cluttered hero image, you have a testing problem, not a redesign problem. Hold that thought; we come back to it below.

Signs your site needs a redesign

HubSpot's list of triggers is a good checklist. Consider a redesign when pages or features are outdated, traffic or conversions decline, pages load slowly, navigation is hard, the brand has evolved, the site is insecure, or visitors struggle to find content. Poor mobile responsiveness and a site that no longer supports current business goals belong on the same list.

Notice what is missing: "it looks old." Ulement makes the point that user feedback, analytics and technical checks should drive the diagnosis, and that dated design alone does not justify the project.

A quick diagnostic

Before you commit, answer these with data, not opinion:

  1. Has conversion rate fallen over the last two to four quarters while traffic held steady?
  2. Do session recordings or support tickets show people getting lost in navigation?
  3. Are mobile conversions far below desktop, even though mobile traffic is large?
  4. Is the site stuck on a CMS or template that blocks changes your team needs?
  5. Does the site still describe what you sell and who you sell it to?

Three or more "yes" answers point toward a redesign. One or two usually point toward targeted fixes, which you can test one at a time.

Start with an audit and a baseline

The most common redesign mistake is starting design before knowing what the current site does. Clear Digital's checklist calls for an audit of analytics, technical, content and security issues, baseline metrics, clear business objectives and early stakeholder alignment. Shopify's guide gives the same order: analyze current performance, gather user, stakeholder and competitor input, and set specific measurable goals before design and development begin.

In practice, capture these numbers before anyone opens a design tool:

  • Conversion rate by page type (home, product, pricing, landing pages) and by device
  • Bounce rate and exit rate on key paths
  • Organic traffic and rankings for the pages that earn you leads or sales
  • Core Web Vitals and load times
  • Your top 20 landing pages by traffic and by revenue, which you must protect

If you need a structured way to run the technical and SEO side, this website audit checklist walks through the steps. Save the results. In three months you will want something to compare against.

Set goals the design must serve

Clear Digital's stance is that business objectives should drive design, with aesthetic choices subordinate to goals such as more qualified leads or fewer support tickets. Write each goal as a number and a date: "raise demo-request conversion from X% to Y% within 90 days of launch." A goal you cannot measure is a preference.

How to carry out the redesign

The sequence below fits most small and mid-sized teams. Adjust the depth, not the order.

  1. Define scope and owners. Name one decision-maker. Scope creep, not design difficulty, is what stretches projects.
  2. Map the structure first. Decide page hierarchy, navigation and key user journeys before visuals. This is the part that makes it a redesign.
  3. Design mobile first. Figma's guide says mobile-first design is essential: prioritize touch-friendly layouts and readable text, then scale up to desktop.
  4. Build accessibility in from the start. ProfileTree recommends automated tools plus manual screen reader testing to meet WCAG rather than treating it as a final polish.
  5. Write content for the new structure. Reusing old copy in a new layout is a quiet way to carry old problems forward.
  6. Build, test and stage. Test across browsers and devices on a staging site.
  7. Launch with redirects and tracking verified. More on this below.
  8. Optimize after launch. The launch is the first version, not the finish.

Do not squeeze the SEO and testing phases when a deadline slips. ProfileTree warns that rushing any phase tends to cost more time than it saves, particularly SEO and testing work.

How long a redesign takes

Incremys puts typical redesigns at 3 to 6 months, with a simple showcase site around 3 months and a complex project up to 9. These are rules of thumb from one source, so treat them as planning ranges.

What stretches a timeline:

  • Content. Writing, approvals and image production are usually slower than design.
  • Stakeholder rounds. Each extra approver adds a feedback loop.
  • Platform change. Moving CMS or ecommerce platforms adds data migration and testing.
  • Integrations. Forms, CRM, payments and analytics each need rework and verification.

Build a buffer for holidays and reviews. A plan with no slack is a plan that will miss its date.

What a redesign costs

Published totals vary widely with scope, so no single number applies to you. What is consistent is the logic. ArcStone explains that a refresh is generally the lower-budget option, while a redesign costs more because of structural changes, possible CMS replacement, broader content and functionality work, and thorough accessibility, speed, security and SEO improvements.

Use these cost drivers to compare quotes line by line:

Cost driverWhat raises itHow to control it
Page countMany unique templates and page typesConsolidate pages; reuse templates
PlatformReplacing the CMS or ecommerce systemKeep the platform if it is not the bottleneck
ContentNew copy, photography, videoAudit and keep content that performs
FunctionalityCustom features, integrationsLaunch core features first, add later
SEO and migrationLarge URL sets, restructured navigationMap redirects early; protect top pages
RevisionsOpen-ended feedback roundsFix the number of rounds in the scope

Get a written scope that says what happens when requirements change. Open-ended projects with vague deliverables are where budgets drift.

Pre-launch checklist: protect traffic and usability

A redesign can lose search visibility if URLs change without a plan. Clear Digital's checklist calls for cross-browser and device testing, verified 301 redirects, accessibility compliance and correct analytics tracking. After launch it adds an XML sitemap and monitoring of Core Web Vitals, load times, uptime, conversion rates, rankings and organic traffic.

Before you push live:

  • Export every current URL and map each to its new destination with a one-to-one 301 where possible
  • Confirm analytics and conversion events fire on the staging site
  • Test forms, checkout and key flows on real phones, not only emulators
  • Run an accessibility pass with automated tools and a screen reader
  • Submit the new sitemap and keep the old baseline report handy
  • Check page speed on the heaviest templates

Shopify also lists features that have stopped working on some browsers or operating systems among the diagnostics to check, which is a reminder to test the unglamorous combinations.

Perspective: redesign less, test more

We build an A/B testing tool, so we have a bias, and we will state it plainly: most teams reach for a full redesign when they actually have five or six specific questions they have never tested. Is the headline clear? Does the form ask for too much? Does the pricing page bury the plan most people need?

A big-bang redesign changes dozens of things at once. If conversions rise, you do not know why. If they fall, you do not know why either. That is a poor way to learn about your customers.

Perspective: redesign less, test more — overview diagram

Our view is that a redesign should be treated as a hypothesis, not a verdict. Redesign the structure when the data demands it, but validate the new pages the way you would validate any change: split traffic, compare against the old version, and keep what wins. Script weight matters here too. A testing tool that slows the page you are trying to improve defeats the purpose, which is why we built Stellar's script at only 5.4KB.

If you cannot yet justify the full project, start by testing the pages that matter most. Our guides on A/B testing for landing pages and steps to improve conversions on your site show where to begin, and the A/B testing ideas library gives you concrete experiments to run before you commit a budget.

— Juan

Measure whether the redesign worked

Shopify's advice is to define measurable targets and evaluate the redesign against them, using bounce and conversion rates and search rankings. Clear Digital adds the discipline of validating analytics tracking and monitoring performance after launch.

A simple measurement plan:

  1. Compare like with like. Use the same date ranges, device splits and traffic sources as your baseline. A launch during a seasonal peak will flatter the results.
  2. Watch leading and lagging indicators. Bounce rate and engagement move first. Revenue and lead quality take longer.
  3. Segment. A redesign can help mobile and hurt returning desktop users. Averages hide that.
  4. Check search. Expect some ranking movement in the weeks after launch. A sustained drop on money pages points to a redirect or content problem.
  5. Keep experimenting. Clear Digital recommends building an experimentation culture, such as A/B testing, focused on high-traffic pages, so conversion gains compound after launch.

Test the redesign before you roll it out

If traffic allows, do not switch everyone at once. Run the new page against the old one for a defined period and compare conversions. Headlines, hero media, calls to action and form length are good first tests. Our posts on landing page headline tests and video versus image on landing pages cover two of the highest-impact elements.

Test your redesign with Stellar

Stellar is an A/B testing platform for marketers and growth teams. You build variants in a no-code visual editor, track goals, and read results in real-time analytics, without waiting on developers. The script is a lightweight 5.4KB, so your tests do not drag down the pages you are improving. Stellar also integrates with WordPress, Shopify, Webflow, Wix, Squarespace, Framer and Bubble.

Plans are priced by monthly tracked users: Sandbox is $0 per month, Plus is $29 per month, Pro is $99 per month and Scale is $399 per month. Enterprise has no published price. The free plan is for businesses with under 25,000 monthly tracked users. See the plans on the Stellar site and start by testing one page of your redesign.

Common redesign mistakes

  • Designing before diagnosing. If you cannot name the problem in numbers, the redesign has no target.
  • Changing everything at once. Keep what converts. Your analytics will tell you which pages those are.
  • Skipping redirects. Orphaned URLs lose rankings and send visitors to error pages.
  • Treating launch as the end. Sites need ongoing testing and maintenance, or they drift back to where they started.
  • Letting taste outrank evidence. Stakeholder preference is a input, not a result. Test it.

FAQ

What is the difference between a website redesign and a refresh?

A redesign overhauls structure, navigation, layout and functionality. A refresh updates surface elements such as images, copy, colors and minor UX details on a structure that still works. If your problems are about how the site is organized or what it can do, redesign. If they are about polish, refresh.

How much does it cost to have a website redesigned?

It depends on page count, platform changes, content needs, integrations and SEO migration. A redesign generally costs more than a refresh because it involves structural changes and broader work. Ask each provider for an itemized scope so quotes are comparable.

How long does a redesign take?

One industry guide cites roughly 3 to 6 months for typical projects, around 3 for a simple site and up to 9 for a complex one. Content approvals and platform migrations are the usual causes of delay.

Will a redesign hurt my SEO?

It can if URLs change without a plan. Map and verify 301 redirects, submit a new XML sitemap and monitor rankings, load times and organic traffic after launch, as Clear Digital's checklist advises.

How do I know the new design converts better?

Compare against baseline metrics you recorded before starting, using the same date ranges and segments. For the cleanest answer, split traffic between old and new pages in an A/B test and compare conversion rates.

Sources

Recommended