The Website Redesign Playbook: When, Why, and How to Do It Right

A furniture retailer came to us in 2023 after their previous agency redesigned their website. Traffic looked great during the first week - everyone was excited about the fresh look. Then the Google Search Console data came in. Organic traffic had dropped 62% in three weeks. The agency had changed every URL on the site, set up zero redirects, and deleted 40 pages of content they considered "outdated." It took us five months to recover what they lost in five days. A website redesign done wrong is one of the most expensive mistakes a business can make. Done right, it's a growth multiplier. Here's how to do it right.

When It's Actually Time for a Redesign

Not every problem requires a full redesign. Sometimes you need a refresh, sometimes you need targeted fixes, and sometimes you need to burn it down and start over. Here's how to tell the difference.

Signals That Scream "Redesign Now"

Your bounce rate has been climbing for 6+ months. A homepage bounce rate above 55% for a service business or above 45% for e-commerce (measured in GA4, which calculates it differently than Universal Analytics did) is a red flag. If it's trending upward despite consistent traffic quality, your design is losing people.

Mobile conversion rates are less than half of desktop. With mobile traffic typically at 60-70% for most businesses, a mobile experience that converts at 1.2% versus desktop's 3.8% means you're leaving money on the table every day. We see this pattern constantly in sites built before 2020 that were "responsive" but never truly mobile-first.

Your CMS is fighting you. If adding a new page or updating content takes your team more than 15 minutes, your technology is a bottleneck. We've seen companies running WordPress sites with 47 plugins, 3 page builders stacked on top of each other, and load times approaching 9 seconds. At that point, patching won't help.

Your site fails Core Web Vitals. Check PageSpeed Insights. If your Largest Contentful Paint is over 4 seconds, Cumulative Layout Shift is above 0.25, or Interaction to Next Paint exceeds 500ms on mobile, Google is actively deprioritizing your pages. These metrics became ranking factors in 2021 and their weight has only increased.

Visual design is more than 4-5 years old. Design trends shift, but more importantly, user expectations shift. Patterns that felt modern in 2021 - heavy hero sliders, hamburger menus on desktop, stock photo grids - now signal "nobody maintains this site." Trust erodes before the visitor reads a single word.

Signals That Need a Refresh, Not a Redesign

If your site architecture, CMS, and URL structure are solid but the visual design feels dated, you might only need a CSS overhaul and updated imagery. If conversions are dropping on specific pages but the rest of the site performs well, targeted landing page optimization is cheaper and faster.

Phase 1: The Pre-Redesign Audit

Before you write a single line of code or pick a colour palette, you need to understand exactly what you have and what's working.

Content Audit

Export every URL from your site. We use Screaming Frog - crawl the site, export to CSV, and you'll have every page, its title, meta description, word count, and status code. For a 200-page site, this takes about 10 minutes.

Now categorize every page into one of four buckets:

Keep as-is - High traffic, good conversions, strong backlink profile. Don't touch these pages beyond design updates.
Update and keep - Decent content but needs refreshing. Outdated stats, old screenshots, thin content that could be expanded.
Merge - Multiple pages covering the same topic. Combine them into one authoritative page and redirect the others.
Remove - Zero traffic, no backlinks, no conversions for 12+ months. Redirect to the most relevant remaining page.

We did this for an accounting firm's website and reduced their page count from 186 to 94. The surviving 94 pages were stronger, more focused, and easier to maintain. Organic traffic increased 23% within four months of the redesign launch - partly from consolidating thin content into comprehensive pages.

Backlink Audit

Run your domain through Ahrefs or SEMrush. Export every page with at least one referring domain. These pages are non-negotiable - their URLs must either stay the same or have proper 301 redirects. Losing a page with 45 referring domains because someone thought "/services/consulting" should become "/what-we-do/business-consulting" without a redirect is a painful, avoidable loss.

Performance Baseline

Document your current metrics before you change anything:

Organic traffic by landing page (last 12 months)
Conversion rates by page and device type
Core Web Vitals scores
Top 50 keyword rankings
Indexed page count in Google Search Console

This baseline is your scoreboard. After launch, you'll compare every metric against it to measure whether the redesign was a success or a regression.

Phase 2: The Migration Plan

This is where most redesigns go wrong. The design gets all the attention; the migration gets a sticky note that says "set up redirects before launch."

URL Mapping Document

Create a spreadsheet with every current URL in column A and the corresponding new URL in column B. Every. Single. URL. Not just the main pages - blog posts, category pages, images, PDFs, everything that Google has indexed.

If you're keeping the URL structure the same (which we strongly recommend unless there's a compelling reason to change it), most rows will be identical. But you still need the document to catch the exceptions - pages being merged, removed, or restructured.

301 Redirect Plan

For every URL that changes, create a 301 redirect from the old URL to the new one. Not 302 (temporary) - 301 (permanent). This tells search engines to transfer the ranking signals from the old URL to the new one.

