Every migration checklist tells you what to do. Far fewer tell you how to know whether it worked, and for AI visibility, knowing is genuinely hard: citations churn even in quiet weeks, engines answer from stored snapshots, and the instruments that would tell you the truth only tell it if you set them up before launch. This post is the verification half of the migration problem, the timeline of what to capture, check, and read, before, during, and after. The mechanical half, redirect behavior for AI crawlers, URL mapping, schema and entity migration, lives in the companion checklist, and the two are meant to be run together.
The stakes are the usual migration story with a new chapter; the community threads about post-migration traffic drops now come with an AI subplot, rankings that recovered while citations quietly didn't, or the reverse, and nobody with baselines to say which.
Organic traffic dropped 30% after a site migration. Anyone dealt with this?
T-Minus Four Weeks: Build The Evidence Kit
Everything after launch is interpretation, and interpretation needs a before. Four artifacts, dated and filed where the whole team can find them.
The citation baseline. Run your full tracked query set per engine and save the results, and for the queries that matter most, screenshot the actual answers citing you. The screenshots feel excessive until week three, when someone asks "didn't we use to be in this answer?" and the answer exists as evidence rather than memory. If a weekly tracking loop is already running, this artifact builds itself; export the last month.
The instrument exports. Search Console performance including the AI report, top pages by AI-feature impressions, and analytics by landing page. These are your denominators later.
The crawl-log fortnight. Two weeks of AI crawler activity: which bots, which pages, what cadence, what errors. Post-launch crawl behavior only means something against this rhythm.
The earning-pages inventory. Every URL that currently earns citations, rankings, or meaningful traffic, in one sheet, because this is the list the redirect map must cover perfectly and the list your post-launch checks walk.
A note on the kit's cheapest and most-skipped item: the answer screenshots. Citation trackers record that you were cited; screenshots record what the answer said and where you sat in it, first source or footnote, recommended or merely mentioned. After a migration, "we're still cited" and "we're still the recommendation" can diverge, and only the screenshots let you notice.
One more pre-launch act: write the rollback gates now, numbers and durations, and get them agreed. Gates written before launch are engineering; gates improvised at week two are politics.
200+ SaaS teams already track their AI citations.
They know exactly when ChatGPT mentions their brand, and when it stops. Do you?
Launch Day: Verify Like A Machine
The team will check the site with human eyes; your job is the machine's eyes, within hours of cutover.
Raw HTML at the new URLs. Curl the top twenty earning pages and confirm the content, the answer-first openings especially, is present in the raw response. Rendering regressions are the classic silent migration failure, invisible in a browser, total for fetchers that don't run JavaScript.
Redirects, with hop counts. Spot-check old URLs from the inventory, confirming they land on the right new pages, and count the hops, because AI crawlers tolerate shorter chains than Googlebot. One hop is the standard; chains are debt.
The access layer survived. Robots.txt, bot-protection rules, and any allowlists, re-verified on the new infrastructure, since fresh deploys love to ship default-deny security settings that quietly 403 every crawler you spent a year admitting.
First bot arrivals. Watch the logs for the first AI crawler visits to the new structure and confirm they're receiving 200s. The crawlers arriving and succeeding is the first genuine signal the machine world has accepted the move.
The Special Cases
Three migration flavors bend the timeline enough to deserve their own notes.
Domain changes. The hardest case for AI visibility, because entity trust is partly domain-anchored: engines have learned that your brand lives at the old address, and the corroboration layer, directories, reviews, mentions, still points there. Extend the timeline's expectations by a month, update the third-party layer aggressively in launch week (directories, review profiles, social bios, the canonical self-description everywhere), and expect the stored-snapshot phase to run longest here. The old domain must redirect for years, and its registration should be treated as permanent infrastructure.
CMS or platform swaps with same URLs. The friendliest case on paper, and the one with the sneakiest failure: rendering. Same URLs, new templates, and suddenly the pricing table is client-side or the FAQ block renders differently. The launch-day curl pass matters most here, and the evidence kit's page inventory should include a saved copy of each earning page's raw HTML for diffing.
Consolidations and redesigns that prune pages. Every removed URL that earned citations needs an explicit decision, redirect to the best successor, or accept the loss on purpose, recorded in the inventory. The post-launch reading then checks whether successor pages inherited the citations, which happens more often than skeptics expect and less often than optimists do, and the delta is your consolidation quality score.
How often does ChatGPT mention your brand?
Most founders have no idea. The answer might surprise you.
Weeks One And Two: Read Churn Like An Adult
Now the hard part: the readings will move, and most movement is noise. Citation sets rotate substantially week to week in the calmest of times, so single-week drops prove nothing, and this is where teams without controls talk themselves into either panic or false comfort.
Three controls make the readings honest. Cohort against unchanged queries: if some tracked queries' pages migrated and others didn't, their divergence is your cleanest damage signal. Use competitors as weather stations: if your share fell while the same rivals hold their citations across your query set, that's you, not the weather. Join citations to crawl logs: damage almost always leaves a mechanical trail, bots hitting errors, old URLs still being fetched, coverage of key pages lapsing, so a citation dip with clean logs is probably churn, and a citation dip with dirty logs is a work ticket with an address on it.
Expect one genuinely confusing phenomenon: engines citing your old URLs from stored snapshots for a while after launch. It's why the redirects from the old addresses must work forever, never for a "transition period," and why traffic arriving via old URLs post-launch is a sign the system is working, not failing.
Months One And Two: The Recovery Reading
The month-scale question is whether the trend line re-converges on the baseline, and the layers move on different clocks: Google's surfaces re-settle first as recrawls propagate, AI engines follow their crawlers' revisit cadence, and the stored-snapshot layer refreshes last. A realistic recovery curve dips, wobbles, and returns over four to eight weeks; the pattern that warrants escalation is the flatline, week after week below baseline with no slope, especially on the queries whose pages you know migrated cleanly.
Set the reporting rhythm now too: one short weekly note to stakeholders, three lines, citation share versus baseline, crawl health, anything escalated, because the alternative is ad-hoc screenshots in executive threads, and ad-hoc screenshots during a migration recovery are how organizations convince themselves of things that aren't happening.
At week six, run the formal comparison: citation share per engine against the baseline kit, AI-report impressions against the export, crawl coverage against the fortnight rhythm. Three outcomes, three actions. Converged: write the retro, keep the kit as the next migration's template. Partially converged: the gap names its own investigation, since you can now say precisely which queries, engines, and pages didn't come back, and chase those redirects, renders, or consolidation decisions specifically. Flatlined below the gates you wrote at T-minus-four: that's the conversation the gates exist for, held with evidence instead of adrenaline.
The One-Page Timeline
For the project doc: T-4 weeks, evidence kit built, rollback gates written, companion checklist's mechanical work underway. T-1 week, kit refreshed, inventory frozen, redirect map reviewed against it. Launch day, machine-eye verification within hours, curl, redirects, access, first bots. Weeks 1-2, weekly citation checks read with controls, logs joined to every anomaly, no strategic conclusions drawn. Weeks 3-8, trend versus baseline, escalate flatlines, celebrate convergence quietly. Forever, old redirects stay live, and the kit gets archived where the next migration's team will actually find it.
Two closing habits separate teams that migrate well twice from teams that relearn everything. First, the kit outlives the project: archive it with the retro, because your next migration inherits its template, and your next quarter's odd citation dip gets diagnosed faster with a known-good baseline on file. Second, fold the migration queries back into the standing weekly loop rather than retiring them, since the pages that just moved are precisely the ones whose next six months of citation behavior you most want on a chart.
Migrations don't have to cost you the answers you've earned. They cost the teams who couldn't tell what changed, which is a different and fixable problem. The whole discipline above compresses to one sentence: capture the before, verify like a machine, and read the after with controls, so that every surprise the migration produces arrives with an address attached instead of a mystery attached.
15 hours a week manually. Or 15 minutes with RankControl.
Track citations, monitor competitors, and fix content gaps across every AI search engine. Automatically.
