What's the honest answer on whether AI Overviews and AI answer engines even care about a site's migration history, or only about current content quality?
AI answer engines carry no migration-history signal. Google's published guidance names no ranking or AI-features factor for platform history, and states that AI Overviews and AI Mode need no additional requirements beyond standard SEO (Google Search Central, September 2026). What a migration changes is current content quality: URLs, redirects, rendered markup and page speed. Fix those four and the history stops mattering.
Where the worry comes from, and why it misreads the mechanism
"Migration history" is not a thing an engine stores about your domain. There is no ledger of platform changes. What exists is an index built from what the crawler fetched most recently, and a ranking layer on top of it. A migration matters to that index only through what it did to the fetched bytes.
So the honest answer deflates most migration-era AI-visibility panic, and then hands back a shorter, harder list.
The four things a migration actually changes
- URLs. If the URL an engine previously cited now 404s or redirects three hops, the citation degrades. Google recommends keeping redirects "for as long as possible, generally at least 1 year" (per Google Search Central, September 2026).
- Rendered markup. Theme JSON-LD does not travel. A Shopify theme emits Product and Article through the native
structured_datafilter (per Shopify developer docs, September 2026); Organization, BreadcrumbList, FAQ and review nodes have to be rewritten into the new theme or they are simply gone. - Content that did not survive the move. Comparison tables, spec blocks and FAQ sections routinely get dropped in a replatform because nobody owned them. Those were the passages being quoted.
- Speed and render path. A page that times out for a crawler is a page with no content.
What the engines say about the transition itself
Google acknowledges the disruption plainly: "With any significant change to a site, you may experience ranking fluctuations while Google recrawls and reindexes your site," and for a medium-sized site "it can take a few weeks or more" before the new URLs replace the old ones (per Google Search Central, September 2026). That is a recrawl story, not a penalty story, and it resolves.
The part nobody can verify, stated as such
No engine publishes a recrawl interval, a citation-decay curve, or any signal named for site history. Anyone presenting a number for how long AI citations take to recover after a replatform is extrapolating. We are not going to do that here.
What to do instead of worrying about history
Audit the current page against the question it should answer: is there a self-contained answer in the first forty to sixty words, does the markup validate, does the URL still match what external sources link to. Those three checks cover everything a migration could plausibly have broken.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: Migration history is not a signal. Current content quality is the whole game, and a replatform is simply a large, fast way to damage current content quality. That reframing changes the remediation plan from reputational repair to a content and markup audit.
- What we’ve seen: The pages that lose AI citations after a Shopify migration are almost always the ones where a structured comparison block or a spec table did not make it into the new template. The homepage and the PDPs come across fine because someone owned them.
- Where we disagree: A common agency pitch treats post-migration AI-visibility loss as evidence that engines distrust the new site. Google's documentation supports the simpler explanation, and the simpler explanation comes with a fix list.
- What this page adds: that there is no history signal to repair, and the four concrete things a migration does break instead.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-13.
Where we worked this out
Our decision records