Implementation depends on your server:

Apache: .htaccess with Redirect 301 /old-path /new-path or RewriteRule for pattern-based redirects
Nginx: rewrite ^/old-path$ /new-path permanent; in your server block
OpenLiteSpeed: Rewrite rules in .htaccess work, but be aware that not all Apache directives are compatible - test thoroughly
WordPress: Use the Redirection plugin for manageable lists, or server-level redirects for performance on large sites

Test every redirect before launch. We use a script that crawls the old URL list and checks that each one returns a 301 to the correct destination. Manually checking 200 redirects is error-prone; automate it.

Sitemap Preparation

Have your new XML sitemap ready before launch day. Submit it to Google Search Console within the first hour after going live. This prompts Google to crawl your new URLs quickly rather than discovering changes gradually over weeks.

Phase 3: Design and Development

We won't prescribe design trends - those depend on your industry, audience, and brand. But here are principles that consistently produce better outcomes.

Mobile-First Is Not Optional

Design for the smallest screen first, then scale up. We still see agencies designing desktop first and then cramming the layout onto mobile. The result is always compromised - text that's too small, tap targets too close together, forms that require horizontal scrolling.

Speed Is a Feature

Set a performance budget before development starts. Our standard: LCP under 2.5 seconds, CLS under 0.1, INP under 200ms. Every design decision gets tested against this budget. That gorgeous full-screen video background? If it pushes LCP past 3 seconds, it goes. No exceptions.

Preserve What Works

If your current site has a page that converts at 7%, don't redesign it from scratch because "we're redoing everything." Redesign around the elements that drive that conversion rate. Test changes incrementally after launch.

Phase 4: Pre-Launch Checklist

The week before launch is where discipline matters most. Here's our internal checklist, refined over dozens of migrations.

[ ] All 301 redirects tested and verified (automated script, not manual)
[ ] XML sitemap generated and validated
[ ] Google Analytics / GA4 tracking verified on staging (check real-time reports)
[ ] All forms tested (contact, newsletter, booking - submit real test entries)
[ ] robots.txt reviewed (no accidental Disallow: / left from staging)
[ ] Canonical tags present on every page
[ ] Open Graph and Twitter Card meta tags set
[ ] Favicon and Apple touch icons in place
[ ] SSL certificate valid and all pages serving over HTTPS
[ ] No mixed content warnings (HTTP resources loaded on HTTPS pages)
[ ] 404 page designed and functional
[ ] Core Web Vitals passing on mobile (test with PageSpeed Insights)
[ ] Cross-browser testing (Chrome, Firefox, Safari, Edge - and Safari on iOS specifically)
[ ] Cookie consent / GDPR compliance verified
[ ] Backup of old site taken (full database and files)

Phase 5: Launch Day and Beyond

Launch Day Protocol

Deploy during low-traffic hours (Tuesday or Wednesday, 6-7 AM typically works for European businesses)
Submit new sitemap to Google Search Console immediately
Monitor real-time analytics for the first 2 hours - are visits registering? Are conversions tracking?
Test all critical user flows: homepage to contact form, product page to checkout, blog post to newsletter signup
Run a crawl with Screaming Frog against the live site - check for broken links, missing redirects, and unexpected 404s
Check Google Search Console's URL Inspection tool on your top 10 pages - request indexing for each

The First 30 Days

Monitor these metrics weekly:

Indexed pages in GSC - Should stabilize within 2-3 weeks. If the count drops significantly, Google is having trouble with your new structure.
Crawl errors - Some are inevitable. Fix 404s that have traffic or backlinks immediately. Batch the rest.
Organic traffic - Expect a 10-20% dip in weeks 1-2 as Google recrawls. If the dip exceeds 30% or lasts beyond week 3, investigate redirect issues.
Conversion rates - Compare against your baseline. If mobile conversions improved but desktop dropped, you know exactly where to focus.

The "Oh No" Recovery Plan

If organic traffic tanks post-launch, these are the steps in order:

Check robots.txt - is anything blocked that shouldn't be?
Verify redirects are returning 301, not 302 or (worse) 404
Check canonical tags - are pages canonicalizing to the wrong URL?
Review Google Search Console for manual actions or security issues
Compare indexed page count - are pages missing from the index entirely?

In 90% of cases, the problem is one of these five items. We've never encountered a redesign traffic loss that couldn't be diagnosed and reversed within these checks.

The Bottom Line

A website redesign is a high-stakes project, but it doesn't have to be high-risk. The businesses that get hurt are the ones that treat it as purely a design exercise. The ones that thrive treat it as a technical migration with a design layer on top. Document everything, redirect everything, measure everything, and keep your finger on the pulse for 30 days after launch. Do that, and your redesign becomes what it should be - a step forward, not a setback.