Document old and new domains, subdomains, and affected systems.
- Document old and new domains, subdomains, and affected systems1 cited source1 category
Save for later 0
Use × to move an item here. You can restore it when you’re ready.
Your checks and saved items stay in this browser. Nothing is submitted.
Why this matters
Defining the full scope prevents unexpected issues and mid-launch scope creep.
Hypothetical standard operating procedure
Adapt this example to your site, access, tools, and change process. It is our suggested procedure, informed by the sources below.
- List current domains and subdomains involved in migration.
- Inventory all systems referencing the domain, including marketing and analytics.
- Record whether URL structures will change alongside the domain.
- Freeze non-essential content changes until migration stabilizes.
- Assign a migration launch owner responsible for decisions.
Watch for
Incomplete scope leads to missed redirects and broken integrations.
Definition of done
A documented list of old/new domains, subdomains, CMS, analytics, ads, email, CRM, forms, payment tools, CDN, and social profiles.
Sources & attribution
Original checklist wording and example SOP by Best SEO Checklist, using source-grounded AI assistance. Editorial contact: Ted Kubaitis, @tedkubaitis on Teams. Check current source guidance before implementation.