Why do a competitor’s products show a star rating, a price, and an “in stock” badge right in the Google results while yours show a plain blue link? It usually comes down to one thing the competitor did and you did not: they marked up their product pages with structured data, and Google could read it. That same markup is now what decides whether your catalog shows up in free Merchant listings, in the Shopping tab, and increasingly in the answers AI shopping assistants give when someone asks for a product like yours.
This guide covers what product structured data is, what it does for you today, how to add it, and how to check it actually works. The goal is practical: get your products eligible for the visibility your competitors already have.
Overview
- Product structured data is markup you add to product pages so Google and other platforms can read the price, availability, rating, and other details directly, instead of guessing from the page text.
- It is the gating requirement for three things merchants want: rich results in Search, free product listings and the Shopping tab via Merchant Center, and eligibility to be surfaced by AI shopping assistants.
- Google recommends JSON-LD, and the markup has to live in the HTML your server returns. A 2026 Mirakl analysis found fewer than 10% of product pages carried the structured data needed to surface in shopping agents and LLM answers, so the bar to stand out is lower than most merchants assume.
π Quick takeaway
The blue-link-versus-rich-result gap is rarely about authority or budget. It is about whether your product data is machine-readable, and most catalogs still are not.
What is product structured data?
Product structured data is a standardized way to annotate a product page so search engines and shopping platforms can pull out the facts that matter: name, price, currency, availability, brand, rating, and more. Instead of a crawler guessing what “$49.99” on the page means, the markup tells it explicitly: this is the price, in this currency, for this product, and it is in stock.
It follows the vocabulary published by Schema.org, which major search engines and platforms read. When the markup is valid, Google can render your listing as a rich result: a richer block in the search results with extra detail and visual elements, set apart from plain text links.
π Quick takeaway
Structured data does not change what a human sees on your page. It changes what a machine understands about it, which is exactly what decides whether you get a rich result.
What does product structured data do for merchants?
Product structured data is what makes your products eligible for rich results in Search, free listings through Google Merchant Center, the Shopping tab, and the product feeds that advertising platforms run on. In plain terms, it is the difference between a product page that only ranks as a link and one that can earn visual, detail-rich placement across Google’s shopping surfaces at no media cost.
Google now separates product results into two experiences, and the distinction matters for what you can earn:
- Merchant listings are for pages where shoppers can buy directly. They support shipping and return policy properties and are what feed the Shopping tab and free product listings.
- Product snippets are for pages where people cannot purchase directly, such as a review or aggregator page, and lean on review and rating data.
Adding the properties required for a merchant listing also makes a page eligible for product snippets, so getting the merchant-listing markup right covers both cases. The honest framing today is eligibility, not a guaranteed revenue lift. Without the markup you are not in the running for these placements at all, and the upside scales with how complete and accurate your product data is.
There is a real example behind this. When scandiweb set up a new Google Shopping channel for a US and Canada identification-solutions merchant, automating the product data sync between Magento and Merchant Center took active products from 43 to thousands and helped order quantity climb from 10 to 50-plus in two months. The structured data and feed were the foundation that made that channel work at all.
π Quick takeaway
The point of product markup is not a guaranteed revenue percentage. It is eligibility. Skip it and your products cannot appear in the placements that drive free shopping traffic.
How do you add product structured data?
You add product structured data by choosing a markup format, placing the required properties in your product page HTML, and submitting the data to the platforms you want to appear on. The two formats worth using are Schema.org Microdata and JSON-LD, and Google recommends JSON-LD.
Where to add product markup
Product markup belongs on the pages that represent a single buyable product. The two common cases are:
- A product detail page on a specific brand’s store, where the shopper can add the item to cart.
- A shopping aggregator page that lists the same product from different sellers, similar to a marketplace listing.
For a merchant running their own store, the product detail page is the priority. That is the page that needs to qualify as a merchant listing.
What markup format to use
Structured data can be expressed in three formats: Schema.org Microdata, JSON-LD, and RDFa. For product data, the practical choice is JSON-LD. Google recommends JSON-LD, and it keeps the markup in a single script block rather than scattered across your HTML tags, which is easier to maintain.
One rule trips up a lot of teams: your markup has to live in the HTML your server returns. Schema injected by JavaScript after the page loads may not be read, so if your store renders product data client-side, confirm the structured data is present in the server response, not just in the rendered DOM.
Required properties for product markup
At the top level, an annotated product needs a name plus one of Review, AggregateRating, or Offers to be eligible for rich results. In practice, merchant listings need more than the bare minimum, because Google and the feed platforms ask for the details that make a listing useful.
For most stores, the working set of properties to get right is:
name,brand,description,image, and the producturlofferswithprice,priceCurrency,availability, andconditionskuor anotherproductID, plusgtinormpnwhere the product has one
For variant products, the isVariantOf property lets you represent options like size or color without splitting them into separate URLs, which keeps your markup clean and your ranking signals consolidated.
π Quick takeaway
The minimum for a rich result and the set Google actually wants for a strong merchant listing are not the same. Mark up the full working set, not just the two required fields.
How to validate product structured data
Validate your markup with Google’s Rich Results Test and the Schema Markup Validator. The Rich Results Test tells you whether a page is eligible for a specific rich result and flags errors and warnings. The Schema.org validator checks that your markup is syntactically correct.
If you have used structured data before, note that Google’s old Structured Data Testing Tool has been retired. The Rich Results Test is the current eligibility checker, and validation is also where a wider technical SEO audit catches markup that passed in isolation but breaks at scale across a large catalog.
Does product structured data still matter for AI search?
Yes, and it is becoming more important, not less. As shopping assistants and large language models start answering “find me a product like this” queries, structured data is one of the clearest signals they can read to understand what you sell, what it costs, and whether it is available. Well-implemented product schema is increasingly suspected to influence AI search interpretation of products and entities, though the major engines have not confirmed the exact weighting.
The opportunity here is unusually open. A 2026 Mirakl analysis of 427 product pages across 35 countries found that fewer than 10% carried the structured data needed to surface in shopping agents and LLM answers, with most pages scoring 5 to 12 out of 30 and only 9% scoring 18 or higher. Treat that as a LinkedIn analysis rather than a peer-reviewed study, but the direction is clear: the catalogs that are machine-readable today are competing against a field where most are not.
This is the technical backbone of answer engine optimization (AEO). If you want your products considered when someone asks an AI assistant for a recommendation, the same markup that earns a rich result is what makes you legible to the model.
π Quick takeaway
The AI-shopping shift does not need a new playbook. The structured data you add for Google rich results is the same data that makes your products readable to LLMs and shopping agents.
Product structured data requirements for Google and Facebook
On-page product structured data is the source the Product Catalog pulls from on advertising platforms and other listings. The same markup feeds both Google Merchant Center and Facebook Catalog, with small differences in which fields each one requires.
Google Merchant Center and free listings
For your products to appear as rich results in Search and Images, properly annotated product pages are enough. To reach the Shopping tab and free product listings, you submit your product feed to Google Merchant Center. Once you have valid structured data on your site, the “website crawl” feed method becomes available, and you can enable automated feeds that read your markup and sitemap to keep product data current.
Google Merchant Center accepts Microdata, JSON-LD, and RDFa. If your pages meet the requirements, Google pulls the product details it needs to build the listing. For automatic item updates, specify price, priceCurrency, availability, and condition, where availability values include InStock, OutOfStock, PreOrder, and BackOrder.
Facebook Catalog
To connect Facebook Catalog, you need Facebook Business Manager set up and the Facebook pixel on your site, and your product pages need microdata Facebook can read. Facebook supports three ways to keep a catalog updated automatically:
- OpenGraph, Facebook’s own protocol, placed in the head of your page
- Schema.org Microdata, placed across the product page
- JSON-LD for Schema.org, placed inside a script tag
Markup that works for both platforms
If you want one set of markup valid for both Google and Facebook, the format options are Schema.org Microdata and JSON-LD for Schema.org. The tables below show the fields each platform expects, in both formats.
| Microdata tag | Attribute from the page | Required for Merchant Center? | Required for Facebook Catalog? |
|---|---|---|---|
| Name | Product name | Yes | Yes |
| Brand | Brand name (can be the site name) | Yes | Yes |
| Description | Short description | Yes | Yes |
| productID | SKU | Yes | Yes |
| url | Product page URL | Yes | Yes |
| image | Image URL | Yes | Yes |
| price | Numeric value only | Yes | Yes |
| priceCurrency | Currency in the accepted format | Yes | Yes |
| availability | In stock or out of stock | No | Yes |
| condition | New, refurbished, or used | No | Yes |
| GTIN | Only if issued | Yes (if issued) | No |
| MPN | Only if issued | Yes (if issued) | No |
| JSON-LD tag | Attribute from the page | Required for Merchant Center? | Required for Facebook Catalog? |
|---|---|---|---|
| name | Product name | Yes | Yes |
| brand | Brand name (can be the site name) | Yes | Yes |
| description | Short description | Yes | Yes |
| productID | SKU | Yes | Yes |
| url | Product page URL | Yes | Yes |
| image | Image URL | Yes | Yes |
| offers | Offer nested inside offers | Yes | Yes |
| price | Price without currency | Yes | Yes |
| priceCurrency | Currency in the accepted format | Yes | Yes |
| availability | In stock or out of stock | No | Yes |
| condition | New, refurbished, or used | No | Yes |
| GTIN | Only if issued | Yes (if issued) | No |
| MPN | Only if issued | Yes (if issued) | No |
Product feeds are not the only way to pass data to these platforms, but they are the most common and most reliable way to keep listings current. Beyond the required fields, adding accurate recommended properties improves your chances of a richer display. Complete and correct beats long and sloppy, so prioritize getting the core set right over stuffing in every optional field.
π Quick takeaway
The required-field lists for Merchant Center and Facebook overlap heavily but are not identical. Mark up availability and condition even where Google calls them optional, because Facebook and the AI surfaces use them.
eCommerce platforms and product feeds
How you sync products to Google and Facebook depends on your platform. Here is the short version for the common ones.
Magento (Adobe Commerce)
The Magento Marketplace lists numerous product feed extensions that generate, upload, and manage feeds for Google, Facebook, Amazon, Instagram, Pinterest, eBay, and more. The Magento 2 product feed extensions worth a look are Xtento and Amasty, which handle the export and scheduling so your feed stays in sync.
For larger Magento (Adobe Commerce) catalogs, the markup and feed are only half the job. Getting structured data, canonical handling, and crawl behavior right across thousands of SKUs is where Magento SEO services earn their keep, because a single misconfigured template can disqualify an entire product type from rich results.
Shopify
You can add the Google channel as an app from the Shopify App Store to sync products between Shopify and Google, subject to the store requirements Google sets. Facebook needs a separate app. If you are tightening up a Shopify store more broadly, the Shopify SEO checklist walks through the technical and on-page work that surrounds the feed.
WooCommerce
The Google Listings and Ads extension, built with Google, connects a WooCommerce store to Merchant Center directly. A separate extension handles the Facebook sync.
Other platforms
Most mature platforms, including Drupal Commerce, have modules or apps that sync product data to Google and Facebook. The pattern is the same everywhere: valid structured data on the page first, then a feed connector that reads it.
FAQ
What is product structured data?
Product structured data is standardized markup added to a product page so search engines and shopping platforms can read details like name, price, availability, and rating directly from the HTML. It makes your products eligible for rich results, free Merchant listings, and AI shopping answers.
What are the three formats of structured data?
The three formats are Schema.org Microdata, JSON-LD, and RDFa. For product pages, JSON-LD is the recommended choice because Google recommends it and it keeps all the markup in one script block instead of spread across your page’s HTML tags.
Does product schema still matter for AI search?
Yes. Shopping assistants and large language models read structured data to understand what you sell, what it costs, and whether it is in stock. With fewer than 10% of product pages currently AI-ready by one 2026 analysis, machine-readable product data is one of the clearest ways to be considered in AI shopping answers.
Which tool replaced Google’s Structured Data Testing Tool?
Google’s Structured Data Testing Tool was retired. Use the Rich Results Test to check whether a page is eligible for a specific rich result, and the Schema Markup Validator at validator.schema.org to confirm the markup is syntactically correct.
What is the difference between merchant listings and product snippets?
Merchant listings are for pages where shoppers can buy directly and support shipping and return-policy properties, which feed the Shopping tab and free listings. Product snippets are for pages where people cannot purchase directly and rely on review and rating data. The merchant-listing markup also makes a page eligible for product snippets.
Do I need a product feed if I already have structured data?
Structured data alone qualifies you for rich results in Search and Images. To reach the Shopping tab and free product listings, you also submit a feed to Google Merchant Center, and valid on-page structured data is what turns on the automated “website crawl” feed method.
About this guide
Written by Henriks Diure, SEO Specialist at scandiweb. Maintained by the scandiweb SEO team. Last updated May 2026.
Is your catalog structured so Google and AI shopping engines can actually read it? If you are not sure which product pages qualify for rich results and which are invisible to the Shopping tab, get a structured-data audit and we will tell you exactly what is missing and how to fix it across your platform.
Share on: