9 Phases of a Website Redesign Process That Actually Ship in 2026

Most website redesigns fail before a single pixel moves, because teams treat the redesign as a visual refresh instead of a business system. A disciplined website redesign process protects revenue, compresses timelines by 30 to 40 percent, and prevents the six-figure rebuilds we see when companies skip discovery and jump straight to a new theme. We have run this sequence dozens of times, and the pattern is consistent: the teams that respect the phases ship faster, convert better, and stop guessing.

TL;DR

• SEQUENCE BEATS SPEED: A structured website redesign process (audit, strategy, content, design, build, QA, launch) reliably ships 4 to 12 weeks faster than an ad-hoc rebuild because rework drops by roughly 50 percent.
• CONTENT AND SEO COME BEFORE DESIGN: Teams that lock messaging, URL mapping, and redirects before visual design protect 60 to 90 percent of existing organic traffic instead of tanking it on launch day.
• MEASURE IN 30/60/90: The redesign is not done at launch; you validate it against conversion rate, organic sessions, and Core Web Vitals over the first 90 days, then iterate.

Quick Comparison: The 9 Phases at a Glance

#	Phase	Primary Value	Setup Effort	Expected Impact
1	Redesign Audit & Baseline	Know what to keep vs. kill	Medium	Prevents 100% of blind traffic loss
2	Goals & KPI Definition	Ties design to revenue	Low	Aligns team, cuts scope creep 40%
3	Competitive & UX Research	Evidence over opinion	Medium	20-35% higher task success
4	Information Architecture	Users find things	Medium	Cuts bounce 15-25%
5	Content Strategy & Copy	The real conversion lever	High	2-3x lift on key pages
6	Visual Design & Prototyping	Brand + usability	High	10-30% conversion lift
7	Development & Build	Fast, accessible, stable	High	Core Web Vitals pass rate 90%+
8	QA, SEO Migration & Redirects	Protect rankings	Medium	Retains 80-95% organic traffic
9	Launch & 30/60/90 Optimization	Compounding gains	Ongoing	15-50% cumulative CRO uplift

The phases below run roughly in order of leverage. Skip early phases and you pay for it in later ones at 3x the cost. Let’s break each one down the way we scope it for clients.

1. Redesign Audit and Baseline

You cannot improve what you have not measured. Before anyone opens Figma, we pull a full baseline of the current site so every future decision is defensible. This is the single most skipped phase, and skipping it is why so many redesigns quietly lose 40 to 70 percent of organic traffic within a month of launch. At Presta, we treat the audit as a legal deposition: everything on record, nothing assumed.

Key Steps:

• Analytics baseline: Export 12 months of traffic, conversion, and revenue data by page so you have a before/after benchmark.
• Top-page inventory: Rank every URL by traffic and revenue to identify the pages you must not break.
• Technical crawl: Run a full site crawl for broken links, redirect chains, thin content, and indexation issues.
• Heatmap and session review: Watch real users to find the friction the numbers alone won’t show.
• Keyword and backlink map: Record which URLs earn rankings and backlinks so you can preserve that equity.

Advantages:

• Turns opinion-driven debates into data-driven decisions in about a week.
• Identifies the 20 percent of pages driving 80 percent of revenue, so effort goes where it matters.
• Creates the baseline you will report against at 30, 60, and 90 days.
• Surfaces quick wins worth acting on before the redesign even starts.

Limitations:

• Requires clean analytics; if tracking was broken, expect to spend extra days reconstructing history.
• Tempting to over-audit and delay; cap it at 5 to 8 business days.

Complexity: Medium. Best for: every redesign, no exceptions. Expected result: prevents the blind 40 to 70 percent traffic loss that kills unaudited relaunches, typically protecting five to six figures in monthly revenue.

2. Goals and KPI Definition

A redesign without a numeric target is a decoration project. Before design, we force a conversation about what the new site must do in dollars, leads, or signups, then we translate that into two or three measurable KPIs. When we scope this for clients, the exercise usually cuts the wish list in half, because most feature requests do not map to any goal.

Key Steps:

