Product schema

What it does for AI citation

Shopping questions are among the most common things people ask assistants, and an answer naming products needs price and availability it can trust. Unmarked prices force the model to scrape them out of prose, which it does unreliably and sometimes wrongly.

A working example

Paste this into a <script type="application/ld+json"> tag in your page head and replace the values. It is valid as written.

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example Widget",
  "image": ["https://example.com/widget.jpg"],
  "description": "What it is and who it is for, in a sentence.",
  "sku": "EW-001",
  "brand": { "@type": "Brand", "name": "Example Co" },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/widget",
    "priceCurrency": "USD",
    "price": "49.00",
    "availability": "https://schema.org/InStock"
  }
}

What actually goes wrong

These are the errors that show up repeatedly on real sites, in rough order of how often we see them.

• A price that disagrees with the price rendered on the page. This is the single most common structured-data error and it is a trust problem, not a formatting one.
• price as '$49' instead of '49.00' with priceCurrency separate. The symbol belongs in priceCurrency.
• availability as the word 'In stock' rather than the schema.org URL.
• Inventing aggregateRating for a product with no real reviews. Fabricated ratings are a manual-action risk and the reason Google tightened this in the first place.

Markup is necessary, not sufficient

Valid Product does not buy you a citation. It makes your page legible, which is the precondition. Whether an assistant names you when a buyer asks also turns on your content, how current the page is, and who else on the web corroborates you. Any tool that tells you markup alone will get you cited is overselling.

Other types