Home / Blog / Technical SEO
Technical SEO

The Migration Checklist That Protects Rankings and AI Citations

Redirect maps get the headlines, but schema parity and crawler access are where visibility actually dies.

March 11, 2026 · 6 min read · AEO GEO Hourly Editorial

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

Baseline rankings, snippets, and citations before freeze
Schema parity validated on staging, again at cutover
AI crawler access re-verified in robots and CDN rules
Day 14 and day 45 re-scans with rollback triggers

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.

Want this implemented for you?

This exact method ships inside our client engagements at $45/hr, estimate in writing first.

Start a Project

Keep Reading