Product schema generator. Rich-result eligible.
Fill 14 fields, get copy-ready Product JSON-LD that matches Google's Product rich-result required fields. Includes offers (price, currency, availability), brand, GTIN, SKU, aggregateRating. Inline validator on every keystroke.
Dedicated Product schema generator. Fill the form on the left; the right panel renders rich-result-eligible JSON-LD with offers, aggregateRating, brand, and identifiers. Inline validator runs on every keystroke. No fetch, no log.
Sources used by this generator
- schema.org/Product · /Offer · /AggregateRating
- Google Product rich-result spec + merchant listing
- ISO-4217 currency codes · GTIN/UPC/EAN identifier formats
Generation runs entirely in JavaScript on your device. No JSON is sent to any external service.
Privacy: form runs in-browser only. Your inputs never leave the device.
Two rich results. One schema.
Product rich result. The classic — price, availability, and a star rating shown directly under the title in the SERP. Eligibility requires name, image, description, offers (price + priceCurrency), and either GTIN or MPN. The aggregateRating block is optional but adds the visible star count, which is what drives the CTR uplift. Studies routinely report 30-90% CTR lift on product pages with the rich result vs without.
Merchant listing experience. The expanded format — Google Shopping organic listings (free since 2020), Knowledge Panel Shopping carousel, image-search overlays. Eligibility requires GTIN (Global Trade Item Number — UPC, EAN, ISBN, JAN), shipping cost in offers, and return-policy structured data. The standard Product rich result above is a strict subset; if your product has GTIN, set it and Google routes the page through the merchant pipeline automatically.
Identifier hierarchy: GTIN beats MPN beats SKU. GTIN is globally unique across retailers — the same product sold by Amazon, Walmart, and your store should have the same GTIN. MPN is manufacturer-side. SKU is your internal stock-keeping unit. Including all three you have gives Google maximum signal to disambiguate your product from competitors.
aggregateRating discipline. Self-serving aggregateRating without real visible reviews is prohibited by Google's structured-data policy and risks a manual-action that removes ALL rich results across the site. The rule: aggregateRating must reflect real reviews on the same page (or aggregated from those visible reviews). If you don't have reviews yet, leave the field empty rather than fabricate it. Build a review program first; add the schema when the visible reviews are real.
availability values use the schema.org URL form: https://schema.org/InStock, /OutOfStock, /PreOrder, /BackOrder, /Discontinued, /SoldOut. The bare enum (just "InStock") is older and still works but the URL form is canonical per current schema.org spec.
Six questions users ask.
What does Product schema unlock?
The Google Product rich result: price + availability + star rating shown directly in the SERP. Studies consistently report a 30-90% CTR lift for product pages with the rich result vs without. The schema also feeds Google Shopping (free organic listings since 2020), Knowledge Panels, and AI shopping assistants. Without it, your product page ranks but doesn't get the visual badges that drive click-through.
Are GTIN, SKU, and MPN really needed?
GTIN (Global Trade Item Number — UPC, EAN, ISBN, etc.) is required for the merchant-listing rich result and strongly recommended for the standard Product rich result. MPN (Manufacturer Part Number) is the fallback when no GTIN exists. SKU is your internal stock-keeping unit and is always optional from Google's standpoint but useful for analytics tagging. Including all three gives Google maximum signal to disambiguate your product from competitors selling the same item.
Can I include aggregateRating without real reviews?
No. Google's structured-data spam policy prohibits self-serving aggregateRating that doesn't reflect real customer reviews on the page. The rating must come from reviews visible on the same page (or an aggregated rating computed from those visible reviews). Submitting fake or aggregated-from-elsewhere ratings risks a manual structured-data action that removes ALL rich results across the site. If you don't have reviews yet, leave the aggregateRating fields empty.
What availability values are valid?
Schema.org URL form: https://schema.org/InStock, OutOfStock, PreOrder, BackOrder, Discontinued, SoldOut. The generator outputs the URL form, which Google requires. Some older docs show the bare 'InStock' enum value, but the URL prefix is the canonical form per current schema.org spec.
What about price and priceCurrency?
Price must be a numeric string (no currency symbol — that's what priceCurrency is for). priceCurrency must be a 3-letter ISO-4217 code: USD, EUR, GBP, INR, etc. Decimals are allowed (49.99). For products with variant prices, use lowPrice and highPrice in an AggregateOffer instead of a single Offer; this generator covers the common single-price case.
Does this tool log my product data?
No. The form runs entirely in JavaScript on your device. Nothing is sent to Digital Heroes servers. No signup, no email, no analytics beacon includes the product data.
Schema cluster.
Article Schema Generator
Article / BlogPosting / NewsArticle.
Review Schema Generator
Review + AggregateRating JSON-LD.
Structured Data Validator
Validate any JSON-LD.
Schema Markup Generator
Multi-type — 6 schemas in one tool.
Shopify development
Product schema baked into theme.
SEO service
Schema + technical + content.