• Primary business goal: Name the one metric the redesign exists to move (e.g. demo requests, revenue per session).
• Supporting KPIs: Define 2 to 3 secondary metrics like bounce rate, page speed, or organic sessions.
• Baseline vs. target: Set a specific number and timeframe for each KPI (e.g. lift lead conversion from 1.8% to 3.0% in 90 days).
• Non-goals: Explicitly list what this redesign will not try to fix, to protect scope.
• Stakeholder sign-off: Get one document everyone agrees on before design starts.

Advantages:

• Reduces scope creep by roughly 40 percent because every request gets tested against a goal.
• Gives the design team a north star, speeding up decisions.
• Makes success objectively provable at launch, not a matter of taste.
• Aligns marketing, sales, and leadership on one page.

Limitations:

• Leadership sometimes resists committing to numbers; push through it.
• Vanity metrics creep in; keep KPIs tied to revenue or pipeline.

Complexity: Low. Best for: teams with more than one stakeholder. Expected result: 40 percent less scope creep and a redesign that can prove its worth.

3. Competitive and UX Research

Research replaces expensive guessing. We study how competitors and adjacent leaders solve the same user problems, then validate assumptions with lightweight user testing. This phase turns “I think users want X” into “we watched five users struggle with Y.” Our team frequently builds a simple research repository here so insights don’t evaporate the moment design begins.

Key Steps:

• Competitor teardown: Analyze 4 to 6 competitors’ navigation, messaging, and conversion paths.
• User interviews: Talk to 5 to 8 real or target users about their goals and frustrations.
• Task-based testing: Ask users to complete key tasks on the current site and record where they stall.
• Jobs-to-be-done map: Capture what users are actually hiring your site to do.
• Insight synthesis: Consolidate findings into 5 to 10 prioritized problem statements.

Advantages:

• Improves task success rates by 20 to 35 percent when the design responds to real friction.
• Kills bad ideas cheaply, before they cost development hours.
• Builds a shared evidence base that ends internal opinion wars.
• Uncovers messaging gaps competitors are exploiting.

Limitations:

• Can slip into analysis paralysis; timebox to 1 to 2 weeks.
• Small sample sizes are directional, not statistically bulletproof.

Complexity: Medium. Best for: sites with unclear conversion problems. Expected result: 20 to 35 percent higher task completion on redesigned flows.

4. Information Architecture and User Flows

If users can’t find it, it doesn’t exist. Information architecture is the skeleton of the redesign, and getting it right is worth more than any hero animation. We map every important page, define the navigation, and design the flows for your highest-value conversion paths before touching visuals. This is where the earlier audit and research pay off directly.

Key Steps:

• Content inventory to sitemap: Turn the audited page list into a clean, prioritized sitemap.
• Card sorting: Let users group content so navigation matches their mental model, not your org chart.
• Primary flow mapping: Diagram the 2 to 3 flows that drive the most revenue or leads.
• Navigation design: Define global nav, footer, and internal linking logic.
• URL structure planning: Design clean, SEO-friendly URLs and note every change for later redirects.

Advantages:

• Cuts bounce rates 15 to 25 percent when navigation matches user expectations.
• Shortens conversion paths, often removing 1 to 3 unnecessary steps.
• Creates the blueprint developers and designers both build against.
• Establishes the URL map that protects SEO in phase 8.

Limitations:

• Requires cross-team agreement, which takes time to negotiate.
• Poorly documented IA leads to rework in design and build.

Complexity: Medium. Best for: sites with more than 20 pages or complex navigation. Expected result: 15 to 25 percent lower bounce and measurably shorter conversion paths. For a fuller walkthrough of how we sequence this, see our breakdown of the journey of a new website functional specification.

Section checklist:

• Sitemap: Approved and mapped to business goals.
• Flows: Top conversion paths diagrammed and validated.
• Navigation: Global and contextual navigation defined.
• URLs: New structure documented with old-to-new mapping started.
• Sign-off: Stakeholders have reviewed the architecture before design.

5. Content Strategy and Copy

Design gets the credit, but content does the converting. This is the phase teams underestimate the most, and it is where we see the biggest gap between mediocre and exceptional redesigns. Messaging, page structure, and copy should be locked before high-fidelity design so designers build around real words, not lorem ipsum. At Presta, we’ve seen conversion lifts of 2 to 3x on key pages driven almost entirely by sharper messaging, no visual change required.

Key Steps:

