Technical SEO Specialist Pre-Launch Migration Checklist

Role: Senior Technical SEO Architect specializing in enterprise SaaS platform migrations and infrastructure overhauls.

Context

• Source domain: {{source_domain}}
• Target infrastructure: {{target_architecture}}
• CMS and rendering setup: {{cms_framework}}
• Staging environment: {{staging_url}}
• Critical URL inventory size: {{critical_url_count}}
• Redirect mapping repository: {{redirect_mapping_sheet}}

Task

Generate an exhaustive, phase-by-phase technical SEO pre-launch migration checklist that enables engineering and growth teams to validate crawlability, redirect fidelity, and indexation integrity before cutover.

Method

1. Review the staging environment on {{staging_url}} to identify potential rendering or JavaScript hydration indexing blockers.
2. Inspect redirect rules within {{redirect_mapping_sheet}} against the {{critical_url_count}} high-priority URLs from {{source_domain}}.
3. Validate canonical tag logic across {{target_architecture}} to prevent circular or self-referential canonical errors.
4. Check robots.txt directives and XML sitemap generation scripts within {{cms_framework}} for accidental indexation locks.
5. Audit internal linking patterns, breadcrumb structures, and navigation menus on the staging environment.
6. Evaluate status code responses for internationalization, trailing slashes, and protocol parameters.
7. Formulate explicit pass/fail acceptance criteria and ownership assignments for every checklist item.

Constraints

• MUST format all verification steps as actionable checklist items with checkboxes ([ ]).
• MUST categorize items into DNS/Headers, Crawl/Render, URL Mapping, and Meta Directive phases.
• MUST NOT recommend generic advice without tying it directly to {{cms_framework}} and {{target_architecture}}.
• Keep technical notes concise and scoped strictly to pre-launch verification.

Output format

A markdown document containing four sequential checklist phases. Each phase must include 4 to 6 discrete checkbox items with assigned owner role, priority tier (P0/P1/P2), and pass criteria.

Self-review

• Confirm all 6 variables are referenced in the checklist logic.
• Verify every checklist item has a definitive pass/fail verification standard.
• Ensure no post-migration steps dilute the pre-launch scope.