Free Product Schema Markup Generator — JSON-LD Product Structured Data
Generate Google-valid Product schema markup with Offer, AggregateRating, Reviews, GTIN, MPN, shipping, and return policy. Live Google rich result SERP preview. Completeness score showing rich result eligibility. 5 product templates. Dark code editor. No signup. No watermark.
Rate this tool
Why this beats ContentPowered, iLoveSchema, LetStartDesign, and Infidigit
How to generate Product schema markup in 3 minutes
LazyTools vs other free product schema generators
| Feature | LazyTools | ContentPowered | iLoveSchema | LetStartDesign | SearchSavvy | Infidigit |
|---|---|---|---|---|---|---|
| Live Google SERP preview | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| Completeness score | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| Sale price + priceValidUntil | ✅ Yes | ❌ No | ❌ No | ✅ Yes | ❌ No | ❌ No |
| Shipping details schema | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| Return policy schema | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| Individual reviews UI | ✅ Yes | ❌ No | ❌ No | ❌ No | ✅ Basic | ❌ No |
| GTIN / MPN / SKU fields | ✅ All 3 | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Partial |
| Rich result target selector | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| Pre-built templates | ✅ 5 | ❌ None | ❌ None | ❌ None | ❌ None | ❌ None |
| Download .json file | ✅ Yes | ❌ No | ❌ No | ❌ No | ✅ Yes | ❌ No |
| Dark code editor | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No | ❌ No |
| No signup required | ✅ Never | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
Product Schema Markup Guide — JSON-LD Implementation for Google Rich Results & Google Shopping
Product schema markup is one of the highest-ROI technical SEO changes available to e-commerce sites. Listings with star ratings, price, and availability displayed in search results achieve 82% higher click-through rates than standard blue links, according to SEMrush's 2025 research. Yet 68.7% of websites have no schema markup at all. For an e-commerce site selling 100 products, implementing complete Product schema across every product page can be the difference between flat blue links and rich product listings that immediately communicate value to potential customers before they even visit your site.
Product Snippets vs Merchant Listings — The Critical Distinction
Google offers two distinct types of Product rich results, and most guides conflate them. Product Snippets appear in standard web search results below your page title. They can show star ratings, review counts, price, and availability. To qualify, you need the product name property plus at least one of: review, aggregateRating, or offers. Merchant Listings appear in the Google Shopping tab, Shopping carousels, and product comparison panels. They require stricter data: offers with price, priceCurrency, and availability, plus at least one product identifier (gtin, mpn, or sku). Shipping details and return policy are strongly recommended for Merchant Center eligibility. Know which type you are targeting before implementing — the field requirements are different.
Required vs Recommended Product Schema Properties
For Product Snippets, Google's minimum requirement is name plus one of review, aggregateRating, or offers. In practice, always include all three — they each add visible elements to your rich result and collectively maximise the information Google can show. For Merchant Listings, add offers.price, offers.priceCurrency, offers.availability, and at least one identifier. The recommended properties that go beyond the minimum include: description (used in rich result descriptions), image (shown in product carousels), brand (used in product knowledge panels), offers.condition (new/used/refurbished), offers.shippingDetails, and hasMerchantReturnPolicy.
Product Identifiers — GTIN, MPN, and SKU
Product identifiers are how Google matches your product to its global product catalog and to other retailers selling the same item. GTIN (Global Trade Item Number) is the most valuable identifier — it is a universal standard used across retailers worldwide. Common GTIN formats include UPC (12 digits, North America), EAN (13 digits, Europe), and ISBN (for books). If your product has a barcode, that barcode number is your GTIN. Include it using the gtin property in your schema. MPN (Manufacturer Part Number) is the identifier the manufacturer uses to identify the product. Combined with brand, MPN uniquely identifies a product in Google's catalog even without a GTIN. SKU is your own internal identifier — less useful for catalog matching but still recommended for Merchant Center data accuracy.
For products you manufacture yourself (where there is no universal GTIN), use mpn plus brand together. Google treats brand plus MPN as a reliable identifier for products that do not have GTINs in the global catalog. For digital products, services, or custom-made items, GTIN and MPN may genuinely not apply — SKU is sufficient in these cases.
AggregateRating Schema — Getting Stars in Search Results
The aggregateRating property is what enables star ratings in Google search results. It requires: ratingValue (the average rating), and either reviewCount or ratingCount (or both). reviewCount is the number of reviews with written text. ratingCount is the total number of ratings including those without text. If you have 500 star ratings but only 120 with written reviews, use ratingCount: 500 and reviewCount: 120.
Google has strict content guidelines for aggregateRating: ratings must come from genuine customers reviewing the specific product on that page. Never include fabricated ratings, never import ratings from third-party platforms, and never reuse ratings from a different product. Google actively detects and penalises sites that use fake or imported ratings, resulting in manual actions that remove rich result eligibility from all product pages. If you do not yet have ratings, leave the property out entirely — an absent rating is better than an invalid one.
Shipping Details and Return Policy — The Often-Missed Properties
Shipping and return policy schema are among the most underimplemented properties in product markup, yet Google increasingly uses them for Merchant Center eligibility and shopping result filtering. The shippingDetails property (type: OfferShippingDetails) should include: shippingRate (the shipping cost as a MonetaryAmount, or 0 for free shipping), shippingDestination (the countries you ship to as DefinedRegion), and deliveryTime (a ShippingDeliveryTime with handlingTime and transit time ranges in business days).
The hasMerchantReturnPolicy property (type: MerchantReturnPolicy) should include: returnPolicyCategory (the policy type), merchantReturnDays (the return window in days), returnMethod, and returnFees. Google uses this data to populate shopping filters like "free returns" and "30-day returns" that users increasingly rely on to filter product results. Implementing these properties can meaningfully improve your Merchant Listing visibility.
Product Schema for WooCommerce and Shopify
Both WooCommerce and Shopify generate basic Product schema automatically, but both have significant gaps that limit rich result eligibility. Shopify's Dawn theme generates name, description, image, and offers with price and availability. What's missing: aggregateRating, gtin, mpn, shipping details, and return policy. WooCommerce with Yoast SEO generates similar basics but also omits shipping and return policy. Use this generator to create a supplementary JSON-LD block with the missing properties, then add it to your theme's product template or via a custom HTML block.
The simplest WordPress implementation method is adding the JSON-LD in a Custom HTML block in the Gutenberg editor on each product page. For programmatic implementation across all products, use the wp_head action hook in functions.php to dynamically generate the schema from WooCommerce product data using the Woo Product API. For Shopify, paste the JSON-LD into the product.liquid or product-template.liquid file, using Liquid variables to populate the dynamic values from product data.
Product schema markup — questions answered
Product schema markup is JSON-LD structured data that tells search engines about your product: name, description, price, availability, brand, identifiers, ratings, and reviews. When correctly implemented, Google can display rich results showing star ratings, price, and availability directly in search results, improving click-through rates by up to 82%.
Product Snippets appear in standard web search results and need name plus review, aggregateRating, or offers. Merchant Listings appear in Google Shopping, requiring offers with price/priceCurrency/availability plus at least one identifier (GTIN, MPN, or SKU). Shipping and return policy are recommended for Merchant Listings.
GTIN is the barcode number (UPC, EAN, or ISBN) - most valuable for catalog matching. MPN is the manufacturer's part number - use with brand to identify products without a GTIN. SKU is your internal identifier. For own-brand products without a universal GTIN, use brand + MPN. For digital products, SKU alone is sufficient.
No. Google's guidelines are explicit: reviews must come from genuine customers reviewing the specific product on that page. Never use fabricated ratings, import reviews from third-party platforms, or reuse ratings from different products. Violations result in manual actions removing rich result eligibility. If you have no reviews yet, leave aggregateRating out entirely.
Google uses shipping and return policy data for Merchant Center eligibility, shopping result filters ("free returns", "ships in 3-5 days"), and to display trust signals in product carousels. Most tools ignore these properties, making them a competitive advantage. Free shipping and a clear return policy also reduce bounce rates from product pages.
LazyTools Product Schema Generator is 100% free. No signup, no account, no credit card. Generates complete JSON-LD with Offer, AggregateRating, Reviews, GTIN/MPN/SKU, shipping, return policy, and sale price. Live Google SERP preview, completeness score, 5 templates, dark editor, JSON download. Entirely browser-based.