• Messaging framework: Define value proposition, proof points, and objection handling per page.
• Content audit decisions: Decide what to keep, rewrite, merge, or retire from the current site.
• Page-level content briefs: Give each priority page a purpose, target keyword, and desired action.
• SEO content mapping: Assign target keywords and search intent to each URL.
• Copywriting: Write the real copy, headlines first, before design begins.

Advantages:

• Drives 2 to 3x conversion lifts on hero and product pages from messaging alone.
• Aligns copy with search intent, supporting organic recovery post-launch.
• Eliminates costly redesign rework caused by content that doesn’t fit the layout.
• Gives the brand a coherent voice across the site.

Limitations:

• Content is often the biggest bottleneck; start it early or it delays everything.
• Requires subject-matter input from busy internal experts.

Complexity: High. Best for: every redesign, especially lead-gen and ecommerce. Expected result: 2 to 3x conversion lift on priority pages. Our detailed take on this lives in the journey of a new website content guide.

A website redesign is not a paint job; it is a content and conversion system that happens to have a visual layer.

Let’s Build a Redesign That Actually Moves Revenue

If you’re staring at an aging site that’s leaking leads and you don’t have the internal bandwidth to run all nine phases properly, this is exactly what our Startup Studio was built for. We compress a redesign that would take an internal team 5 to 6 months into a focused 8 to 14 week engagement, and we bring the audit, content, design, and SEO migration under one accountable roof so nothing falls through the cracks. Tell us your goals and current numbers, and we’ll map the fastest path to a site that converts: hire the Presta Startup Studio or get in touch with our team.

6. Visual Design and Prototyping

Now, and only now, does the site start to look like a site. With architecture and content locked, design becomes a high-leverage layer instead of a guessing game. We work mobile-first, design in components, and prototype the key flows so stakeholders can click through the experience before a line of code is written. This is where brand and usability finally meet.

Key Steps:

• Design system: Build reusable components, colors, type, and spacing for consistency and speed.
• Wireframes to hi-fi: Move from low-fidelity layouts to polished, on-brand screens.
• Interactive prototype: Make the top flows clickable for realistic stakeholder review.
• Accessibility baked in: Design for WCAG AA contrast, focus states, and readable type from the start.
• Design QA: Review every screen against the KPIs and content briefs from earlier phases.

Advantages:

• Delivers 10 to 30 percent conversion lifts when design reduces friction on key flows.
• A design system cuts future page-build time by 40 to 60 percent.
• Prototypes catch usability problems while fixes still cost minutes, not developer days.
• Mobile-first design protects the majority of traffic on most modern sites.

Limitations:

• Endless revision cycles waste budget; cap major review rounds at two.
• Design without a system creates inconsistency and slows development.

Complexity: High. Best for: brand-driven and conversion-critical sites. Expected result: 10 to 30 percent conversion lift plus a reusable design system. See how we approach the visual layer in the journey of a new website design breakdown.

Section checklist:

• System: Component library and tokens are documented.
• Prototype: Top flows are clickable and reviewed.
• Accessibility: Contrast and focus states meet WCAG AA.
• Responsive: Mobile, tablet, and desktop layouts are approved.
• Handoff: Developer-ready specs and assets are exported.

7. Development and Build

This is where design meets reality, and where cutting corners costs the most later. We build with performance, accessibility, and maintainability as first-class requirements, not afterthoughts. A beautiful design on a slow, brittle build will underperform an average design on a fast one every single time, because Core Web Vitals now directly influence both rankings and conversion.

Key Steps:

• Environment setup: Stand up staging, version control, and a deployment pipeline.
• Component build: Develop reusable, tested components matching the design system.
• CMS configuration: Make content editable by your team without a developer for every change.
• Performance budget: Enforce limits on image weight, scripts, and third-party bloat.
• Integrations: Wire up analytics, forms, CRM, and any commerce or booking tools.

Advantages:

• A performance budget pushes 90 percent-plus of pages to pass Core Web Vitals.
• Component-based builds cut future maintenance costs by 30 to 50 percent.
• A well-configured CMS saves your team 5 to 10 hours of dev requests per month.
• Staging environments let you test everything before it touches live traffic.

Limitations:

• Scope creep during build inflates timelines fast; freeze the design first.
• Cheap builds accrue technical debt that surfaces within 6 to 12 months.

