New researchTechnical SEO & AI Search · 2027Explore the framework

Product structured data: product snippets, merchant listings and how to check them

Which product markup Google uses for which pages, the required and recommended properties, availability values, and how to check product markup across a store.

Part of the E-commerce SEO series. For the full picture, start with E-commerce technical SEO: the complete guide for online stores.

Product markup is the most valuable structured data a store can add, and one of the most often broken. A template change drops the price, a currency goes missing, availability says “in stock” on products that sold out last month. Each one quietly removes the rich result.

This guide covers which kind of product markup applies to which pages, the properties Google requires, and how to check markup across a whole catalogue.

Product snippets or merchant listings?

Google’s product structured data introduction describes two uses of the same Product type:

Product snippets Merchant listing experiences
For “Product pages where people can’t directly purchase the product”, such as editorial reviews “Pages where customers can purchase products from you”
Typical site Review sites, comparison content Online stores
Required name, plus at least one of review, aggregateRating or offers See below

Most stores need merchant listings markup on product pages.

What do merchant listings require?

From Google’s merchant listing documentation:

Type Required Recommended (examples)
Product name, image, offers description, brand, sku, gtin, aggregateRating, review, color, size, material
Offer price (greater than zero) and priceCurrency (ISO 4217), or the same inside priceSpecification availability, itemCondition, url, priceValidUntil, shippingDetails, hasMerchantReturnPolicy

A minimal example:

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Trail Runner 2",
  "image": "https://example-store.com/img/trail-runner-2.jpg",
  "sku": "TR2-RED-9",
  "brand": { "@type": "Brand", "name": "Example" },
  "offers": {
    "@type": "Offer",
    "price": 129.00,
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://example-store.com/trail-runner-2/"
  }
}

Availability

availability uses schema.org values such as InStock, OutOfStock and BackOrder. Keep it in sync with the page: when a product sells out, the page and the markup should both say so. That’s also the right way to handle temporarily out-of-stock products, rather than removing the page; see the e-commerce technical SEO guide.

Variants

Products sold in several colours or sizes can describe the group with ProductGroup and each variant with its own Product. See product variants and SEO.

Structured data, Merchant Center, or both?

Both. Google says “providing both structured data on web pages and a Merchant Center feed maximizes your eligibility to experiences and helps Google correctly understand and verify your data.” Some surfaces need Merchant Center: Google’s e-commerce guide says to “upload your products to Google Merchant Center” to appear in the Shopping tab, and Lens and local inventory also rely on it.

Whatever the source, the markup, the feed and the visible page must agree on price and availability.

How do you check product markup across a store?

Google’s Rich Results Test and Search Console’s rich result reports check pages one by one or as Google finds them. To check every product page in one pass, crawl the store. Crawlens extracts JSON-LD from every page and flags:

Check What it catches
Invalid JSON-LD Syntax errors that make the whole block ignored
Structured data missing required properties Product without a name, or without any of offers, review or aggregateRating; Offer without a price

These follow the product snippet requirements. Merchant listings also need image and priceCurrency, so check those as well. Use custom extraction to pull values into columns for every product, for example with regex extractors on the JSON-LD for "priceCurrency", "availability" and "gtin13", and a custom rule that flags product pages where any of them is empty. Then:

  • Compare price and availability with the page. Extract the visible price with a CSS extractor and compare it with the markup’s.
  • Find out-of-stock products at scale by filtering the availability column.
  • Spot templates without markup: product URLs where the extraction is empty.

Each URL’s details in Crawlens also show the structured data found on it. For the general approach to structured data errors, see structured data errors.

Checklist

  • Merchant listings markup on every buyable product page
  • name, image and offers on every Product
  • price (above zero) and priceCurrency on every Offer
  • availability set and kept in sync with the page
  • brand, sku/gtin, shipping and return policy where available
  • Variants described with ProductGroup where relevant
  • Merchant Center feed matches the pages and markup
  • No invalid JSON-LD; required properties present across the catalogue
  • Visible price and markup price match

Frequently asked questions

What's the difference between product snippets and merchant listings?

Product snippets are for pages where people can't buy the product directly, such as editorial reviews. Merchant listing experiences are for pages where customers can buy the product from you. They have different required properties.

What properties are required for product structured data?

For product snippets, a name plus at least one of review, aggregateRating or offers. For merchant listings, the product needs name, image and offers, and the offer needs a price greater than zero and a priceCurrency.

How do I mark a product as out of stock in structured data?

Set the offer's availability to https://schema.org/OutOfStock. Other values include InStock and BackOrder. Keep it in sync with what the page shows.

Do I need Merchant Center if I have product structured data?

Google recommends both. It says providing structured data on web pages and a Merchant Center feed maximizes your eligibility for its experiences and helps it understand and verify your data. The Shopping tab and Lens rely on Merchant Center.

Does product structured data improve rankings?

It makes pages eligible for rich product results and merchant listing experiences, which can make them more visible and clickable. Google says structured data isn't required for its generative AI features and there's no special markup for them.

· Founder, Crawlens

Dien builds Crawlens, a desktop crawler for technical SEO audits, and writes about the checks it runs: crawling, indexing, rendering and Search Console data.

Audit your own site with Crawlens

Crawl, run 70 checks, and see them next to Search Console and Core Web Vitals data.

Download free for Windows