Introduction

A website redesign differs from a new website build in how it handles the existing asset. A new build starts from a blank canvas. A website redesign starts from a documented inventory of what the current website is doing well — organic rankings, conversion rates, user navigation patterns — that must be preserved, and what it is failing to do — specific conversion drop-offs, Core Web Vitals failures, accessibility gaps — that must be fixed. The process reflects this difference at every stage: the audit phase produces the preservation inventory and improvement targets before any design work begins, the information architecture phase builds the redirect map alongside the new structure, and the launch phase stages deployment to protect organic rankings and existing user workflows during the transition. Google Analytics 4, Google Search Console, and Screaming Frog provide the measurement infrastructure across the audit and monitoring phases. WCAG 2.1 accessibility assessment is integrated into the audit phase rather than treated as a post-design compliance check. The Nielsen Norman Group’s research on website redesign outcomes documents the audit-first approach as the strongest predictor of whether a redesign improves commercial performance.

How the Website Redesign Process Works

Definition. The typical website redesign process is a structured sequence of diagnostic, design, development, and measurement activities that transforms a documented set of website commercial performance gaps into a redesigned website — preserving the organic search equity and user familiarity of the existing site while addressing the specific conversion failures, accessibility violations, and technical performance problems the audit identifies, and confirming the improvements through post-launch measurement against documented pre-redesign baselines.

What each stage of the website redesign process produces

• Behavioral audit — a prioritized list of specific website failures ranked by commercial impact, Core Web Vitals baselines, WCAG 2.1 accessibility assessment, SEO structure documentation including URL inventory and organic performance by page, and conversion funnel baselines that post-launch measurement will compare against
• Information architecture and UX design — a validated site map reflecting the redesign’s commercial objectives, a redirect map covering all URLs with organic traffic, wireframes for the highest-friction commercial pages tested with representative users, and a content inventory with disposition decisions for every current page
• Visual design and design system — brand-aligned visual design for all page templates, a design system governing component consistency, mobile-first responsive layouts, and WCAG 2.1 compliant color and interaction design verified before development handoff
• CMS development and SEO implementation — frontend and backend implementation on the chosen CMS platform, 301 redirect implementation and verification, on-page SEO optimization for all pages, Core Web Vitals engineering to Google’s performance thresholds, analytics instrumentation, and pre-launch technical verification
• Staged launch and post-launch monitoring — phased deployment to a traffic subset before full rollout, daily behavioral monitoring in the first two weeks, twelve weeks of weekly Google Search Console monitoring for organic performance, and a sixty-day conversion performance review against pre-redesign baselines

What Is the Typical Website Redesign Process in 5 Steps

1. Conduct the behavioral audit before writing a design brief or briefing any agency on visual direction. Pull twelve months of Google Analytics 4 data for organic traffic by page, conversion rate by primary commercial action, and bounce rate by acquisition source. Export Google Search Console performance data to document which URLs rank for which queries at what positions. Run Screaming Frog to crawl the full current site and identify technical SEO issues — redirect chains, duplicate content, missing canonical tags, crawl errors. Run Google Lighthouse on the five highest-traffic commercial pages to establish Core Web Vitals baselines. Conduct a WCAG 2.1 accessibility assessment covering contrast, keyboard navigation, and screen reader compatibility. This audit produces the three inputs the redesign brief requires: what the current website is doing commercially that must be preserved, what it is failing to do that the redesign must fix, and what the success metrics and baselines are that post-launch measurement will compare against.
2. Define the information architecture and build the redirect map before any visual design begins. Restructure the site’s navigation and URL hierarchy based on the audit’s findings about how users actually navigate versus how the current architecture assumes they navigate. Create the content inventory — listing every page with a disposition decision: migrate unchanged, migrate with revision, consolidate, or remove. Build the redirect map for every URL with organic traffic, mapping each current URL to its destination in the new architecture. Test the structural decisions with five-user prototype sessions using wireframes rather than visual designs — recruiting participants who have used the current website to validate that the new information architecture is navigable by the existing user population. Since 2019, the website redesigns that produce the most consistent organic traffic preservation are those where the redirect map was treated as an information architecture deliverable completed before the architecture was finalized, not as a pre-launch task completed under time pressure.
3. Design the visual system and produce high-fidelity screens from the approved information architecture. Apply brand guidelines to a design system that governs typography, color, spacing, and component behavior across all page templates. Design each template for mobile-first viewport — the majority of organic search traffic on most business websites arrives on mobile, and a design process that produces desktop-primary layouts and adapts them for mobile produces worse mobile experiences than one that starts from mobile constraints. Produce high-fidelity screens for all pages in the redesign scope, covering every state — default, loading, error, empty, success — before development handoff. Run a WCAG 2.1 accessibility audit against the high-fidelity designs before handoff, catching contrast failures, touch target sizing issues, and semantic structure problems that are significantly cheaper to fix in Figma than in production code.
4. Develop the website on the chosen CMS platform with SEO and performance requirements built into the development brief as acceptance criteria rather than as post-launch improvements. Implement all 301 redirects from the redirect map, verify every redirect returns a 301 status code through a pre-launch Screaming Frog crawl, and confirm no redirect chains longer than one hop. Implement on-page SEO optimization for all pages — title tags, meta descriptions, heading hierarchy, image alt text, canonical tags. Engineer Core Web Vitals performance to Google’s Good thresholds — LCP under 2.5 seconds, CLS under 0.1, INP under 200 milliseconds — verified through Google Lighthouse before the staging environment is presented for client review. Configure Google Analytics 4 event tracking for all defined conversion actions and verify tracking before launch. Complete the full pre-launch technical checklist before agreeing a launch date.
5. Launch in stages and monitor organic and conversion performance for twelve weeks. Deploy the redesigned website to a defined traffic subset — if the hosting platform supports it — or to a complete launch with immediate behavioral monitoring configured before the launch date. Monitor Google Analytics 4 daily for the first two weeks, watching for unexpected conversion rate drops on the redesigned commercial flows. Monitor Google Search Console weekly for twelve weeks, reviewing the Performance report for impression and click changes, the Coverage report for indexing errors, and the Core Web Vitals report for field data score updates. Schedule a formal sixty-day review of conversion performance against the pre-redesign baselines documented in the audit phase — the review that confirms whether the redesign produced its intended commercial improvements or whether specific flows need further iteration.

Pro tip: Before setting the launch date, verify that the Google Analytics 4 event tracking for every defined conversion action is firing correctly on the staging environment — not on a test environment where conversion events may be filtered, but on the actual staging URL where the tracking implementation matches what will be deployed. A launch without verified conversion tracking produces the first sixty days of post-launch measurement without the data to confirm improvement against pre-redesign baselines, leaving the redesign’s commercial impact unconfirmed at the moment it is most important to document.

Conclusion

The typical website redesign process — behavioral audit, information architecture with redirect map and prototype validation, visual design, CMS development with SEO implementation, and staged launch with post-launch monitoring — differs from a new website build process at every stage by accounting for the existing website’s organic equity, user familiarity, and commercial performance that must be preserved while specific failures are addressed. The process that consistently produces measurable commercial improvement is the one where the audit precedes the brief, the redirect map precedes the architecture sign-off, and the performance review closes the engagement rather than the launch date. For businesses building the behavioral baseline and SEO documentation that the first stage of this process requires, our UX audit service delivers the prioritized findings, conversion baselines, and organic performance documentation that any website redesign brief depends on. For organizations ready to execute the full process from audit through post-launch measurement, our web development services cover every stage as a single structured engagement with defined gates and commercial outcome accountability.