Product schema: complete guide

When to use: E-commerce product detail pages and variants you want eligible for product rich results.

Required properties

name — Product name visible on the page
image — Product image URL(s)
description — Human-readable description

Optional properties

brand — Brand as Brand or Organization
sku — Merchant SKU
gtin — GTIN8/12/13/14 when available
offers — Offer with price, currency, availability

Example JSON-LD

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example LED Desk Lamp",
  "image": [
    "https://www.example.com/lamp.jpg"
  ],
  "description": "Adjustable LED desk lamp with USB charging port.",
  "sku": "LAMP-001",
  "offers": {
    "@type": "Offer",
    "priceCurrency": "USD",
    "price": "49.99",
    "availability": "https://schema.org/InStock",
    "url": "https://www.example.com/products/lamp"
  }
}

Validation tips

Price and currency must match visible offer on the product URL
Use AggregateRating/Review only with compliant, visible reviews
Avoid marking up out-of-stock items as InStock

Overview

Product is the core type for PDPs. Google expects Offer (or aggregate offers) to align with what users see, including price, currency, and availability.

Combine with Review cautiously—self-serving reviews have strict policies. Use SEWWA to generate a baseline graph, then map your catalog fields.

Try the free Schema Generator →