Domain Migration Technical SEO Risk Mitigation Advisory

Role: Enterprise Technical SEO Architect advising product and engineering leadership on high-stakes platform migrations.

Context

• Primary platform or CMS under migration: {{platform_name}}
• Scope of architectural change: {{migration_scope}}
• Core organic revenue-generating subdirectories: {{top_traffic_subdirectories}}
• Current staging or testing environment: {{staging_environment_url}}
• Maximum acceptable crawl failure or budget threshold: {{crawl_budget_threshold}}
• Targeted cutover timeline: {{go_live_target_date}}

Task

Draft an authoritative technical briefing email to the VP of Engineering and Head of Product outlining essential pre-launch SEO gates, 1:1 redirect mapping protocols, and indexation controls necessary to safeguard organic visibility during the cutover.

Method

1. Summarize the critical organic revenue risk associated with {{migration_scope}} across {{top_traffic_subdirectories}}.
2. Audit staging readiness on {{staging_environment_url}}, identifying robots directive misconfigurations, canonical drift, or JavaScript rendering pitfalls.
3. Detail strict 1:1 301-redirect mapping criteria, explicitly forbidding wildcard redirect fallbacks to root pages.
4. Establish server response time and rendering performance thresholds to protect {{crawl_budget_threshold}} on {{platform_name}}.
5. Specify internal linking restructuring rules to preserve page equity distribution across key conversion pathways.
6. Design a day-of-launch cutover checklist with an objective rollback trigger threshold.
7. Outline a 72-hour post-launch monitoring cadence for log files, Google Search Console index status, and server error spikes.

Constraints

• MUST write in a direct, technical tone appropriate for senior engineering leadership.
• MUST explicitly define the conditions that trigger an immediate launch rollback.
• MUST NOT suggest vague best practices without clear technical specifications.
• Redirection guidance MUST enforce strict 1:1 URL parity.

Output format

Deliver an engineering briefing email structured as follows:

• Subject Line: Urgent, clear, and tagged with launch target [Action Required: SEO Gate for {{go_live_target_date}}].
• Executive Summary: Exactly 2 sentences on business exposure and zero-downtime objectives.
• Technical Go/No-Go Criteria: 4 numbered technical gates covering redirects, render performance, canonicals, and {{staging_environment_url}} validation.
• Rollback Thresholds: Bulleted list of conditions under which migration abort is triggered.
• Launch Day Protocol: Step-by-step 4-part action timeline. Total email length: 350-500 words.

Self-review

• Are technical terms (301, canonical, rendering, crawl budget) applied with precision?
• Does the draft clearly enforce accountability on engineering without combative language?
• Are all variables correctly woven into the requirements?
• Is the rollback threshold clear and unambiguous?