Structured dataschema.orgSEO5 min read · 2026-11-03

Product Structured Data for AI Agents and Search: A schema.org Guide

A practical guide to schema.org Product and Offer markup in JSON-LD: which fields to include, how to avoid common errors, and how to test your pages for AI agents and search engines.

Product structured data is a block of JSON-LD code that describes a product in a standard format from schema.org. At a minimum, a product needs a name, an image and an Offer with price, currency and availability. Search engines and AI agents can read this block directly, so it gives them clean facts without guessing from your page layout.

What structured data is

Structured data is machine-readable information added to a page. The most common format is JSON-LD, a script block in the page head or body. It uses the schema.org vocabulary.

The block does not change how your page looks. It tells software what the page is about. For a product page, the two key types are:

Google documents which fields it reads for product rich results and merchant listings. Other search engines and AI systems may read the same markup. Support differs by system, and no one can promise that markup leads to a mention or a sale.

A minimal, correct example

This example shows a product with one offer.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Merino beanie, grey, one size",
  "image": ["https://example.com/images/merino-beanie-grey.jpg"],
  "description": "Soft beanie made from 100% merino wool. One size fits most adults.",
  "sku": "BEANIE-GREY",
  "gtin13": "4006381333931",
  "brand": { "@type": "Brand", "name": "Example Brand" },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/products/merino-beanie-grey",
    "priceCurrency": "EUR",
    "price": "29.90",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  }
}

Use your own real values. The URLs, brand and numbers above are examples only.

Fields to include

Product fields

Offer fields

Optional fields that help

Check Google's current documentation for the exact fields it supports for each use.

Variants

Products with sizes or colors need care. Schema.org has a ProductGroup type with hasVariant and variesBy for this. Each variant is a Product with its own SKU, price and availability.

If your platform does not output ProductGroup, make sure at least that the selected variant on each URL has the right price and availability.

Common errors

How to test

  1. Open the Schema Markup Validator at schema.org and check that the JSON-LD parses.
  2. Use Google's Rich Results Test on a live URL. Fix errors first, then warnings.
  3. In Google Search Console, check the product and merchant listing reports, if you use them.
  4. Compare the markup with the visible page: price, currency, stock, title.
  5. Re-test after theme, plugin or platform updates.

Shopify and WooCommerce notes

If you edit markup in theme code, work on a copy first.

Frequently asked questions

Is JSON-LD better than other formats?

JSON-LD is the format Google recommends. It is easier to maintain than Microdata, because it sits in one block and does not mix with your HTML.

Do AI agents use schema.org markup?

Many systems can read it, because it is a standard. But we cannot say that every agent does. Keep the same facts in your visible page text too.

Can structured data guarantee that I appear in AI answers?

No. It makes your data easier to read. Whether you appear depends on many other factors, such as relevance, trust and price.

How often should I check my markup?

Check after each theme, plugin or platform update, and test a few top products every month.

Clean product data, clean orders

Once the sale happens, the order needs a correct invoice. See what we build for EU stores.

See our products →