Product Schema Generator — Free JSON-LD for E-commerce

Build valid Product structured data with price, brand, SKU, availability, and ratings. Eligible for Product rich results and Google Shopping.

🛍️Product Schema

Fields marked with * are required for valid schema markup.

JSON-LD Output

<span class=400">"text-gray-500">&lt;script type=400">"application/ld+json"&gt;</span>
{
  400">"@context": 400">"https://schema.org",
  400">"@type": 400">"Product",
  400">"offers": {
    400">"@type": 400">"Offer",
    400">"priceCurrency": 400">"USD",
    400">"availability": 400">"https://schema.org/InStock"
  }
}
<span class=400">"text-gray-500">&lt;/script&gt;</span>

Copy this code and paste it into the <head> section of your HTML page.

What is Product Schema Markup?

Product schema is the Schema.org type used to mark up sellable items on a website. It tells Google, Bing, and other search engines that the page describes a specific product — not a category page, blog post, or marketing page — and conveys the structured properties they need to render Product rich results: name, image, brand, price, availability, SKU, GTIN, and review data.

Implemented in JSON-LD format inside a <script type="application/ld+json"> tag, Product schema is a prerequisite for appearing in Google's Shopping experiences, Product Knowledge Panels, and merchant listings. It is one of the highest-impact schema types for any e-commerce store.

Why Product Schema Matters

  • Rich results with price and stock: Pages with Product schema can show price, currency, and "In stock" / "Out of stock" badges directly in Google search results, lifting CTR significantly over plain blue-link competitors.
  • Google Shopping eligibility: Free Google Shopping listings (organic, not paid) require Product schema. Without it your products will not appear in the Shopping tab regardless of how many backlinks the page has.
  • Review stars in search: Pages with a valid aggregateRating nested in Product schema can display star ratings, which can lift CTR by 20-30% on competitive queries.
  • Merchant listing experiences: Mobile Search increasingly uses Product schema to render expandable product cards with image, price, and shipping info — completely changing how users interact with your listing.
  • Comparison Shopping Services (CSS): In EU markets, CSS providers rely on Product schema to surface your inventory at retail-equivalent prices.

Product Schema Properties Explained

Required Properties

  • name: The product name as it appears on the page. Should match your H1 tag. Avoid promotional language ("BEST" / "SALE!"); use the descriptive name.
  • offers (with price): A nested Offer object containing price, priceCurrency, and availability. Without Offer, Google considers the markup incomplete for rich results.

Strongly Recommended Properties

  • image: Absolute URL to a high-quality product image (1200×1200 or larger preferred). Multiple images can be provided as an array — the first is treated as primary.
  • description: A clear description of the product, typically matching your meta description or the lead paragraph on the page.
  • brand: Nested Brand object with name. Critical for branded search and Google's product identity matching.
  • sku: Your internal stock-keeping unit. Used by Google to deduplicate when the same product appears on multiple URLs.
  • gtin / mpn: Global Trade Item Number (UPC/EAN/ISBN) or Manufacturer Part Number. Required for Google Shopping merchant listings.
  • aggregateRating: Nested object with ratingValue and reviewCount only if you have genuine first-party reviews.

Availability Values

The availability field uses Schema.org URLs, not plain text. Common values:

  • https://schema.org/InStock — currently sellable
  • https://schema.org/OutOfStock — temporarily unavailable
  • https://schema.org/PreOrder — accepting orders before release
  • https://schema.org/Discontinued — no longer sold
  • https://schema.org/BackOrder — accepting orders, expected to fulfill later

Step-by-Step Implementation

Step 1: Confirm This Is a Product Page

Product schema belongs only on individual product detail pages (PDPs). Do not add it to category listings, search results, or the homepage. For listing pages, use ItemList or CollectionPage instead.

Step 2: Gather Required Data

Before using the generator, have ready: product name, current price (without currency symbol — just the number), three-letter currency code (USD, EUR, GBP, CNY, JPY, etc.), stock status, product image URL, brand name, SKU, and any verified review aggregate.

Step 3: Generate and Copy the JSON-LD

Use the form above to fill in your product data. The generator emits valid JSON-LD as you type. Copy the script tag and paste it into your page's <head> or anywhere in the document body — both are accepted by Google.

Step 4: Validate

Test your live URL in Google's Rich Results Test. Look for "Eligible for Product snippets". Fix any warnings (especially missing recommended fields like gtin) before deploying widely.

Step 5: Monitor in GSC

Google Search Console's Enhancements section has a dedicated "Merchant listings" and "Product snippets" report. Monitor weekly for impression and click counts, and fix any errors flagged.

Product Schema Best Practices

  • Keep price as a string in JSON-LD: "price": "29.99", not a number with currency symbol.
  • Use ISO 4217 three-letter currency codes (USD, EUR, GBP) — never symbols.
  • Mark up only the canonical product URL — duplicate Product schema across URL variants causes confusion.
  • Update availability dynamically when stock changes. Stale "InStock" on actually out-of-stock items can trigger manual actions.
  • For variants (size, color), use the ProductGroup + hasVariant pattern, not multiple separate Product schemas.
  • Include brand even for generic items — use your store name as the brand if no manufacturer brand exists.
  • Use gtin13 for EAN-13 barcodes (most common globally), gtin12 for UPC-A (North America), or gtin14 for shipping containers.

Common Mistakes to Avoid

  • Adding Product schema to category or search result pages — only use on individual product pages.
  • Including the dollar sign or other currency symbol inside the price field.
  • Fabricating reviews to populate aggregateRating — this violates Google's structured data policy and risks manual actions.
  • Using free-text availability ("In stock!") instead of the Schema.org URL value.
  • Missing the offers wrapper — price and currency must be nested inside Offer, not at the Product root.
  • Adding multiple Product schemas to a single PDP for variants — use ProductGroup or a single Product with size/color attributes instead.

Frequently Asked Questions

What is Product schema markup?

Product schema is structured data that tells Google your page describes a sellable item. It conveys properties like price, currency, availability, brand, SKU, and review ratings so search engines can show Product rich results in Search and Google Shopping.

Do I need Product schema for every product page?

Yes. Every individual product detail page (PDP) should have its own Product schema with the unique price, SKU, and availability. Category and search result pages should not use Product schema on individual items — use ItemList instead.

What's the difference between Product schema and Offer schema?

Product is the item itself (name, brand, image). Offer is the commercial offer to sell it (price, currency, availability, URL). Google requires Offer nested inside Product for rich results. Our generator handles the nesting automatically.

Can I use Product schema for digital products or services?

For digital products (software, ebooks, downloads), Product schema works fine. For services, use the Service type instead — Google treats services and products differently in rich results.

How do I add aggregateRating without fake reviews?

Only include aggregateRating if you collect genuine first-party reviews on your site. Faking ratings is a Google policy violation that can trigger a manual action. If you don't have reviews, omit the rating fields — the schema is still valid.

Will Product schema guarantee rich results?

No structured data guarantees rich results — Google decides based on page quality, schema validity, and content match. But pages without Product schema can never be eligible. Schema is necessary, not sufficient.

Related Schema Generators

Try our AI tools

✍️

Quilliam

AI-powered story generator — create novels chapter by chapter

Try Quilliam →
🎨

MyInk AI

Generate unique tattoo designs with AI in seconds

Try MyInk →