A Website Redesign and Migration Checklist

Direct answer：A structured checklist to minimize ranking and lead loss during website redesign and migration by defining URL inventory, traffic baselines, content mapping, and rollback criteria.

Pre-Migration Audit

URL Inventory & Traffic Baseline

Export all live URLs with current rankings, organic traffic, and conversions (last 6 months).
*Verification*: Cross-check with Google Search Console and analytics tools for completeness.
*Exception*: Exclude URLs with <5 visits/month unless they drive high-value leads.

Content Mapping

Match old URLs to new URLs (1:1, merge, or retire).
*Criteria*: Preserve or improve topical alignment; avoid orphaned pages.
*Acceptance*: Audit new IA with a crawler (e.g., Screaming Frog) for broken links.

Redirects & Canonicals

301 redirects for all changed URLs; canonicals for duplicate variants.
*Failure Diagnosis*: Test redirect chains (max 1 hop) and validate canonicals post-launch.

Launch Readiness

Analytics & Form Tests

Confirm tracking codes are ported; test form submissions and thank-you page triggers.

Launch Window

Deploy during low-traffic periods; avoid holidays or peak campaign dates.
*Evidence*: Historical traffic patterns from analytics.

Rollback Criteria

*Follow-up*: Compare pre/post-migration crawl reports for indexing errors.

Pre-Migration Documentation and Validation

1. URL Inventory and Traffic Baseline

Inputs: Export all indexed URLs from Google Search Console (GSC), including impressions, clicks, and average position for the last 90 days. Exclude non-indexable pages (e.g., admin paths, staging environments).

Acceptance Check: Verify no high-traffic URLs (>50 monthly clicks) are missing from the inventory. Flag URLs with conversions but low impressions for pre-launch SEO improvements.

2. Content Mapping and Redirect Plan

Steps: Map old URLs to new URLs (1:1 only; avoid combining pages without canonicalization). For discontinued content, identify alternative targets (e.g., parent category) or document intentional 410s.
Decision Criteria: Redirects must preserve topical relevance (e.g., /product-x → /new-product-x, not /blog). Use 301s unless testing temporary changes.
Exception Handling: Pages with dissimilar content but overlapping keywords require a content gap analysis before redirecting.

3. Analytics and Form Validation

Preconditions: Confirm Google Analytics 4 (GA4) filters exclude internal IPs and staging domains. Test all lead gen forms with dummy data pre-launch.

4. Launch Protocol

Execution Window: Deploy during low-traffic hours (e.g., weekends for B2B). Monitor GSC for crawl errors and GA4 for referral anomalies for 14 days.
Verification Item: Check indexed new URLs via site: operator 48 hours post-launch. Missing pages may indicate incorrect robots.txt or meta tags.

Evidence and Quality Gate Definition

Preconditions

URL Inventory: Complete list of existing URLs with traffic data (last 6 months).
Traffic Baseline: Documented organic traffic, conversions, and rankings for key pages.
Content Mapping: Alignment of old URLs to new URLs with priority tiers (T1: high traffic/conversion, T2: moderate, T3: low).

Ordered Checks

Evidence Sources:

Google Analytics: Validate traffic and conversion metrics.
Search Console: Confirm indexing status and search performance.
Crawl Reports: Identify broken links or redirect chains.

Fact vs. Recommendation:

Facts: Data from Analytics, Search Console, or crawl tools.
Recommendations: Inferences (e.g., "redirects may preserve rankings").

Quality Gate:

Acceptance Criteria:
All T1 URLs have 1:1 redirects or equivalent content.
Canonicals point to the correct destination.
Forms and CTAs are tested post-migration.
Exceptions:
Legacy URLs with no traffic can be deprecated.
Low-value pages may be consolidated.

Expected Evidence

Redirect Map: CSV with old URL, new URL, HTTP status (301/302).
Canonical Audit: List of pages with canonical tags and targets.
Form Test Log: Screenshots or recordings of form submissions.

Failure Diagnosis

Ranking Drops: Check redirects, canonicals, and content parity.
Lead Loss: Verify form functionality and CTA placement.

Rollback or Follow-Up

Rollback Plan: Pre-migration backup of content and database.
Follow-Up: Monitor traffic and conversions for 30 days post-launch.

Pre-Launch Verification and Rollback Criteria

Before finalizing the migration, verify the following:

URL Inventory and Traffic Baseline:

Record all existing URLs with their current traffic metrics (sessions, conversions, bounce rates).
Identify high-traffic and high-conversion pages for priority handling.
*Exception*: Exclude URLs with negligible traffic (e.g., <10 visits/month) unless they serve a critical function.

Content Mapping and Redirects:

Map old URLs to new URLs, ensuring 1:1 redirects for high-value pages.
Use 301 redirects for permanent moves and 302 for temporary changes.
*Acceptance Check*: Test redirects using a crawler or manual checks to ensure no 404 errors.

Canonical Tags:

Verify canonical tags point to the correct URL to avoid duplicate content issues.
*Exception*: If consolidating pages, ensure the canonical tag reflects the primary URL.

Analytics and Tracking:

Confirm tracking codes (e.g., Google Analytics, Google Tag Manager) are correctly implemented on the new site.
*Acceptance Check*: Validate data collection in real-time post-launch.

Form and Functionality Tests:

Test all forms (lead gen, contact, etc.) to ensure submissions are recorded and routed correctly.
*Exception*: If forms are rebuilt, verify backend integrations (e.g., CRM, email systems).

Launch Window and Rollback Plan:

Schedule the launch during low-traffic hours to minimize disruption.

*Acceptance Check*: Monitor key metrics for 48 hours post-launch; trigger rollback if thresholds are breached.

Post-Launch Monitoring

Continuously monitor traffic, conversions, and technical errors for at least two weeks.
Use tools like Google Search Console to identify indexing or crawl issues.
*Verification Item*: Cross-check analytics data with pre-migration baselines to confirm recovery.

Pre-Launch Ownership Assignment

Assign clear roles and responsibilities to ensure accountability during the redesign and migration process:

Business Owner: Approves final URL mapping, redirect rules, and launch timing based on lead-generation impact.

*Evidence Field*: Signed-off migration plan with conversion-rate protection clauses

Editorial Owner: Audits content inventory, identifies gaps, and maps old-to-new URLs.

*Evidence Field*: Content matrix with metadata, word count, and conversion rates per page
*Exception*: Pages with <10 visits/month may be consolidated without redirects

Technical Owner: Implements 301 redirects, canonicals, and analytics tracking.

*Evidence Field*: Redirect spreadsheet with HTTP status verification

QA Owner: Tests forms, tracking, and mobile responsiveness.

*Evidence Field*: Test cases covering lead-capture flows on 3 devices

Review Owner: Monitors rankings and traffic for 30 days post-launch.

*Evidence Field*: Weekly organic traffic report comparing pre/post URLs
*Follow-Up*: Priority pages losing rankings get manual indexing requests

Verification Items

Confirm Google Search Console coverage report matches URL inventory
Validate noindex tags aren’t accidentally applied to high-value pages
Check referrer data preserves original UTM parameters in redirects

Limited Rollout Design

Preconditions

URL inventory with traffic baselines (last 90-day averages for organic visits, conversions, bounce rates)
Redirect mapping validated with HTTP status code checks (301 vs 302)
Analytics UTM parameters and form completion goals configured in testing environment

Rollout Steps

Record: Page IDs, baseline metrics, redirect targets

Observation protocol

Minimum 14 days to capture weekly traffic patterns
Hourly monitoring for HTTP 5xx errors
Daily checks for:
Redirect chains >3 hops
Canonical tags pointing to staging URLs
Form submission errors

Threshold triggers

Decision Matrix

Metric：Continue Threshold；Rework Threshold；Stop Threshold

Verification Items

[ ] Search Console coverage report shows no ‘Submitted URL blocked by robots.txt’ errors
[ ] Core Web Vitals (LCP, FID, CLS) within 75th percentile for test pages
[ ] Backlink checks confirm referring domains resolve to new URLs

Pre-Migration Planning

URL Inventory & Traffic Baseline

Export all live URLs with: current traffic (last 90 days), conversion rates, backlinks, and indexed status.
*Verification item*: Confirm Google Search Console and analytics data match.

Content Mapping

Map old URLs to new URLs (1:1, merge, or retire). Flag high-traffic pages for priority redirects.
*Exception*: Pages with backlinks but no traffic may keep URLs or use 301 redirects.

Redirect Strategy

Implement 301 redirects for all retired or merged URLs. Test redirect chains (max 1 hop).
*Acceptance check*: Use Screaming Frog to validate redirects return 200/301 status codes.

Launch Execution

Canonicals & Indexing

Set self-referential canonicals on new pages. Submit updated sitemap to Google Search Console.
*Failure diagnosis*: Check for accidental noindex tags via URL Inspection Tool.

Form & Conversion Testing

Test all lead forms, CTAs, and tracking scripts (e.g., UTM parameters, CRM integrations).
*Rollback criteria*: Forms failing to submit or track conversions in 24h post-launch.

Post-Launch Review

Traffic Monitoring

*Evidence field*: Google Analytics segment for migrated URLs only.

Backlink Audit

Use Ahrefs/Semrush to confirm backlinks resolve to new URLs. Disavow broken spam links.
*Verification item*: Check if lost backlinks affect rankings for target keywords.

Pre-Launch Verification Steps

URL Inventory & Traffic Baseline

[ ] Export all indexed URLs with current rankings, impressions, and conversions (Google Search Console).

*Exception*: Exclude pages with traffic spikes from temporary campaigns.

Content Mapping & Redirects

[ ] Map old URLs to new URLs with 1:1, 1:0 (retire), or 1:many (consolidate) logic.
[ ] Validate redirects with curl -I or Screaming Frog for 301 status codes.
*Exception*: Temporary 302s require a documented sunset date.

Canonicals & Analytics

[ ] Confirm self-referential canonicals on new pages.
[ ] Update Google Analytics filters to exclude staging domains.
*Verification Item*: Test UTM parameter consistency for migrated lead forms.

Rollback Criteria

[ ] Pre-stage DNS revert instructions and backup redirect maps.
*Acceptance*: Full rollback executed within 2h if thresholds breached.

admin