Website Redesign SEO Checklist (No Traffic Loss)

Three weeks after launch, organic traffic is down 42 percent. Rankings for your money keywords have slipped to page two. The redesign was supposed to grow traffic, not torch it. This is what happens when SEO is treated as a launch task rather than a redesign discipline.

The Three Migration Failure Modes

Most post-redesign traffic drops come from one of three root causes. In the worst cases, all three happen simultaneously.

Broken redirects. Old URLs either return 404 errors or redirect to the wrong destination. Google’s indexed URLs return nothing useful. Any link equity built over years evaporates.

Lost content depth. The redesign merged or deleted pages that ranked individually. A “services overview” page replaces six individual service pages. Each of those pages had rankings and backlinks that are now orphaned.

Technical SEO regression. The new build renders pages differently, blocks crawlers in robots.txt, ships without canonical tags, or loses structured data. Sometimes the staging environment’s noindex directive gets pushed to production.

All three are preventable. None of them require deep technical knowledge. They require a checklist completed at the right stages.

The Pre-Launch SEO Checklist

Complete these before the new site goes anywhere near a production domain.

Crawl audit (do this first):

Crawl the existing site with Screaming Frog or Sitebulb
Export all indexed URLs (use Search Console > Pages for the definitive list)
Identify which URLs rank and drive traffic (Search Console > Search Results, filter by landing page)
Identify URLs with backlinks (Ahrefs or Google Search Console > Links)

URL mapping:

Map every current URL to its new equivalent
Flag URLs being merged, deleted, or restructured
Confirm each mapped URL has a 301 redirect configured
Test redirects on staging before launch

Content audit:

Confirm all ranking pages are preserved or redirected to equivalent content
Check that merged pages retain at least equivalent content depth to the best original
Verify meta titles and descriptions are present on all pages
Confirm H1 tags are present and correct on all pages

Technical checks on staging:

Robots.txt allows crawling (check staging doesn’t have Disallow: /)
Canonical tags point to the correct production URLs
Schema markup is present and validates in Google’s Rich Results Test
XML sitemap is present and lists all intended pages
HTTPS is configured and all internal links use https://
Page speed baseline measured (Lighthouse on key pages)

The Launch Day Playbook

The day of DNS transfer is the riskiest window. Complete these in order.

Immediately after DNS propagation:

Verify SSL certificate is active and serving correctly
Smoke test all critical pages (homepage, top five landing pages, contact)
Verify redirects from old URLs are firing correctly (use a 301 checker tool)
Check robots.txt is allowing crawl on production
Verify canonical tags point to correct URLs

Within two hours of launch:

Submit updated XML sitemap in Google Search Console
Request re-indexing of homepage and top five landing pages via URL Inspection
Submit sitemap in Bing Webmaster Tools
Verify Search Console is no longer showing staging domain

Within 24 hours:

Check for crawl errors in Search Console (Coverage report)
Verify analytics tracking is firing correctly
Test all forms are submitting and delivering notifications
Check all conversion events in GA4

The 30 Day Post-Launch Monitoring Routine

Traffic changes after a redesign are normal for 30 to 60 days. Google recrawls, re-evaluates, and redistributes rankings. Some fluctuation is expected. What you are watching for is sustained decline or specific page-level drops.

Daily for the first week:

Check Search Console > Coverage for new 404 errors
Check Search Console > Performance for significant impression drops on top queries
Monitor for any crawl anomalies

Weekly for four weeks:

Compare organic sessions week over week and year over year
Run a rank tracking check on your top 20 keywords
Review Search Console > Links for any unexpected reference changes
Check for any new manual actions in Search Console

Warning signs that need immediate attention:

404 errors on previously ranking URLs (redirect is missing or broken)
Sitemap showing submitted URLs not indexed (blocking or canonical issue)
Significant impression loss on branded queries (something is serving noindex)
Crawl budget being wasted on duplicate URLs (canonical issue)

When and How to Roll Back Partial Changes

Full rollbacks are rarely needed if you catch problems within the first week. Partial rollbacks are more common.

Safe to undo quickly: noindex tags added in error, robots.txt changes, meta changes, canonical updates.

Harder to undo: URL changes that have already been recrawled and deindexed, content merges where the original is no longer live.

The trigger for escalation: if any high-value page loses more than 50 percent of its impressions within 14 days and you cannot identify a clear cause, escalate. Check whether the page is still indexed by searching site:yourdomain.com/page-url. If it has dropped from the index, check for noindex, canonical issues, or crawl blocking.

A Migration That Went Well

A UK professional services firm migrated 142 URLs from an aged WordPress site to a new Astro build. By running the pre-launch checklist above, mapping all 142 URLs to their new equivalents, and completing a staged redirect implementation, the migration achieved zero percent organic traffic loss in the 90 days following launch. Rankings on key service-line terms actually improved in week six, because the new site scored 91 on mobile PageSpeed Insights versus 34 on the old site.

The checklist was not glamorous work. The outcome was.

If you are mid-redesign or planning one and want a second opinion on your SEO handover plan, book a migration scoping call. We run this process on every web development and web design project we take on, and we can review your redirect map or crawl export directly.