What Google, AI Mode, and ChatGPT actually read on your product page

Optimize a product page for Google and AI search by doing three jobs in a fixed order: keep winning the click for your own product queries, make the product's facts machine-verifiable, and earn mentions where answer engines actually look. Google's own documentation now says the third job decides how your product gets described, and it is the one most teams never start.

Earlier this week a beginner in r/SEO asked how to approach a product page from scratch: keyword research, on-page SEO, technical SEO, product schema, internal linking, backlinks. The question is fair. The list is the problem. Every item on it was the right answer in 2019, and not one of them decides whether ChatGPT describes your product correctly.

Google's guide to optimizing for generative AI features is blunter than most agency advice. Generative features, it says, "can show what's being said about products and services across the web, including in blogs, videos, and forum discussions." The same page tells readers to skip the tricks the last two years sold: chunking content into fragments for models, rewriting copy in an AI-friendly voice, chasing llms.txt, and paying for mentions. It also carries a section called "Optimize your local business and ecommerce details," which is worth reading correctly. Google thinks the fundamentals are the AI strategy for product pages.

The click is still Google's to give

Nothing about answering machines has changed the economics of a product query. Someone types your SKU or your product plus "price," and one of two things happens: they click and land on your page, or an answer assembles around them and the click lands somewhere else. The first outcome is still the cheapest sale you will make, and it is won the way it was won in 2019: a title that names the product, a price visible without interaction, real reviews, and category pages that actually link to the products they contain.

What changed is how far that work now carries. The 320-query citation study we broke down earlier this year found that AI Mode pulls 93% of its cited sources from Google's own top-10 results, and Perplexity 89%. Ranking for your product query is now also how you become raw material for those two surfaces. A page sitting on page three earns nothing from either.

There is a second reason not to abandon the click. Research reported by Digiday in October puts 16% of shoppers starting product searches in ChatGPT, and 9% buying there. The gap between those two numbers is discovery without purchase, and closing it is still the job of the page.

Google's Product documentation also stopped being a markup-only story. There are two classes of markup, product snippets and merchant listings, and Google now says plainly that you can feed it page markup, a Merchant Center feed, or both, with both maximizing eligibility. The line that matters: product snippets "may use pricing data from your merchant feed if it's not present in the structured data on the page." Your feed is part of your product page now, whether or not the team that owns it reports to marketing.

Make the facts verifiable, not rewritten

The temptation is to rewrite the page for machines: denser prose, more sections, an FAQ block on every product, specifications restated three ways. Google's guide says directly that you do not need to write in a specific way for generative AI features, that there is no ideal page length, and that chunking content is unnecessary.

What you actually owe a machine is a set of facts it can read, cross-check, and trust:

• Specifications as HTML text, not as an image of a spec sheet. Google's own guidance on agentic experiences notes that browser agents inspect the DOM structure, accessibility tree, and rendered screenshots. A spec table built out of text is readable three different ways; a JPG is readable one.
• One price, one availability state, one set of identifiers, agreed across the page, the feed, and the largest marketplace listing for that product. An engine that quotes a stale price does not just lose you the citation, it loses you the buyer who checked.
• Plain sentences next to the specs that answer the actual question: what it fits, what it does not, what you need with it. Retrieval works on passages, and a passage that answers "will this work with my model" is worth more than a paragraph of category keywords.

In the catalog audits we run, this is where teams stall. The page is clean, crawlable, marked up, and still absent from the answer, because everything they touched was read by Google and nothing they touched was read by ChatGPT.

What each surface actually reads

The mistake behind most product-page GEO plans is treating "AI search" as one channel. It is at least four, and they read different things.

The engine-by-engine split matters more than any single number. Our breakdown of the citation rulebooks each engine follows explains why the same page can be invisible in ChatGPT and dominant in AI Mode: each engine pulls from a different pool, and only some of those pools are Google's rankings.

The part your page cannot do

Google's list of what generative features read ends with blogs, videos, and forum discussions. Read that as a work order. For most product categories the answer is assembled from category roundups, review platforms, comparison threads, and video reviews, and your product page is quoted only when it supplies a fact the others do not.

The AI Citation Source Index, which synthesizes more than 680 million citations, puts numbers on the concentration: the top 15 domains capture roughly 68% of consolidated citation share, with community and reference sources dominating, and each engine favoring a different mix. Meanwhile the same report's engine table shows ChatGPT leaning on encyclopedic and editorial sources while Google's own features lean on community ones.

You cannot mark up your way onto those surfaces, and Google explicitly warns that seeking inauthentic mentions "isn't as helpful as it might seem." The mentions that work are the ones a real customer would leave anyway, which makes the practical version of this work unglamorous: get the product into category comparisons people read, answer forum questions where your category is discussed, and make review generation part of fulfillment instead of a campaign. We wrote earlier about why most brands stay invisible in AI product discovery even with a technically perfect catalog; the page-level changes above are the half that sits on your own domain.

What to skip for now

Three things the last two years sold that Google has now told you to stop doing, and we would stop regardless: FAQ blocks written to be quoted (Google removed FAQ rich results in May 2026, and our earlier breakdown covers what replaced them), prose rewritten in an AI-friendly register, and mention schemes. None of them change what an engine retrieves.

The build order

If you want the sequence rather than the essay, run it in this order:

1. Group Search Console by query and page for your product queries. Do you own your SKU query? If not, classic SEO first, because everything downstream reads from a page that ranks.
2. Run one fact pass across page, feed, and the largest third-party listing for each priority product. Price, availability, identifiers, specifications in text.
3. For the top comparison and review queries in your category, find where the answers come from and get your product present on those surfaces honestly.

That sequence is the audit our SEO and GEO team runs for catalog owners, from the first Search Console pull to the surface map: SEO & GEO services. If you are still deciding whether any of this is SEO or GEO, the distinction turns out to matter less than the order: GEO versus SEO, checked against the data.