By Steve Merrill, Founder of WRKNG Digital | September 20, 2026
What structured data does Google Shopping and AI both read?
Google Shopping and AI shopping assistants both read the same eight JSON-LD Product fields: name, offers (price and currency), availability, brand, gtin or mpn, aggregateRating or review, image, and shipping and return details. Get all eight right and you feed both the Shopping graph and the AI answer in one shot. Most Shopify stores nail five and skip three.
I've had a hard time getting store owners to care about the boring fields. They're not boring. They're the ones that decide whether an AI quotes your product or your competitor's. Here's the full list.
1. name (the product name)
The name field is the exact product title, and it should match what a shopper would type or say out loud. Google's Product structured data docs list it as required, and Schema.org defines it as plain text. Keep it under 150 characters and drop the internal SKU codes.
2. offers (price and currency)
The offers object holds price and priceCurrency, and both are required for a valid Product. Price must be a number with no currency symbol inside it, and currency uses the ISO 4217 code like USD or GBP. Google won't show a price-based rich result without this, and AI assistants can't quote a number they can't parse.
3. availability
The availability field tells crawlers whether the item is in stock, using a Schema.org URL value like https://schema.org/InStock or OutOfStock. This is one AI leans on hard, because an assistant recommending a sold-out product looks broken. Sync it to your real inventory, not a hardcoded "in stock."
4. brand
The brand field names the maker, and it should be an object with "@type": "Brand" and a name. It matters for comparison queries, since AI answers group results by brand when a shopper asks "best running shoes from Nike or Hoka." Leave it blank and your product falls out of those brand-filtered answers.
5. gtin or mpn (the field most stores skip)
The gtin (UPC, EAN, or ISBN) or mpn is the unique product identifier, and this is the first of the three most stores skip. Google Merchant Center uses these identifiers to match your product to the same item across the web, which powers price comparison and trust. Without a gtin, an AI can't confirm your $89 jacket is the same one selling for $79 elsewhere, so it hesitates to recommend yours.
6. aggregateRating or review (the second skipped field)
The aggregateRating holds your star average and review count, and review holds individual reviews. This is the second field stores skip, usually because the review app doesn't inject it into the Product JSON-LD. Ratings are one of the strongest signals AI uses when it ranks options, and a listing with "4.7 stars, 312 reviews" gets quoted over a listing with nothing.
7. image
The image field takes one or more high-resolution URLs, and Google recommends multiple images at a minimum of 1200 pixels wide. Use absolute URLs, not relative paths, or crawlers drop them. AI shopping surfaces increasingly show a thumbnail next to the answer, so a missing image means your product shows up as a bare line of text.
8. shippingDetails and hasMerchantReturnPolicy (the third skipped field)
The shippingDetails and hasMerchantReturnPolicy fields cover delivery cost, delivery time, and returns, and this pair is the third field stores skip almost universally. Shopify's structured data docs support adding them, and Google uses them to show shipping and return annotations right in the result. Free shipping and easy returns are exactly what tips an AI recommendation your way.
How we chose this list
These eight fields are the ones that appear in both Google's Product structured data documentation and the Merchant Center product data spec, so they serve Shopping listings and on-page AI reads at the same time. We flagged gtin, ratings, and shipping/returns as the three most-skipped based on what default Shopify themes leave out of the Product JSON-LD.
FAQ
Q: What structured data does Google Shopping need for AI?
Google Shopping and AI assistants both read JSON-LD Product schema. The core fields are name, offers with price and priceCurrency, availability, brand, gtin or mpn, aggregateRating or review, image, and shipping and return details. They mirror the data Merchant Center already pulls from your feed.
Q: Which structured-data fields do most Shopify stores skip?
The three most-skipped are gtin or mpn, aggregateRating or review, and shippingDetails with hasMerchantReturnPolicy. Most default themes leave these out of the Product JSON-LD even when the store already has the data.
Q: Do I need both a product feed and JSON-LD schema?
Yes. The Merchant Center feed powers your Shopping listings, and the on-page JSON-LD is what crawlers and AI assistants read straight off the product page. Keep the two in sync and you earn rich results plus AI mentions.
Q: Does structured data help my store show up in AI answers?
It does. AI assistants pull price, availability, ratings, and identifiers directly from Product schema when they compare products. Missing fields make your listing harder to quote, so the AI cites a competitor with cleaner data.
Want your product pages built to feed both Google Shopping and the AI assistants your buyers already use? See how we do it at WRKNG Digital's agentic commerce page.
