Shopify Product Schema: 7 Fields AI Search Reads

Shopify product schema is the JSON-LD block on your product pages that tells machines what a product is, costs, and whether it is in stock. Most themes output it by default, so the real work is completing seven fields and killing app duplicates. Those fields feed rich results, AI Overviews carousels, and ChatGPT answers, and the same fields are half the work when you get your Shopify products into ChatGPT Shopping.

These are the seven fields worth getting right.

What Are the 7 Product Schema Fields That Matter?

The 7 product schema fields that matter come from Google’s written spec. Its merchant listing documentation requires an Offer with a price above zero and an ISO currency code, and recommends availability, condition, shipping, and returns. Only pages where a shopper can buy are eligible, so collection pages do not count.

1. name: the product’s plain name, matching the visible title on the page.
2. description: what it is, who it is for, and what it is made of, matching the on-page copy, which is the same brief as writing AI product descriptions that rank.
3. offers: price and priceCurrency, the two required fields, plus priceValidUntil if you run sales.
4. availability: InStock, OutOfStock, or PreOrder, kept current, because stale stock kills the listing.
5. aggregateRating and review: the star value, the count, and real review text.
6. brand: your brand name, which matters for branded queries and AI answers.
7. gtin or mpn: the identifier that lets Google and the Shopping Graph match your product to the rest of the world’s data about it.

The first four get you eligible and the last three get you chosen. A listing with stars, a brand, and a matched GTIN shows more than one with a bare price, and the details decide the click. Everything in the block must match what a shopper sees on the page, since Google treats a mismatch as a violation.

Doesn’t Shopify Already Add Product Schema?

Yes, Shopify already adds product schema for the most part, and that is where the problems start. Dawn and the themes built on it output Product JSON-LD out of the box, with name, image, price, and availability wired to your product data, which is why a fresh store usually passes the Rich Results Test without anyone touching code.

Then the apps arrive. A review app injects its own Product block to add stars, an SEO app injects a third to be safe, and now the page has two or three competing blocks with different values. Duplicate schema is the most common structured data problem I find on Shopify audits, and it makes Google pick a block for you, sometimes the one without your reviews.

The fix is one block with everything in it. Let the theme carry the Product schema, use the review app’s integration setting to feed ratings into it rather than adding its own, and remove the SEO app’s duplicate if it has one. Once one block carries everything, the description field does double duty, because the same plain copy is what models quote when they recommend the product.

Why Do AI Surfaces Care About Product Schema?

AI surfaces care about product schema because it is the version of your page a machine can trust. Microsoft’s Bing team said schema markup helps its LLMs understand content, and Copilot draws on the same crawl. Google’s AI carousels pull price and rating from that pipeline too, half of getting into Google AI Overviews.

Google is also clear about what schema is not. Its AI features documentation says no special markup is required for AI Overviews or AI Mode, so schema is not a secret AI ranking lever, it is confirmation of what the page already says. The honest framing is that schema removes ambiguity, and machines reward pages they do not have to guess about.

The classic rich results payoff still stands on its own. Google’s structured data case studies include Nestle measuring 82% higher click-through on rich result pages and Rotten Tomatoes seeing 25% more clicks, and stars plus price in a search result is the closest thing to free ad formatting a store gets. The same seven fields then feed the newer surfaces without any extra work.

How Do You Check and Fix Your Product Schema?

You check and fix your product schema in four steps that take about twenty minutes, once a quarter. You are looking for three failure modes: missing fields, duplicate blocks, and values that drifted out of sync with the page. Fix in that order, because a page with two broken blocks gets nothing from a new field.

1. Run your top five product pages through Google’s Rich Results Test and note every error and warning on the Product result.
2. Open Search Console’s merchant listings report, which Google ships as its own report, and work the error list from most pages affected down.
3. View source and count the application/ld+json blocks that declare a Product. More than one means a theme and app collision, so consolidate to one.
4. Spot-check values against the page: price, availability, and rating should match what a shopper sees today, not last month.

Then leave it alone until products change. Schema is plumbing, and plumbing is done when it stops leaking, so the ongoing work is keeping reviews flowing and stock accurate rather than adding more markup.

One Block of Code, Three Jobs

Shopify product schema comes down to seven fields: name, description, price, availability, ratings and reviews, brand, and GTIN, in one clean block per page. Your theme almost certainly outputs the block already, your apps are the most likely thing breaking it, and the same data earns rich results, feeds AI product carousels, and confirms your catalog feed. Complete it, deduplicate it, and check it quarterly.

I help Shopify brands stop renting their customers from Meta and Google by building search and AI visibility that keeps sending buyers after the ads turn off. If you want your top 20 products audited for the seven fields and the duplicates, my AI search services include exactly that pass.