What Is Product Schema? The Complete Guide (2026)

Product Snippets vs. Merchant Listings — Two Different Rich Results

Google supports two separate rich result types for Product schema, each with different eligibility requirements. Understanding the difference is essential because you may qualify for one and not the other.

If you run an e-commerce store where users can buy directly, target Merchant Listings — that's the shopping carousel that drives the highest-intent commercial traffic. If you run a review or comparison site, target Product Snippets. Google notes that adding the full Merchant Listings properties also makes pages eligible for Product Snippets, so e-commerce sites benefit from implementing both.

Required Properties

Based on Google's Product structured data documentation, these properties are required. Missing any one of them is a hard error that prevents rich results:

Recommended Properties

These properties don't block basic eligibility, but they significantly improve rich result quality, AI citation accuracy, and Merchant Listings eligibility:

How to Structure the Offer Object

The offers property is the most commonly misconfigured part of Product schema. Greadme validates every field inside Offer— here's what each one means:

Full Implementation Example

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Wireless Noise-Cancelling Headphones",
  "image": [
    "https://example.com/headphones-1x1.jpg",
    "https://example.com/headphones-4x3.jpg",
    "https://example.com/headphones-16x9.jpg"
  ],
  "description": "Premium wireless headphones with 30-hour battery and active noise cancellation.",
  "brand": {
    "@type": "Brand",
    "name": "SoundPro"
  },
  "sku": "SP-ANC-300",
  "gtin13": "4901234567890",
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.6",
    "reviewCount": "312"
  },
  "offers": {
    "@type": "Offer",
    "url": "https://example.com/products/headphones",
    "priceCurrency": "USD",
    "price": "149.99",
    "priceValidUntil": "2026-12-31",
    "availability": "https://schema.org/InStock",
    "itemCondition": "https://schema.org/NewCondition"
  }
}

"offers": {
  "@type": "Offer",
  "priceCurrency": "USD",
  "price": "149.99",
  "availability": "https://schema.org/InStock",
  "itemCondition": "https://schema.org/NewCondition",
  "shippingDetails": {
    "@type": "OfferShippingDetails",
    "shippingRate": {
      "@type": "MonetaryAmount",
      "value": "0",
      "currency": "USD"
    },
    "shippingDestination": {
      "@type": "DefinedRegion",
      "addressCountry": "US"
    },
    "deliveryTime": {
      "@type": "ShippingDeliveryTime",
      "handlingTime": {
        "@type": "QuantitativeValue",
        "minValue": 0,
        "maxValue": 1,
        "unitCode": "DAY"
      },
      "transitTime": {
        "@type": "QuantitativeValue",
        "minValue": 3,
        "maxValue": 5,
        "unitCode": "DAY"
      }
    }
  },
  "hasMerchantReturnPolicy": {
    "@type": "MerchantReturnPolicy",
    "applicableCountry": "US",
    "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
    "merchantReturnDays": 30,
    "returnMethod": "https://schema.org/ReturnByMail",
    "returnFees": "https://schema.org/FreeReturn"
  }
}

"offers": {
  "@type": "AggregateOffer",
  "lowPrice": "129.99",
  "highPrice": "189.99",
  "priceCurrency": "USD",
  "offerCount": "5"
}

The 8 Most Common Product Schema Mistakes

How Product Schema Affects AI Visibility

AI shopping assistants and search engines (ChatGPT Search, Perplexity, Google AI Overviews) parse Product JSON-LD to extract structured facts before reading prose. When answering queries like "what are the best noise-cancelling headphones under $200?", they pull:

• name — to identify and name the product in the response
• offers.price + priceCurrency — to compare prices across products without guessing from prose
• aggregateRating.ratingValue — to rank or recommend products based on user satisfaction
• brand.name — to attribute the product to a recognized manufacturer
• offers.availability — to filter out out-of-stock items from purchase recommendations

Industry data from 2025 shows pages with complete Product schema achieve 30–40% higher AI citation rates compared to product pages without structured data. For e-commerce sites, this translates directly to more product mentions in AI-generated shopping guides and buying recommendations.

How to Validate Your Product Schema

The fastest way to validate Product schema is to run your URL through Greadme. Greadme checks every field in the Product and Offer objects — including price format, currency codes, availability values, aggregateRating structure, reviewer name validity, and SKU format — and gives you a scored report with actionable fixes. It also tells you separately whether you qualify for Product Snippets and Merchant Listings.

FAQ

Is Product schema required for Google Shopping?

For organic Merchant Listings (the free shopping results), yes — Product schema with a valid Offer is required. For paid Google Shopping ads, product data is managed through Google Merchant Center, not structured data. Both channels can benefit from the same Product schema implementation.

Can I use Product schema for a service instead of a physical product?

No. Product schema is specifically for tangible goods and downloadable products. For services, use Service schema or a more specific type like LocalBusiness.

Do I need shippingDetails for Product schema to work?

Not for basic eligibility — shippingDetailsis optional. However, Google requires it for full Merchant Listings eligibility in the US, Canada, Australia, and most European markets. Without it, Google Search Console shows a "merchant listing experience" warning and the product may not appear in the shopping carousel.

What's the difference between Offer and AggregateOffer?

Offer represents a single seller's offer at a specific price. AggregateOffer represents a price range across multiple sellers (use lowPrice, highPrice, and offerCount). UseAggregateOffer on comparison or marketplace pages. Use Offer when you are the seller and want Merchant Listings eligibility.

Can I have Product schema and AggregateRating without any reviews on the page?

No. Any rating in your schema must reflect ratings that are visible to users on the page. Adding aggregateRatingwith no visible reviews on the page violates Google's structured data guidelines and can trigger a manual action for spammy structured data.

How do I mark up a product with variants (colors, sizes)?

For product variants, use ProductGroup schema with individual Product objects for each variant linked via hasVariant. Each variant needs its own sku or gtin, a variant-specific image, and an offers.url that deep-links directly to that variant.

Should Product schema go on every page of my e-commerce site?

Apply it on individual product pages and product variant pages. Do not apply it on category pages, search result pages, or the homepage — those should use ItemList or WebPageschema instead. Applying Product schema to non-product pages confuses Google's classifier.