Magento Product Structured Data: Schema, Offers and Validation
Audit what the storefront actually publishes
Product structured data describes the item and its offer in a format search engines can read. A valid implementation can make a page eligible for supported search features, but it does not guarantee a rich result, ranking improvement or an AI citation. Start with the public product URL and the rendered page rather than assuming a theme or module supplies everything.
Magento stores differ by theme, extensions and storefront architecture. A headless frontend may generate its own JSON-LD. Inspect that frontend, then compare the markup with the price, stock, images and reviews a visitor sees.
Useful types and their limits
| Type | Purpose | Check |
|---|---|---|
| Product | Describes the specific item. | Correct name, image and genuine identifiers; do not invent GTINs. |
| Offer | Describes a purchasable offer. | Price, currency, URL and availability match the visible offer. |
| AggregateRating or Review | Describes actual product feedback. | Only include genuine, eligible feedback visible on the page. |
| BreadcrumbList | Describes the page's navigation hierarchy. | Names and URLs follow a useful, crawlable path. |
Required and recommended properties depend on the feature. Product snippets and merchant listings have different requirements. Use Google's product structured-data documentation for the current rules rather than treating a fixed list of types as a universal checklist.
FAQ content is useful, but the old Google result is gone
Google stopped showing FAQ rich results on 7 May 2026 and subsequently removed the feature documentation. Do not promise an expandable FAQ search listing. A useful question-and-answer section can still help buyers understand compatibility, setup or purchase terms, without adding markup for a discontinued search feature. See Google Search documentation updates.
Check one real offer before changing the whole catalogue
- Choose a representative product. Record its selected variant, displayed price, currency, stock status and canonical URL.
- Inspect the output. Look for duplicate Product objects from a theme and an extension, conflicting currencies, placeholder ratings or data that only appears after an interaction.
- Compare every claim. If the visible offer is GBP 49.00, the structured offer must not show an old GBP 39.00 price. This is an illustrative example, not an AgenticEcom price.
- Validate the public URL. Use the Rich Results Test for Google's supported features and a schema validator for vocabulary checks. A passing test does not guarantee display.
- Repeat with difficult cases. Test a discounted product, an out-of-stock item, a configurable product, an item without reviews and another store-view currency.
For configurable products, decide whether the URL represents the group or a specific variant. Make the identifiers, availability and offer agree with that choice. Do not attach a sibling variant's image or price to the selected item.
Keep product pages and feeds consistent
Product markup and Merchant Center feeds are separate outputs that should describe the same offer. If one updates quickly and the other remains stale, investigate the catalogue mapping and cache invalidation. Our Magento Google Shopping feed guide covers the feed workflow. Review the current product's supported channels before choosing a feed integration.
A useful release check is to change a test product's price or stock in a controlled environment, refresh the storefront and inspect both the visible offer and JSON-LD. Record the time each changes. This exposes stale rendering that a static validator cannot detect.
GraphQL schema discovery is a different job
Schema Discovery for Magento concerns the GraphQL API schema. Discovering API fields and types is different from emitting schema.org Product JSON-LD on a storefront. Do not assume that installing an API schema tool adds search markup. Check the storefront implementation and the tool's actual documented capabilities separately.
Monitor after deployment
Recheck important product URLs after theme, pricing, review or cache changes. Use the relevant Search Console enhancement reports to investigate errors, then inspect affected pages. Keep a small set of representative URLs and expected values for repeatable release checks.
Structured data supports an accurate, accessible product page. It does not replace useful specifications, internal links or a clear buying journey. The Magento SEO checklist provides the wider context.