Product Schema (JSON-LD) Generator

Paste your product details into the form and get a ready-to-copy application/ld+json script block. The generator builds a valid schema.org/Product object with nested Offer and AggregateRating, omitting any blank field so your markup stays clean. Drop the output into your product page's <head> to unlock Google product snippets and Merchant Center rich results.

Offer (pricing)
Aggregate Rating (optional)

How to use the Product Schema (JSON-LD) Generator

Fill in the product fields, then click Generate (or use the live update as you type). Fields left blank are automatically omitted from the output — no null values pollute your markup.

  1. Name — required. The exact product name customers would search for.
  2. Image — required for rich results. Use a high-quality image hosted on your domain. At least 600 px wide; Google prefers 3:2 or 16:9.
  3. Description — recommended. A plain-text product description (no HTML inside the property).
  4. Brand & SKU — recommended for Merchant listings. SKU is your internal catalog number; GTIN is the barcode.
  5. Offer block — set price, currency (ISO 4217 code, e.g. USD, EUR, GBP), and availability. Price valid until tells crawlers when the price expires; Google may suppress the snippet after that date.
  6. Aggregate Rating — only included when Rating value is non-empty. Google requires a review count alongside the rating value. At least 1 review; Google filters out ratings with very few reviews.
  7. Copy the output block and paste it into your page's <head>, or pass it to your CMS/template engine.

What is Product schema and what does it unlock?

Product schema (schema.org/Product) is structured data that tells Google's crawlers exactly what a page sells — its name, price, availability, brand, and customer ratings. When Google processes this markup, it can display product snippets in organic results (star ratings, price, availability shown directly under the blue link) and feed data into Google Merchant Center free listings and the Shopping Graph. These rich results consistently outperform plain blue links in click-through rate because buyers get the key decision data without clicking through.

Google's documentation distinguishes required from recommended properties. For a basic product snippet, name, image, and either offers or aggregateRating are required. For Merchant Center listings Google additionally expects sku, gtin, brand, and a complete offers block including priceValidUntil. GTIN is especially important: it lets Google match your listing to its product knowledge graph, which can significantly boost visibility.

JSON-LD (JavaScript Object Notation for Linked Data) is Google's preferred implementation format. Unlike microdata or RDFa, JSON-LD lives in its own <script> tag and never touches the visible HTML, so it is easy to add, maintain, and validate without redesigning the page. Paste the generated block anywhere in the <head> or at the end of <body> — Google processes both equally.

Common use cases

  • E-commerce product pages — add a JSON-LD block to every product page to unlock price and star-rating snippets in Google Search, increasing click-through rates vs. bare organic results.
  • Merchant Center free listings — provide GTIN, brand, and a complete Offer block so Google can surface your products in Shopping tabs without paid ads.
  • Price-comparison aggregators — third-party scrapers and comparison engines that read schema.org data will automatically pick up your pricing, reducing the need for separate data feeds.
  • Limited-time offers — set Price valid until to a sale end-date; Google will suppress the outdated price snippet after expiry so your listing stays accurate.
  • Pre-order campaigns — set availability to PreOrder and a future price-valid date to signal upcoming product launches to the Shopping Graph before inventory is live.
  • Review aggregation — when your page aggregates third-party reviews, surface the average rating and count via AggregateRating to show stars in the SERP without needing individual Review objects.

Frequently asked questions

Which fields are required for Google product snippets?
Google requires at minimum: name, image, and at least one of offers (with price and availability) or aggregateRating. Pages missing these will not be eligible for the rich result.

Does the Product schema replace a Google Merchant Center feed?
No — but it supplements it. Schema.org markup on your product pages enables free product listings in Search. A Merchant Center feed (via Google Merchant Center or a Shopping app) is still needed for Shopping ads and more granular inventory control.

What GTIN format should I use?
Use whatever barcode format your product carries: GTIN-8, GTIN-12 (UPC), GTIN-13 (EAN), or GTIN-14. Pass the full numeric string, zero-padded to its standard length. Google maps all of them to the same knowledge-graph entity.

Why is my product snippet not appearing in Search?
Common reasons: the page is not indexed, required fields are missing, the price or availability is incorrect/stale, or Google has not yet recrawled since you added the markup. Use Google Search Console's Rich Results Test and URL Inspection tools to diagnose.

Can I put multiple Product blocks on one page?
Google supports only one primary Product entity per page. If your page is a product listing (multiple items), use a different schema type such as ItemList, or ensure each product has its own dedicated URL with its own Product block.