Product structured data for ecommerce: what it does and what it does not
It sits inside the larger AEO vs GEO vs SEO debate, which this page does not repeat.
What does product structured data do?
Structured data gives Google explicit clues about what a page means. For a shop, the clues describe a product: name, price, availability, reviews.
Google publishes separate guides for the main types:
- Product markup. Google's intro splits it into product snippets, for pages where people cannot buy directly, and merchant listings, for pages where customers can buy from you2.
- Merchant listing markup. Only pages where a shopper can purchase the product are eligible, and the listing can show details such as price, availability, shipping and returns3.
- Review snippet markup for reviews and ratings4.
Valid markup can make a page eligible for richer results. Google says these are shown at its discretion and may change2. Those results appear on the SERP, alongside everything else Google shows.
Why do e-commerce brands use it?
Because product pages are where the money is, and clearer pages are easier for Google to read. In merchant listings, shoppers may see price and availability before they click3.
It is also a way to keep your product feed and your page saying the same thing. We do not quote click-through gains. We have no source for them.
How do we implement it?
Check the pages first
Product pages should be accurate and complete. If they are thin or wrong, fix the content before marking anything up.
Map fields to markup
Decide which fields on the page feed which markup fields. Mark up what the shopper can see, nothing else.
Build and test
Use one source of markup, so a theme and an app do not contradict each other. Validate pages after each change.
Name an owner
Prices, stock and reviews change, so the markup has to change with them. Someone checks it.
When should you not use it?
Skip the extra effort, for now, when:
What does it cost in effort?
We give no figures.
- Mapping. Decide which fields on the page feed which markup fields.
- Implementation. Templates, a shop app or a developer. Check the output, not the setting.
- Testing. Validate pages after each theme or app change.
- Upkeep. Prices, stock and reviews change. The markup has to change with them.
Pitfalls
Markup that does not match the page
Google lists making sure your structured data matches the visible text on the page among its SEO best practices1. Mark up what the shopper can see, nothing else.
Fake or borrowed reviews
Google's review snippet guidelines say marked-up reviews must be readily available on the page, ratings must come directly from users, reviews must be about a specific item, and reviews or ratings from other websites must not be aggregated4.
Markup built only in JavaScript
Google warns that dynamically generated markup can make Shopping crawls less frequent and less reliable, which matters for fast-changing price and stock3.
Several offers in one merchant listing
Merchant listings need a single offer from the seller, not an aggregate of offers3.
Conflicting markup
A theme and an app that each add their own can contradict one another.
Treating it as a switch
Valid markup makes a page eligible. Google decides what it shows2.
Selling it as an AI fix
Google says no special structured data is needed for its AI features1.
Trust as a badge
Markup does not create E-E-A-T. That framework describes the qualities of content, and is not a single ranking factor.
Our take: Core
We rate product structured data Core. This is our view, not a market fact.
Why? It is low-risk, widely documented by Google, and tied to a concrete outcome: eligibility for rich results. It is part of tidy shop SEO.
For AI visibility, we draw a line. Google's documentation on AI features says you do not need new markup or special schema.org structured data to appear in AI Overviews or AI Mode1. We do not sell "schema for AI". That includes anything sold as GEO built on markup alone.
Our view: do it because it is good housekeeping for search, and drop any claim that it will get you cited by an AI.
FAQ
What is product schema markup?
It is another name for product structured data: code that describes a product to search engines, such as name, price, availability and reviews. Google uses it for product snippets and merchant listings2.
What is merchant listing structured data?
Do I need structured data to appear in AI answers?
Not for Google's AI features. Google says there is no special schema.org structured data you need to add to appear in AI Overviews or AI Mode1.
Will structured data get me rich results?
It can make a page eligible. Google says these features are shown at its discretion2.
What are the rules for review structured data?
The marked-up reviews must be readily available on your page, ratings must come directly from users, and they must be about a specific item. Google also says not to aggregate reviews or ratings from other websites4.
Who should implement it?
Whoever owns your shop templates, with someone who can test the output. Our SEO & AI visibility service covers it.
Sources
- AI features and your website (Google Search Central)Primary source
- Intro to Product Structured Data on Google (Google Search Central)Primary source
- How To Add Merchant Listing Structured Data (Google Search Central)Primary source
- Review Snippet (Review, AggregateRating) Structured Data (Google Search Central)Primary source
Let’s find what’s actually working.
Next step. Want a view on your product markup? Talk to us about your product pages. Or read about our SEO & AI visibility service.