Most post-redesign traffic collapses trace back to work that was skipped in the last two weeks before launch. This checklist is the discipline that prevents them — organized by phase, with the non-negotiables marked clearly.
Before design starts: snapshot everything
Crawl the entire current site and archive it: every URL, title, meta description, heading structure, and word count. Export twelve months of Search Console data — queries, pages, positions — and rank every URL by organic entrances and conversions. This baseline is what "success" will be measured against, and what "we lost something" gets diagnosed with.
Identify your equity pages now: the URLs holding rankings, links, or conversion volume. These get explicit protection plans. A redesign that improves the homepage but breaks three money pages is a net loss nobody notices until the quarterly review.
During design: architecture is an SEO decision
Information architecture determines internal link flow, crawl depth, and topical grouping. Review the proposed sitemap against your keyword clusters: does every commercial intent still have a page? Are equity pages surviving, merging, or dying — and if merging, where does each one’s intent go?
Challenge content reduction early. Designers reasonably want cleaner pages; ranking pages often rank because of content the redesign wants to cut. The compromise is usually structural — tabs, accordions, progressive disclosure — rather than deletion. Content that ranks must survive in crawlable form.
Treat a missing redirect map the way you’d treat missing DNS records — the site is not ready to launch.
The redirect map is a launch-blocking deliverable
Every old URL needs a destination: itself (unchanged), a 301 to its successor, or a deliberate 410. Map one-to-one wherever possible — redirecting everything to the homepage tells Google those pages’ equity is gone and their relevance signals discarded.
Test the map on staging with a crawler before launch: no chains, no loops, no redirects to 404s. This file is the single highest-leverage document in the entire project. Treat a missing redirect map the way you’d treat missing DNS records.
Launch week: verify, don’t assume
Within hours of launch: crawl the new site fully, confirm robots.txt isn’t blocking (staging noindex tags shipping to production is a classic), submit the new XML sitemap, and spot-check the top 50 equity pages by hand — status codes, titles, canonicals, content presence, schema validity.
Check rendering too: if the new stack leans on client-side JavaScript, verify Google actually sees the content with the URL Inspection tool. A page that renders beautifully for users and empty for Googlebot is a redesign failure with a delay timer.
Post-launch: monitor with rollback triggers
Watch Search Console daily for two weeks: indexing coverage, ranking movement on your equity list, and crawl errors. Some volatility is normal for a few weeks; a 30% visibility drop on money pages is not — it’s a signal to diff those pages against your pre-launch snapshot and fix what changed.
Agree on rollback triggers before launch, not during the argument: which metric drop, sustained how long, forces which remediation. Teams with predefined triggers fix regressions in days; teams without them debate causes for a quarter.
The useful takeaway
Snapshot before, protect equity pages during, treat the redirect map as launch-blocking, verify everything at launch, and monitor against predefined rollback triggers. Redesigns lose traffic through skipped process, not bad luck.
