WooCommerce product schema for AI search: what ChatGPT, Google AI Mode and Perplexity actually read
The Product, Offer, Review and Organization structured data your WooCommerce store needs in 2026 — and the plugin mistakes that silently break it.
By Harri Reili Published 9 min read
Structured data is the closest thing to a common language between your store and the machines that decide whether to recommend it. Google documents Product and merchant listing markup as inputs to Search and Shopping (which feed AI Overviews and AI Mode); Perplexity’s merchant program lists Schema.org Product markup as a requirement; and every feed format — Google, Microsoft, OpenAI — expects the same facts your schema should carry.
Here is the checklist we apply to every WooCommerce store, and the mistakes we fix most often.
The minimum viable Product markup
Every product page should output one JSON-LD block of type Product with:
| Property | Why it matters |
|---|---|
name, description, image |
Identity; images are used in shopping surfaces |
sku, gtin (EAN/UPC), mpn, brand |
Matching to catalogues, reviews and prices across the web |
offers → Offer with price, priceCurrency, availability, url |
Without a valid Offer there is no price and no “in stock” — most assistants skip the product |
offers.priceValidUntil (sales), shippingDetails, hasMerchantReturnPolicy |
Merchant listing details Google surfaces; delivery and returns are top buyer questions |
aggregateRating, review (when you have real reviews) |
Trust signal; enables star display |
category, material, color, size (variable products) |
Helps matching for specific queries |
For variable products, expose each variation as an Offer (or ProductGroup with hasVariant), never one generic price.
Site-wide entities: Organization and WebSite
Add an Organization node with name, url, logo, sameAs (social profiles, marketplaces), contactPoint and a postal address, and reference it as Product.brand/Offer.seller where appropriate. AI systems build a picture of who is selling; consistent entity data across your site, Google Business Profile and marketplaces is part of being trusted.
The five WooCommerce mistakes we see most
- Two schema blocks fighting. WooCommerce core, Rank Math/Yoast and a theme each output Product schema; Google picks one, often the incomplete one. Keep exactly one source.
priceCurrencyoravailabilitymissing because a plugin was configured for a different store type or a currency switcher rewrites prices client-side.- GTIN field empty. WooCommerce has a native GTIN/UPC/EAN/ISBN field (Product data → Inventory) since 9.2 — most stores never fill it. Feed plugins have their own field; keep them in sync.
- Reviews disabled but
aggregateRatingstill output — an invalid rating of “0 (0 reviews)” is worse than none. - Variable products with a single price range in schema while the feed reports per-variant prices — inconsistency erodes trust.
Category pages and FAQs
Category pages can carry CollectionPage + ItemList of products, and buyer FAQs can be marked up as FAQPage. Google stopped showing FAQ rich results for most sites in 2023, but the markup is still valid schema and helps make the page’s questions and answers explicit for machines. Write the questions the way buyers ask them.
Validate like an engineer
- Google Rich Results Test for eligibility and errors.
- Schema.org validator for structural correctness.
- Crawl the whole store (Screaming Frog or similar) to catch templates that differ from the one you tested.
- Compare schema to your Merchant Center feed — price, availability, GTIN must match. Google flags mismatches; AI systems trust consistency.
Does schema alone get you recommended?
No. Google states there are no extra markup requirements to appear in AI Overviews or AI Mode — you need to be indexed and eligible for a snippet. Neither OpenAI nor Perplexity publish evidence that JSON-LD is a ranking factor. What schema does is make your facts unambiguous — the same facts your feeds carry and your pages state — so a system that reads your store cannot get the price, availability or identity wrong. Combine it with feeds, crawler access and answer-ready content, and you have removed every reason for an assistant to prefer a competitor.
If you want a second pair of eyes on your markup, our AI Visibility Audit validates every product template and tells you what to fix first.
Sources: Google Search Central — Product structured data, Merchant listing structured data, “AI features and your website”; Perplexity Merchant Program documentation; OpenAI product feed specification; WooCommerce 9.2 release notes (GTIN field).