Complexity: High. Best for: every redesign; the more integrations, the more this matters. Expected result: 90 percent-plus Core Web Vitals pass rate and 30 to 50 percent lower maintenance cost. When debugging inevitably arises, our systematic approach to debugging keeps the build stable. For the broader build stage, the journey of a new website starting development piece walks through it.

The 5-Step Traffic Preservation Framework

Losing organic traffic on launch is the most common and most expensive redesign failure. This is the framework we run for every migration to keep rankings intact. We call it the Traffic Preservation Framework, and it has helped clients retain 80 to 95 percent of organic sessions through launches that competitors bungle.

Step	Action	Timeframe	Outcome
1	Map every old URL to a new one	2-3 days	Zero orphaned URLs
2	Build 301 redirects for changed URLs	1-2 days	No 404s on indexed pages
3	Preserve or improve on-page SEO per page	3-5 days	Rankings held or lifted
4	Update internal links and XML sitemap	1 day	Clean crawl signals
5	Monitor Search Console daily post-launch	30 days	Catch drops within 24-48 hrs

Follow this and a migration that would otherwise cost you 40 percent of traffic instead holds 90 percent-plus. The website redesign roadmap shows how this fits the wider plan.

8. QA, SEO Migration, and Redirects

Launch day is not the finish line; it’s the highest-risk moment of the entire website redesign process. This phase is where meticulous teams separate from reckless ones. We run functional QA, cross-browser and device testing, accessibility checks, and the full SEO migration in parallel so nothing ships broken. When we scope this for clients, we insist on a pre-launch checklist signed off by both dev and marketing.

Key Steps:

• Functional QA: Test every form, flow, and integration across browsers and devices.
• Redirect implementation: Deploy and test all 301 redirects from the mapping step.
• SEO migration checks: Verify titles, metadata, structured data, and canonical tags per page.
• Accessibility audit: Run automated and manual WCAG AA checks and fix blockers.
• Performance validation: Confirm Core Web Vitals and load times on real devices.

Advantages:

• Retains 80 to 95 percent of organic traffic through the transition.
• Catches conversion-killing bugs before real users hit them.
• Protects legal and brand risk by ensuring accessibility compliance.
• Confirms the site actually delivers the speed promised in the build.

Limitations:

• Rushed QA is a false economy; budget at least a week for a mid-sized site.
• Redirect mistakes can silently kill rankings; double-check every one.

Complexity: Medium. Best for: any site with existing SEO equity. Expected result: 80 to 95 percent organic traffic retention and a bug-free launch.

Section checklist:

• Redirects: Every changed URL 301s correctly to its match.
• Forms: All lead and commerce flows tested end to end.
• Metadata: Titles, descriptions, and schema verified per page.
• Accessibility: WCAG AA blockers resolved.
• Speed: Core Web Vitals pass on mobile and desktop.

9. Launch and 30/60/90 Day Optimization

The best redesigns keep improving after launch. We treat go-live as the start of the optimization phase, not the end of the project. Real user data replaces assumptions, and the redesign compounds in value as you iterate against the KPIs you defined in phase 2. This is how a good launch becomes a great asset.

Key Steps:

• Controlled launch: Deploy, verify redirects, and monitor error logs in the first 24 hours.
• Analytics validation: Confirm tracking fires correctly on every key event.
• Search Console watch: Monitor indexation and rankings daily for the first month.
• A/B testing queue: Prioritize experiments on high-traffic, high-value pages.
• Iteration cadence: Ship data-driven improvements every 2 to 4 weeks.

Advantages:

• Delivers a 15 to 50 percent cumulative conversion uplift over the first 90 days.
• Catches SEO drops within 24 to 48 hours instead of months later.
• Turns the redesign into a living, improving asset instead of a static project.
• Builds an experimentation habit that keeps paying off long after launch.

Limitations:

• Requires ongoing attention and testing tools that teams often abandon.
• Early data is noisy; avoid overreacting to a single week.

Complexity: Ongoing. Best for: teams committed to growth, not just a facelift. Expected result: 15 to 50 percent cumulative CRO uplift in 90 days. See the full journey of a new website for how launch fits the arc, and how we handle progress tracking throughout.

KPIs and Measuring Success: The 30/60/90 Day View

A redesign is only successful if the numbers say so. Here is how we frame outcomes across the first quarter post-launch, tied directly to the goals set in phase 2.

