Web design

Website Redesign Checklist: 40 Steps to Avoid Losing Traffic

A 40-step website redesign checklist focused on preserving traffic during a redesign. Covers redirect maps, content audits, technical checks and post-launch monitoring.

The biggest risk of a website redesign is not the design - it is losing the traffic you already have. A redesign that ignores SEO, URL structure and content preservation can destroy months of ranking work. This 40-step checklist is built around the single goal of preserving and improving your existing traffic throughout the process.

Pre-redesign benchmarking

You cannot protect what you have not measured. Before touching a single line of code, document the current state of every aspect of your website's performance. These benchmarks are your baseline - after the redesign, you compare against them, not against a feeling that traffic 'seems about the same'.

Record total monthly organic traffic from Google Search Console
Export your top 100 landing pages by traffic volume
Record current Core Web Vitals scores (LCP, INP, CLS)
Export current rankings for your 20 most important keywords
Check current conversion rate from organic traffic
Document your backlink profile (total referring domains, top linking pages)
Run a full site crawl with Screaming Frog or equivalent
Identify pages with 404 errors, redirect chains and thin content
Record page speed scores from PageSpeed Insights
Document the current information architecture and URL structure

This benchmarking phase should take 2 to 3 days. Skipping it is the most common mistake in website redesigns. Without a baseline, you have no way to measure whether the redesign improved or damaged your SEO performance.

Redirect map - the biggest failure point

A website redesign almost always changes URLs. Every changed URL needs a 301 redirect from the old URL to the equivalent new URL. This is non-negotiable and is the single most common cause of traffic loss during a redesign. A missing or incorrect 301 means Google loses the connection between the old page's authority and the new page, and the rankings disappear.

Build the redirect map before you build the new site. Map every existing URL to its new equivalent. Group pages by type - products, services, blog, landing pages. If no equivalent new page exists, redirect to the closest category page. Never redirect everything to the homepage, because that tells Google nothing about where the content went.

Test every redirect in a staging environment before deployment. Keep the redirect map as a living document and update it whenever URLs change during the build. Prepare the server-level redirect file in .htaccess or Nginx config format. Have a rollback plan ready if redirects fail on launch day.

The redirect map should be reviewed by someone who understands SEO, not just the developer. A developer maps URLs from a technical perspective. An SEO maps them from a traffic preservation perspective. The difference matters.

Content audit

Not all content on your current site is worth keeping. A systematic content audit helps you decide what to keep, what to improve and what to retire. Every decision should be driven by data, not opinion.

Identify pages in the top 30% of traffic - these are your traffic drivers
Identify pages ranking on page 1 for any keyword - keep and improve these
Identify pages with zero traffic in the last 6 months - consider retiring
Check content quality: does every page meet your current editorial standard?
Update statistics, dates and out-of-date references on pages you keep
Identify pages that should be merged (two thin pages on the same topic)
Plan new content pages that fill topical gaps in current coverage
Migrate blog content with the same or improved formatting on the new site
Check that all internal links on kept pages will work after URL changes

A content audit is time-consuming but essential. It also gives you the opportunity to improve content that was previously underperforming - turning the redesign into a traffic uplift rather than just a visual refresh.

Technical checklist

Set up a staging environment with restricted access (password or IP block)
Install and configure Google Analytics and Search Console on staging
Test all 301 redirects on staging before deployment
Generate a new sitemap.xml that includes only new, live URLs
Update robots.txt to disallow staging and allow production
Check that canonical tags point to the correct new URLs
Test page speed on staging - new designs often add bloat
Ensure mobile responsiveness across all device sizes and orientations
Test structured data (Schema) on all critical page types
Verify that all forms, checkout flows and contact pages work end-to-end
Create a custom 404 page that helps users find what they need
Prepare a monitoring dashboard for the launch week
Test all third-party integrations (analytics, chat, booking, payment)

Launch-day checklist

Deploy the new site during a low-traffic period (late evening or weekend)
Immediately verify that all 301 redirects are working on production
Submit the new sitemap to Google Search Console
Request re-indexing of the homepage and top landing pages
Click-test every link on the homepage, navigation and footer
Verify that all forms submit and emails reach the right inbox
Test payment gateway with a real transaction (then refund it)
Monitor Search Console for an immediate spike in 4xx errors
Monitor real-time analytics for a sudden drop in traffic
Keep the old site available on a subdomain for 30 days as fallback

30-day post-launch monitoring

Compare daily organic traffic against the pre-redesign baseline every week
Watch for ranking drops in your top 20 most valuable keywords
Monitor 404 errors in Search Console daily - fix within 24 hours
Check Core Web Vitals on the new pages to ensure no regression
Review Google's index count - is the new site fully indexed?
Monitor conversion rate - improved design should improve CVR, not harm it
Check backlinks pointing to old URLs - if redirected correctly, authority flows
Watch user behaviour recordings or heatmaps to catch usability issues
After 30 days, compile a comparison report against the baseline
Document lessons learned for the next redesign

A redesign is not finished on launch day. It is finished when traffic and conversions have stabilised at or above the pre-redesign baseline. The 30-day monitoring window is your safety net - do not skip it.

We plan and execute website redesigns that protect your traffic. Talk to us.

Questions

Frequently asked questions

What is the most common mistake in a website redesign?

Not mapping 301 redirects from old URLs to new URLs. Every changed URL without a redirect loses the link equity and ranking history built up over years. This single oversight causes more traffic loss than any other redesign mistake.

How long does a website redesign take?

A typical redesign takes 8 to 16 weeks from kick-off to launch, depending on the size of the site, the amount of new content and the complexity of the design.

Should I redesign my whole site at once or in phases?

A phased redesign is safer for SEO. Redesign the pages that need it most first, measure the impact, then proceed. For smaller sites under 50 pages, a full redesign in one deployment is manageable.

Will I lose traffic after a redesign?

You should not lose traffic if you follow the checklist - benchmark, redirect map, content audit and post-launch monitoring are all essential. The most common cause of traffic loss is broken redirects.

Can I keep my old site live during the redesign?

Yes, the old site stays live until the new site is ready. Keeping a copy on a subdomain for 30 days after launch gives you a reliable fallback if something goes wrong during the cutover.

Keep reading