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?

Do AI answer engines keep a record of a site's migration history?

No: AI answer engines keep no documented record of a site's migration history; what their documentation describes is an index built from what their crawlers fetch. Google describes a site move as URL-by-URL work: "The move takes place on a per-URL basis", and 301 redirects "don't cause a loss in PageRank" (Google Search Central, October 2026). Google's AI features then draw on that index through its core ranking systems (Google's generative AI guide, October 2026), which is why AI answers still lean on traditional search signals. OpenAI's crawler documentation covers access and robots.txt, not site history (OpenAI's crawler page, October 2026).

So a migration matters to an engine only through what it did to the pages the crawler fetches.

What does a migration actually change for AI engines?

A migration changes four things AI engines read: the URLs, the rendered markup, the content that survived the move, and the render path.

1. URLs. If a URL an engine cited now returns a 404 or sits behind a chain of redirects, the citation degrades, in our reading. Google recommends keeping redirects "for as long as possible, generally at least 1 year" (Google Search Central, October 2026). Why AI citations can fall while Google rankings hold covers the redirect map.
2. Rendered markup. Theme markup does not travel. Shopify's structured_data Liquid filter outputs Product, or ProductGroup when a product has variants, and Article (Shopify developer docs, October 2026). Organization, BreadcrumbList and review nodes have to be rebuilt in the new theme, work Deploi's structured data decision record scores BUILD.
3. Content that did not survive the move. In our experience, comparison tables, spec blocks and FAQ sections get dropped in a replatform because nobody owned them, and in our judgment those are often the passages engines quoted.
4. Speed and render path. A page that times out for a crawler is a page with no content, so it cannot meet Google's bar of an indexed page that is "eligible to be shown in Google Search with a snippet" (Google's generative AI guide, October 2026).

What does Google say happens to a site during a move?

Google says a site move brings temporary ranking fluctuation that settles over time. Its site-move guide warns: "With any significant change to a site, you may experience ranking fluctuations while Google recrawls and reindexes your site" (Google Search Central, October 2026). For a medium-sized site, "it can take a few weeks or more" before the new URLs replace the old ones. Google adds: "This is normal and a site's rankings will settle down over time." That is a recrawl story, not a penalty story, so it resolves once the crawler has been through. Search Console's Generative AI performance report, on every site by 31 August 2026, shows the AI Overviews and AI Mode side of that recovery by page (Search Console Help, October 2026).

Which claims about migration history can nobody verify?

Three claims about migration history cannot be verified, because neither Google nor OpenAI publishes the data behind them.

• A history or trust signal. Neither Google's site-move guide nor OpenAI's crawler documentation names one, so there is nothing to repair.
• A recrawl date for your URLs. Google says "There are no fixed crawl frequencies" (Google Search Central, October 2026).
• A recovery date for your citations. The one published set of recovery medians we found comes from AI-visibility vendor MaxAEO and covers 38 migrations by business software and tech brands, not Shopify stores (MaxAEO, August 2026). That is why the citation-drop answer treats it as a range to test, not a forecast.

Anyone presenting a recovery date for your replatform is extrapolating.

What should you audit instead of worrying about history?

Audit each high-value page as it stands today, because that is what engines read. The four checks match the four things a migration breaks:

• Redirect. Does the old URL reach its equivalent in one hop, not the homepage?
• Markup. Does the new theme render what the old site rendered, from Product to BreadcrumbList?
• Content. Did the comparison tables, spec blocks and FAQ sections survive, with each answer still stated plainly near its question? How one product page can serve ChatGPT, Perplexity and Gemini covers the format.
• Render. Does each page load in full for a crawler, so Google can index it with a snippet?

Those four checks cover what a migration could plausibly have broken, so they replace any history repair.