The Migration Checklist That Protects Rankings and AI Citations

A migration that preserves rankings can still torch AI citations, because models re-retrieve on their own schedule and judge the new pages fresh. Treat citation continuity as its own workstream: baseline everything before freeze, verify schema and crawler access on launch day, and re-scan at day 14 with rollback triggers already agreed.

Crawl budget is a money metric

When bots spend their visit on parameter junk and duplicate paths, your revenue pages wait days for a recrawl. Prune, canonicalize, and block the waste; fresh content only matters if it gets fetched.

Core Web Vitals are table stakes

LCP under 2.5 seconds, INP under 200 milliseconds, CLS under 0.1. Miss them and you spot competitors a handicap on every query; hit them and speed disappears as an excuse.

Key takeaways

Migrations fail in the details

Redirect maps get the headlines, but schema parity, crawler access rules, and entity language drift are where visibility actually dies. Baseline everything before freeze and re-verify on launch day, not launch week.

In practice

The practical lesson from migrations is that redirect maps get the headlines while schema parity and crawler access are where visibility actually dies, and AI citations are the most fragile part because models re-retrieve on their own schedule and judge the new pages fresh. We baseline rankings, snippets, and citations before the freeze, validate schema parity on staging and again at cutover, re-verify AI crawler access in both robots and CDN rules, and re-scan at day fourteen and day forty-five with rollback triggers agreed in advance. Treating citation continuity as its own workstream, separate from the redirect plan, is what distinguishes a migration that keeps its history from one that quietly resets it. The details nobody thinks to check are exactly the ones that torch visibility, which is why our migration process is a checklist rather than a redirect spreadsheet.