Window	Primary Focus	Target Signals	Red Flags
First 30 days	Stability & retention	Traffic within 90% of baseline, zero critical bugs, Core Web Vitals pass	Traffic drop over 15%, spike in 404s
Days 31-60	Recovery & early lift	Rankings recovered, conversion at or above baseline	Flat or declining conversion
Days 61-90	Optimization & growth	15-50% conversion uplift, organic sessions above baseline	No measurable improvement

30-day priorities:

• Retention: Confirm organic traffic is within 90 percent of baseline.
• Stability: Resolve all critical bugs within 48 hours of discovery.
• Speed: Verify Core Web Vitals pass on real devices.
• Tracking: Ensure every conversion event fires correctly.

60-day priorities:

• Rankings: Confirm keyword positions have recovered to pre-launch levels.
• Conversion: Reach or exceed baseline conversion rate.
• Testing: Launch your first two A/B experiments on top pages.

90-day priorities:

• Uplift: Document a 15 to 50 percent cumulative conversion improvement.
• Growth: Confirm organic sessions are trending above baseline.
• Roadmap: Build the next-quarter optimization backlog from real data.

If you’re just getting started, resist the urge to open a design tool. Begin with phases 1 and 2, the audit and the KPI definition, because those two weeks of work protect every dollar you spend later and settle 80 percent of the arguments before they start. If instead you’re auditing an existing redesign that stalled or underperformed, jump to the Traffic Preservation Framework and the 30/60/90 KPI view first; nine times out of ten the problem is a broken migration or the absence of any measurable goal, and both are fixable without starting over. Whether you handle this in-house or bring in help, the sequence is what saves you, and knowing what makes you an ideal client for a presentational website helps you scope realistically.

Next Steps:

• Pull baseline: Export 12 months of traffic and conversion data this week.
• Define one KPI: Commit to a single primary metric and target number.
• Map your top URLs: List the 20 pages you cannot afford to break.

Frequently Asked Questions

What is the website redesign process?

The website redesign process is the structured sequence of phases that takes a site from its current state to a new, improved version without losing traffic, rankings, or revenue along the way. It typically runs through nine phases: audit and baseline, goals and KPI definition, research, information architecture, content strategy, visual design, development, QA and SEO migration, and post-launch optimization. Each phase feeds the next, which is why skipping early ones is so costly.

The critical thing to understand is that a redesign is a business system, not a visual project. The visual layer is only one of nine phases, and arguably not even the most important one. Content strategy and SEO migration usually have more direct impact on results than the design itself. Teams that treat the process as “get a new theme” consistently underperform teams that respect the full sequence.

At Presta, we’ve refined this process across dozens of engagements, and the biggest predictor of success is whether a team is willing to do the unglamorous early work: the audit, the goals, and the content. Those phases are boring, and they are where the money is made.

How long does the website redesign process take?

For a typical small-to-mid-sized business site, a well-run redesign takes 8 to 14 weeks from kickoff to launch, with the post-launch optimization phase running an additional 90 days. Larger sites with complex integrations, ecommerce, or heavy content volumes can run 4 to 6 months. The single biggest variable is content: if internal experts are slow to provide input and copy, timelines can double.

Here is a rough breakdown of where the time goes: audit and strategy take 2 to 3 weeks, research and architecture another 2 to 3 weeks, content and design run 3 to 4 weeks (often overlapping), development takes 3 to 5 weeks, and QA plus migration takes about a week. These overlap in practice, which is how experienced teams compress the total.

The fastest way to blow the timeline is scope creep during the build phase and slow stakeholder approvals. We reduce both by locking scope in phase 2 and capping review rounds. An agency that has done this many times will typically ship 30 to 40 percent faster than an internal team doing it for the first time, simply because the process is muscle memory.

What are the key steps in a website redesign?

The key steps map directly to the nine phases in this article: audit your current site and establish a baseline, define measurable goals and KPIs, research competitors and users, design the information architecture and user flows, develop the content strategy and write real copy, create the visual design and prototype, build the site with performance and accessibility in mind, run QA and the SEO migration with redirects, and then launch and optimize over 30/60/90 days.

