What Google actually says about being surfaced in AI Overviews and AI Mode

The entry condition is boring, and that is the point

Google publishes an optimisation guide for generative AI features on Search. The operative sentence is short:

"To be eligible to be shown in generative AI features on Google Search, a page must be indexed and eligible to be shown in Google Search with a snippet."

That is the whole gate. Indexed, and snippet-eligible. There is no second list of requirements, no registration, no separate submission surface for AI Overviews or AI Mode.

For a Shopify merchant this reframes the question. "How do I get into AI Overviews" is not a new discipline. It resolves to two older questions you can answer today:

Is this URL indexed by Google?
Is this URL allowed to show a snippet?

If either answer is no, nothing else in this article matters. If both are yes, you are already eligible, and eligibility is where Google's documented control ends.

The scale is worth stating because it sets the stakes rather than the tactics. Google said in May 2026 that AI Mode "has surpassed one billion monthly users, with queries more than doubling every quarter since launch." That is a traffic surface, not a new optimisation channel with its own rulebook.

What Google says you do not need to build

The guide is unusually direct about the things merchants are being sold. Four claims from the same document:

"Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add."
"You don't need to create new machine readable files, AI text files, markup, or Markdown to appear in Google Search (including its generative AI capabilities)."
"There's no requirement to break your content into tiny pieces for AI to better understand it."
Google ignores llms.txt.

The older companion page, "AI features and your website", repeats the schema point: "There's also no special schema.org structured data that you need to add."

So the following are not, by Google's own documentation, entry requirements for AI Overviews or AI Mode: a /llms.txt file, a Markdown mirror of your product pages, an "AI sitemap", a new schema type, or chopping your product descriptions into atomic chunks.

This matters on Shopify specifically because these are easy things to sell as app features. A file at the root of your storefront is cheap to generate and impossible to falsify from the outside. Google's position is that it does not read one.

If you want to build these anyway, do it for a reason you can state. Documentation sites publish llms.txt for their own developer audiences. That is a different purpose from ranking, and it is the only purpose the spec's own ecosystem demonstrates.

Three control planes, three different effects

The most common merchant error in 2026 is treating "AI" as a single switch. Google documents three separate mechanisms, and they do different things. Confusing them is how a store accidentally removes itself from a surface it wanted.

1. Snippet controls (affects Search and generative AI together)

The "AI features and your website" page lists the available controls as nosnippet, data-nosnippet, max-snippet, and noindex.

These are the same controls you have always had. They are not AI-specific. Applying nosnippet to a page removes snippet eligibility, and snippet eligibility is the entry condition for generative AI features. You cannot suppress the AI surface this way without also suppressing the ordinary snippet.

data-nosnippet is the surgical one. It marks a region of a page rather than the whole page. On a Shopify product template that is the difference between excluding a shipping-policy block and excluding the product.

2. Search generative AI control (affects only certain generative AI features)

Google Search Console documents a distinct control. Its help page states:

"This control only affects whether your content can appear in certain Search generative AI features; this control isn't used as a ranking or inclusion signal affecting other parts of Search."

Two consequences follow directly from that sentence. Using it does not demote you in ordinary Search. And it does not touch model training.

The same page is explicit on the second point: "To limit training of the models used to generate responses in Search generative AI features, use Google-Extended."

3. Google-Extended (affects training, not Search)

Google's crawler list describes Google-Extended as "a standalone product token that web publishers can use to manage whether content Google crawls from their sites may be used for training future generations of Gemini models."

And then the line most merchants need to read twice: "Google-Extended does not impact a site's inclusion in Google Search nor is it used as a ranking signal in Google Search."

Blocking Google-Extended in robots.txt is a training decision. It is not a Search decision, and Google says it carries no ranking penalty.

The exception that protects your shopping surfaces

There is one more sentence in the Search generative AI control documentation that is load-bearing for commerce. The control "doesn't override publishers' other choices to participate in particular services, such as Merchant Center and Google Ads."

