Migration playbook
Domain migration with SEO equity preservation
A guide for sites migrating between domains. Done right, equity transfer is near-complete within 60-90 days. Done wrong, you lose 30-60% of organic visibility for months. The difference is mostly redirect discipline and Search Console transition.
Pre-flight
Before kickoff
- Both domains verified in Google Search Console and Bing Webmaster Tools.
- Full URL inventory of the source domain with traffic and link equity data.
- Decision: full structural mirror (recommended) or restructure-while-migrating (riskier).
- Outreach plan for top 50-100 backlinks — link updates accelerate equity transfer.
- Communication plan for users (email, in-app, banner).
If things break
Rollback plan
- Within first 7 days: revert DNS, remove Change of Address. Equity loss minimal.
- After 14 days: rollback gets harder; consider proceeding and recovering rather than reverting.
- Keep the old domain registered and accessible for at least 12 months.
Steps
Sequenced execution
Step 1
Mirror the structure on the new domain
Deploy the new domain with the exact same URL structure as the old, content-identical. Stage and verify.
Step 2
Configure 301 redirects from old to new
One-to-one URL mapping. No chains. Test 100+ URLs with curl -I. Verify 301 status and correct destination.
Step 3
Update canonicals on both domains
Old domain canonicals point to new. New domain canonicals point to itself. Avoid cross-domain canonical loops.
Step 4
Submit Change of Address in Search Console
In the old domain property: Settings → Change of Address. Verify new domain ownership first.
Step 5
Update internal references everywhere
Email signatures, product links, social media, ad campaigns, partner integrations. Stale references slow equity transfer.
Step 6
Reach out to top backlinks
For top 50-100 backlinks (by Domain Rating × relevance), email asking for link updates. Even 30% success rate accelerates recovery.
Expected metrics
Concrete expectations
- Expected downtime
- < 5 min (DNS TTL-bound)
- Typical rollback window
- < 7 days for low equity loss
- Time to equity transfer
- 60-90 days
- Acceptable temporary visibility drop
- 10-30% in first 14-30 days
After cutover
Monitoring discipline
- Search Console performance on both old and new properties — track combined impressions and clicks.
- Old-domain crawl frequency — should drop steadily as Google understands the move.
- New-domain indexation count — should rise to match old-domain baseline within 60-90 days.
- Backlink profile (Ahrefs / Majestic) — track updated vs still-pointing-old.
- Brand search query volume — should not change significantly during the move.
FAQ
Common questions
Do I need to keep the old domain registered?
Yes, for at least 12 months — long enough for redirect equity to fully transfer, and to prevent abandonment-and-squat scenarios. Many teams keep it renewed in perpetuity as a brand defensive asset.
Does the Change of Address tool actually do anything?
Yes — it accelerates Google's consolidation of the two domains in their index. Submit it in Search Console as soon as 301 redirects are confirmed live. Without it, full equity transfer can take 30-60% longer.
What is the single biggest mistake teams make?
Chain redirects (`old.com/a` → `new.com/a` → `new.com/b`) or redirect to homepage instead of mapped page. Both bleed equity. Every old URL needs a direct 301 to its exact new-domain counterpart.
When should I avoid a domain migration?
During seasonally peak traffic, while ranking volatility is high, or within 60 days before a planned algorithm-sensitive release. Migrate during stable periods and avoid stacking multiple major changes.
Last updated:
Get this scoped to your stack
Generic playbooks are useful for orientation; the actual migration plan needs your routes, your CMS, your team capacity. The scoping call is 30 minutes — bring the constraints.
Other migration guides
SSR to SSG migration on Next.js
Move from server-rendered Next.js to fully static generation without losing SEO equity, with sane fallbacks for content that still needs freshness.
SPA to prerendered architecture
Add a prerendering layer to a client-rendered SPA without rewriting it. The compromise that buys crawler reach without an SSR rebuild.
WordPress to headless CMS migration
Move from monolithic WordPress to a headless setup (WP-as-CMS + JS frontend, or full migration to Sanity/Contentful) without losing the SEO baseline.