A site migration is any change to a website's URLs, hosting platform, template, or content management system: a domain move, a replatform from a legacy CMS to a headless one, a full visual redesign, or a simple HTTPS and www consolidation. Every migration playbook written for traditional SEO focuses on the same goal, preserving rankings and link equity through the transition. In 2026 that goal is no longer sufficient on its own, because a migration is now also judged on whether ChatGPT, Perplexity, Google AI Overviews, and Claude keep citing the site afterwards, and that risk barely appears in most existing migration checklists.
The two failure modes are not the same. A page can retain most of its Google ranking after a botched migration and still disappear from AI answers entirely, because the signals that drive AI citation, structured data, crawler access, and a stable canonical URL, are more fragile than the ranking signals a conventional 301-redirect audit is built to catch. A migration that a traditional SEO tool marks as clean can still be an AI citation disaster.
Why migrations are a bigger risk for AI citation than for search rankings
Google's ranking algorithm has decades of tolerance built in for messy migrations: it follows redirect chains, reconciles near-duplicate URLs, and gradually re-crawls a site even when things go wrong. AI crawlers such as GPTBot, ClaudeBot, and PerplexityBot are comparatively unforgiving. Several of them fetch a page once, cache the result for a training or retrieval index, and do not retry aggressively if that fetch fails or the content changes shape. If a migration breaks a redirect, strips schema, or serves a JavaScript shell instead of rendered HTML during the exact window an AI crawler visits, the citation loss can be immediate and does not necessarily recover on the crawler's next pass the way a Google ranking eventually would.
AI citation loss from a migration is often invisible in the tools teams already watch. Google Search Console shows ranking and indexing status, not whether ChatGPT or Perplexity still cite a page. A migration can look completely clean in Search Console while AI citations quietly drop to zero.
What actually breaks AI citation during a migration
Missing or chained 301 redirects
If old URLs return a 404 instead of redirecting, AI systems that rely on retrieval, rather than pure training-time memory, gradually stop including that content in answers because the source no longer resolves. A redirect chain of three or four hops has the same effect on several AI crawlers as a broken link, since some do not follow every hop the way Googlebot does. Every migrated URL needs a single, direct 301 to its new location, not a chain and not a soft 404 that returns a 200 status with an error page.
Schema markup lost in the rebuild
A visual redesign or CMS replatform frequently drops structured data entirely, because the JSON-LD templating logic lived in the old theme or plugin and nobody rebuilt it for the new one. FAQPage, Organization, Article, and Product schema are exactly the machine-readable signals AI retrieval systems lean on most, so losing them in a redesign removes a large share of what made a page citable in the first place, even though the visible page content looks unchanged to a human reviewer.
Crawler access misconfigured on the new environment
New hosting environments, staging-to-production cutovers, and new CDN or WAF configurations regularly introduce accidental blocks on GPTBot, ClaudeBot, and PerplexityBot that were never present on the old setup, either through a stale robots.txt copied from staging or a bot-management rule that treats AI crawlers as unwanted traffic by default. This is one of the most common and most silent migration failures, because the site itself loads fine for a human visitor while the AI crawler is quietly refused.
URL structure changes that sever internal link equity
Flattening a folder structure, renaming slugs for a cleaner URL scheme, or moving a subdirectory to a subdomain all change how the internal link graph resolves. AI crawlers use that graph as a topic and trust signal in roughly the same way search engines do, and restructuring it without care breaks the pillar-and-cluster relationships a site may have spent months building.
The pre-migration AEO checklist
Before a redesign or replatform goes live, confirm the following against the current, pre-migration site so there is a known-good baseline to test the new environment against:
- Export a full URL list with current schema types, so the new build can be checked page by page against what existed before
- Confirm the new CMS or template can output the same JSON-LD schema types, ideally rendered server-side rather than injected client-side
- Draft the full redirect map before development starts, one row per old URL, not a set of generic pattern rules that may not cover every edge case
- Test the staging environment's robots.txt and any WAF or bot-management rules explicitly against GPTBot, ClaudeBot, PerplexityBot, Googlebot-Extended, and Applebot-Extended user agents
- Verify the staging build renders full content in the raw HTML response, not only after client-side JavaScript executes
- Record baseline AI citation status for a sample of important pages by running real prompts against ChatGPT, Perplexity, and Google AI Mode before the migration, so post-launch testing has something to compare against
What to do in the first 30 days after launch
- Spot-check the redirect map on a sample of high-value URLs immediately after cutover, not just the pattern rules but individual pages, since pattern-based redirects frequently miss edge cases
- Pull server logs for GPTBot, ClaudeBot, and PerplexityBot activity daily for the first two weeks to confirm crawlers are actually fetching the new URLs and getting 200 responses
- Re-run the pre-migration prompt tests against ChatGPT, Perplexity, and Google AI Mode weekly, watching for citations that disappear rather than waiting for a monthly review cycle to catch it
- Validate JSON-LD on every major template type with a schema testing tool, not just the homepage, since template-level schema bugs usually affect every page of that type at once
- Monitor AI referral traffic in analytics for a sudden drop rather than a gradual one, which is the signature of a crawler access or redirect failure rather than a normal ranking fluctuation
Keep the old redirect map live for at least six months after a migration, even after everything appears stable. AI training-time knowledge can reference old URLs well after a migration, and a live redirect is the only way that stale reference still resolves to current content instead of a dead link.
How to verify AI citation actually survived the move
The only reliable verification is running the same prompts against the same AI systems before and after the migration and comparing the results directly, rather than inferring citation health from ranking or indexing data. Google Search Console's AI performance reports and GA4's AI referral channel both help with volume trends, but neither confirms that a specific page is still the one being cited for a specific query. Manual prompt testing, repeated on a fixed schedule through the weeks after launch, is the only method that answers that question directly.
When training-time knowledge complicates recovery
Some AI systems answer from parametric, training-time knowledge rather than a live retrieval lookup for a given query, which means a migration can surface a strange, delayed failure mode: the model keeps citing or referencing the old URL structure or old page content for months after the migration, simply because that is what it learned during training and it has not yet been retrained on the new site. This is not something a redirect can fully fix on its own, since a model answering from memory is not necessarily following the link at all. The practical response is the same as for any other stale training-time fact: keep the redirect live indefinitely, keep the on-site content current and internally consistent, and treat the gap as something that closes gradually across future training cycles rather than something a single technical fix resolves immediately.
Run a free CiteRank audit on key pages both before and after a planned migration. Comparing the schema, crawler-access, and citation-worthiness scores from the two audits is a fast way to catch what a redesign silently broke before it costs months of AI visibility. If you have not settled on which audit tool to standardise on for this, our list of AEO checking tools compares the options.
A realistic recovery timeline
If redirects, schema, and crawler access are all handled correctly at launch, AI citation should carry across the migration with minimal disruption, since the underlying content has not changed and the technical signals AI systems rely on are preserved. Recovery from a genuinely broken migration is slower and less predictable: retrieval-based citation can return within weeks of fixing the underlying issue once crawlers re-fetch corrected pages, but any training-time reference to the old site can persist for months until it is superseded in a future model update. This asymmetry is the strongest argument for treating AI citation as a pre-launch checklist item rather than a post-launch recovery project.