Read that as a boundary between two different pipelines. Your website content flows through crawling, indexing and snippets. Your product data flows through Merchant Center. A control that governs the first does not govern the second.

Why "no structured data needed" is true and false at the same time

Here is the part that trips up Shopify merchants, because both halves are documented and they appear to contradict.

True for organic AI answers. If Google's generative AI features quote or cite your blog post, collection page or product page as content, the guide says no special markup is required. Indexed plus snippet-eligible is the condition. Product schema is not an AI ticket.

False for AI shopping. Shopping surfaces do not run on crawled prose. They run on product data, and product data has explicit field requirements.

Google's Product structured data documentation says Product markup drives richer results in Search, Images and Lens, plus merchant listing eligibility. Notably, that page does not mention AI features or shopping agents at all. It is a rich-results and merchant-listings document.

Then there is the commerce protocol layer. Google's Merchant Center documentation for the Universal Commerce Protocol states that "You remain the Merchant of Record", and that "Only product listings using the native_commerce(checkout_eligibility) product attribute will display the 'Buy' button."

That is a field-level requirement. A specific attribute on a specific listing determines whether a specific button renders. No amount of well-written product copy substitutes for it.

Google announced Universal Cart in May 2026 as "an intelligent shopping cart and your new hub for shopping on Google." The buy-side surface is real, and it is fed by structured listings rather than by page text.

So the honest formulation is this. Structured data is not the entry condition for being cited in an AI answer. Structured data is the entry condition for being transactable in an AI shopping surface. Those are two different jobs, and merchants are repeatedly sold one as if it were the other.

What a Shopify merchant should actually check

Concrete items, in order of how often they are wrong.

Indexation of product and collection URLs. Shopify generates a large number of URL variants. Confirm the canonical product URLs are indexed, not just the homepage. This is the first half of the entry condition and it is verifiable in Search Console.

Snippet eligibility. Audit your theme and any installed app for nosnippet, max-snippet values you did not set, and stray data-nosnippet attributes. Apps that inject markup into product templates can suppress snippets without telling you. Loss of snippet eligibility removes generative AI eligibility as a side effect.

Robots directives for the three tokens separately. Decide Googlebot, Google-Extended and the Search generative AI control independently. Write down which one you intended to change and what it governs. A merchant who blocks Google-Extended expecting to leave AI Overviews has made a training decision and nothing else.

Merchant Center as a separate account of your product data. Your feed is not your theme. If you want a Buy button on Google's agentic surfaces, the native_commerce(checkout_eligibility) attribute is the documented condition. Check the feed, not the page.

Product field completeness. This is the one area where effort on the catalogue helps both pipelines. Complete titles, descriptions, options, availability and images are what shopping surfaces consume. The Google documentation above does not promise that completeness produces citations. It does establish that incompleteness limits eligibility on the shopping side.

The inference, labelled as one

Google documents eligibility conditions. It does not document selection. Nothing in the optimisation guide says which eligible pages get chosen for a given AI Overview, or in what order, or how often.

The reasonable reading is that the guide is a floor, not a lever. It tells you how to avoid disqualifying yourself. It does not tell you how to win, and anyone claiming a documented method for winning is going beyond what Google has published.

That is the useful takeaway for a Shopify store. Spend your time on indexation, snippet eligibility, and the completeness of structured product data that shopping surfaces actually read. Do not spend it on files Google says it ignores.

Sources

Optimizing your website for generative AI features on Google Search — Google Search Central, updated 2026-07-10
AI features and your website — Google Search Central, updated 2025-12-10
List of Google's common crawlers — Google, updated 2026-07-14
Search generative AI control — Google Search Console Help, as of 2026-08-31
New opportunities, control and insights for website owners — Google (The Keyword), 2026-06-03, updated 2026-08-31
A new era for AI Search — Google, 2026-05-19
Product structured data — Google Search Central, updated 2025-12-10
Merchant Center UCP requirements — Google Merchant Center Help
Universal Commerce Protocol for merchants — Google
Universal Cart — Google, 2026-05-19