Technical Site Migration
& Domain Change Playbooks
Step-by-step engineering guides for webmasters, SEO engineers, and site architects who need to move fast without breaking rankings.
A site migration is one of the highest-risk operations in web infrastructure. A single misconfigured redirect, a premature DNS flip, or an overlooked canonical tag can wipe out years of accumulated search equity in 72 hours. These playbooks exist to prevent that.
Each guide is written for practitioners — not theorists. Every section contains exact server configs, CLI commands, validation checklists, and rollback protocols you can execute the same day. Whether you are consolidating domains, replatforming a CMS, or restructuring a URL taxonomy, the sequence below will get you through it without surprises.
Start with the auditing playbook to capture your baseline, work through URL mapping to lock in your redirect architecture, then execute the DNS cutover with a tested zero-downtime plan. Every phase links to the next so nothing falls through the cracks.
The library now runs to 88 guides across five sections, covering the whole sequence from a frozen crawl baseline through to the seventy-two-hour soak window after the switch — including the parts that are easy to leave until too late: TLS certificates that must be valid before anything resolves to the new origin, alternate-language annotations that break the moment a hostname changes, and the conversion failures that return a clean 200 while quietly losing money.
This release goes deeper into the handover itself. Search Console ownership is a claim backed by a live token rather than a setting you edit, so a cutover can quietly unverify the property you are about to file a Change of Address from; the sitemap you delete on launch day is the fastest route a crawler has to your redirects; and a rollback is a surgical revert of one rule segment, not an undo of the whole deployment. Each of those now has its own step-by-step guide with the commands to prove the result.
Pre-Migration Auditing
Crawl baselines, risk matrices, traffic mapping, stakeholder gates, and content parity checks before you touch DNS.
Explore playbook →URL Mapping & Redirects
301 vs 302 decision trees, CSV workflows, regex rules, CMS routing, chain elimination, and international hreflang moves.
Explore playbook →DNS & Hosting Cutover
TTL optimization, staging sync, propagation tracking, zero-downtime plans, and TLS certificate cutover.
Explore playbook →Search Console Handover
Property verification, ownership transfer, index-coverage handoff, and sitemap re-submission.
Explore playbook →Rollback Playbooks
Trigger thresholds, DNS and redirect rollback, and the 72-hour post-migration soak window.
Explore playbook →Recently added
New in this release — the steps most often discovered late, when they are expensive:
Transferring Ownership Without Losing History
Hand a property to a new team without unverifying it — add the incoming owner before the outgoing token is withdrawn, and keep sixteen months of data reachable.
Read the guide →Resubmitting Sitemaps After a Domain Change
Why the legacy sitemap must stay live after the move, how to read the processing report, and when the evidence says it is safe to retire.
Read the guide →Rolling Back a Broken Redirect Map
Revert the faulty rule segment rather than the whole deployment, purge caches from the origin outwards, and confirm you did not over-revert.
Read the guide →Validating Redirect Maps Before Deployment
Loops, chains, duplicate sources and rules that match their own output are all detectable offline — four checks that gate the pipeline in seconds.
Read the guide →Deep dives across the whole sequence
Where the newest guides sit in the migration timeline:
Before: Metadata Parity
Titles, canonicals, robots directives and structured data compared between the legacy site and the new build — four of the five are invisible in a browser.
Read the guide →During: Syncing Uploaded Media
Seed, delta-sync, dual-write across the window, then verify byte-for-byte — the phase ordering that makes a media move lossless.
Read the guide →After: Stale Resolver Caches
Traffic still hitting the old origin past the TTL is usually a long-lived process, not a DNS fault — read the decay curve to tell which.
Read the guide →After: Crawled, Not Indexed
One label covers three unrelated situations. Segment the URL list and three cheap measurements settle which one you have.
Read the guide →