The Complete Website Redesign Checklist: Launch Without Losing SEO
Most website redesigns fail to preserve search traffic not because the new design is weak, but because migration happens as an afterthought. Relaunching without a structured inventory turns years of accumulated domain authority into 404 errors overnight.
This checklist is an operational runbook used across our client migrations. It breaks down the redesign process into four sequential phases: pre-design auditing, technical development benchmarks, pre-launch staging verification, and the critical 48-hour post-cutover window.
Phase 1: Discovery, Legacy Audit & Asset Freezing
Before touching wireframes or code, you must record every asset currently driving value on your existing domain. Once the legacy server is decommissioned, recovering lost URL structures or tracking tags becomes exponentially harder.
Phase 2: Architecture & Technical Scope Definition
Determine whether your project requires a full rebuild, a platform migration, or a focused frontend refactor. Avoid changing both your CMS data model and your URL hierarchy simultaneously unless absolutely required.
| Redesign Tier | When to Choose | Primary Migration Risk |
|---|---|---|
| Replatform (e.g., WordPress to API-First / Headless) | When editorial workflows remain useful, but performance, security, and maintenance overhead require architectural change. | Form endpoints, media path rewrites, and dynamic template rendering. |
| Ground-Up Rebuild | When commercial positioning, target audience, and page hierarchy have fundamentally shifted. | High URL churn, metadata loss, and tracking tag discrepancies. |
| Frontend Refactor | When the CMS backend is stable, but mobile responsiveness, Core Web Vitals, and conversion flows need overhaul. | DOM hierarchy shifts and potential layout shifts during script hydration. |
For teams balancing development budgets against architectural choices, our breakdown on website development costs explains how legacy CMS complexity inflates migration fees.
Phase 3: Pre-Launch Staging & Technical Verification
Never approve a redesign based on static Figma designs alone. Staging must run identical server configurations, SSL environments, and populated database content before DNS cutover.
_redirects or server-level rule table. Every legacy page must map directly to its nearest conceptual replacement. Avoid generic wildcards that dump deleted URLs onto the homepage.
noindex, nofollow or HTTP Basic Auth during review, but verify that the production build pipeline strips these restrictions automatically upon cutover.
Organization, Service, BlogPosting) with the Schema Validator to confirm publisher nodes and breadcrumb trails resolve without errors.
Phase 4: Launch Cutover & Critical 48-Hour Protocol
The cutover window requires active real-time monitoring. Treat DNS propagation as a controlled deployment rather than an automated switch.
- DNS TTL Reduction: Drop DNS TTLs to 300 seconds 48 hours prior to cutover to ensure rapid propagation and immediate rollback capability.
- Cutover Execution: Update production DNS records or Cloudflare route triggers. Clear edge caches and verify SSL certificate handshakes.
- Live HTTP Header Check: Immediately run
curl -sI https://yourdomain.comto verify HTTP 200 responses, clean trailing-slash conventions, and active security headers. - Immediate 301 Rule Verification: Test legacy top-tier URLs with automated test scripts to ensure they return clean 301 redirects rather than 404 or 302 temporary redirects.
- Submit Updated XML Sitemap: Request indexation of the new sitemap via Google Search Console and Bing Webmaster Tools.
- Monitor 404 Log Spikes: Review edge server logs or Cloudflare analytics every 4 hours during the first 48 hours to catch unmapped legacy deep links before search bots register them as lost.
Post-Launch Governance
Organic search fluctuations are natural during the first 2 to 4 weeks as search engines recrawl and reindex modified page structures. Compare impressions and click distributions against the baseline inventory established in Phase 1.
To see how our team handles technical architecture and safe production handoffs, review our delivery process or explore our website design and engineering capabilities.