If you had to compress this into the four non-negotiables, they would be: audit before you touch anything, lock content before design, protect SEO with a proper redirect map, and measure results against a numeric goal. Miss any one of those and the odds of a disappointing outcome rise sharply. The other steps improve the result; these four prevent disaster.

The steps are ordered by leverage, not by when they feel exciting. Design feels like the exciting part, which is exactly why teams rush to it and skip the steps that actually determine whether the redesign works.

How do I keep my SEO rankings during a redesign?

Rankings are lost during redesigns almost entirely because of poor URL handling. When URLs change and no redirects are put in place, search engines find dead pages, drop them from the index, and your traffic falls off a cliff. The fix is the Traffic Preservation Framework: map every old URL to a new one, build 301 redirects for anything that changed, preserve on-page SEO per page, update internal links and your sitemap, and monitor Search Console daily for the first month.

Beyond redirects, keep or improve the content on your highest-value pages rather than gutting it. Search engines reward continuity of quality content. If a page ranks well, the redesign should make it better, not replace it with something thinner. Preserve titles, headings, and the core content that earned the ranking in the first place.

The reason we monitor Search Console daily post-launch is that early detection is everything. A ranking drop caught within 48 hours is usually a quick fix; the same drop caught after a month may have compounded into significant revenue loss. Vigilance in the first 30 days is worth more than any optimization you do later.

When does it make sense to bring in Presta’s Startup Studio for a redesign?

Honestly, not every redesign needs an agency. If you have a small brochure site, an internal designer and developer with spare capacity, and a straightforward URL structure, you can run this process yourself using the phases in this article. Plenty of teams do, and we would rather you spend your budget wisely than hire help you don’t need.

The threshold where it becomes worth bringing us in is usually one of three situations. First, when the site is tied to meaningful revenue and a botched migration could cost you five or six figures, the risk justifies experienced hands. Second, when your internal team is at capacity and the redesign would drag on for 6 to 9 months around other work, we can compress it into 8 to 14 weeks. Third, when the site has complex integrations, significant existing SEO equity, or ecommerce, where the margin for error is thin.

Our Startup Studio was built precisely for teams that need the full nine-phase process run properly and fast, without staffing up internally. When the cost of doing it slowly or getting it wrong exceeds the cost of the engagement, that’s the point where hiring an experienced agency pays for itself. Our take on why you should hire an experienced agency goes deeper on that math.

Should I redesign or rebuild from scratch?

This depends on the state of your current site. A redesign keeps the underlying content, structure, and SEO equity and improves on it, which is faster and lower-risk. A rebuild starts fresh, which makes sense when the existing platform is genuinely unsalvageable, when you’re changing technology stacks, or when the information architecture is so broken that patching it would cost more than starting over.

As a rule of thumb, if more than 60 percent of your current content and structure is worth keeping, redesign. If less than 40 percent is worth keeping, a rebuild may be cleaner. In the middle, it’s a judgment call that the audit phase should settle. That’s another reason phase 1 matters so much: it gives you the data to make this decision instead of guessing.

Either way, the process in this article applies. A rebuild still needs the audit, the goals, the content strategy, and especially the SEO migration. The phases don’t change; only the amount you carry forward does.

How much does a professional website redesign cost?

Costs vary enormously based on scope, but for context, a professional redesign of a small business site typically ranges from a few thousand dollars for a light refresh to $25,000 to $75,000 for a full nine-phase engagement with content, custom design, and development. Complex ecommerce or enterprise sites can run well beyond that. The biggest cost drivers are content volume, custom functionality, and the number of integrations.

The temptation is to optimize for the lowest upfront price, but that’s usually a mistake. A cheap build accrues technical debt that surfaces within 6 to 12 months, and a redesign that ignores SEO migration can cost you far more in lost traffic than you saved on the project. We tell clients to budget for the full process and treat it as a revenue investment measured against the KPIs from phase 2.

The ROI framing matters more than the sticker price. If a redesign lifts your conversion rate from 1.8 percent to 3.0 percent on a site doing meaningful traffic, that improvement often pays back the entire project within a few months. That’s the number to focus on, not just the invoice.

Sources

• Google Search Central: Site moves with URL changes
• Google: Core Web Vitals and page experience
• Nielsen Norman Group: How Many Test Users in a Usability Study
• Web Content Accessibility Guidelines (WCAG) 2.1
• Google Search Console Help: Monitoring your site