Product Schema Generator
Build valid Product JSON-LD structured data for Google Shopping rich results. Include pricing, availability, brand, SKU/MPN/GTIN identifiers, and aggregated review ratings. Copy the <script> tag ready for your product page.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product"
}
</script>About Product Schema Generator
Product schema is required to appear in Google Shopping rich results — the star-rated product cards that show above regular search results for commercial queries. Without it, e-commerce products can rank in normal results but never in the shopping carousel where most conversions happen. This generator builds valid Product JSON-LD with pricing, availability, brand, product identifiers (SKU/MPN/GTIN), and aggregate ratings.
The tool converts availability status to the proper schema.org URL format (InStock, OutOfStock, PreOrder, etc.) automatically, includes required pricing fields for shopping results, and supports aggregate ratings when you have genuine reviews. GTIN (the barcode number) is the strongest identifier — Google prefers it for accurate product matching across sites. Add aggregate ratings ONLY when they reflect real customer reviews; fake or invented ratings can trigger manual actions from Google.
How to Use
Fill in the product name, description, image, and brand — the most important fields for shopping rich results.
Add at least one identifier (SKU, MPN, or GTIN). GTIN is the international barcode number; MPN is the manufacturer part number; SKU is your internal stock-keeping unit.
Set price, currency, and availability. The tool converts availability to the proper schema.org URL format automatically.
If you have real customer reviews, add aggregate rating (average) and review count. Do NOT fake reviews — Google penalizes fabricated ratings heavily.
Copy the <script> tag into your product page's <head>.
Frequently Asked Questions
Which product identifier should I use — SKU, MPN, or GTIN?
Use ALL that apply. GTIN (UPC/EAN/ISBN barcodes) is the strongest — Google prefers it. MPN (manufacturer part number) is the second strongest. SKU is your internal identifier and helps only if you sell the product yourself. For rich results, at least one identifier is required by Google's guidelines.
Can I use Product schema without price?
Yes for basic Product entity, but you will not get rich shopping results without an offers.price. If the product is out of stock or has no price yet, include the price anyway and set availability appropriately.
How do I add multiple offers from different sellers?
Replace the single 'offers' object with an 'offers' array of Offer objects — one per seller. Each offer can have its own price, currency, availability, and seller URL. This tool generates a single offer; edit the output for multi-seller scenarios.
Are review ratings required?
No — but they significantly boost click-through rate in search results by showing stars. Only include aggregateRating if you have real, verifiable customer reviews on the product page. Fake or invented ratings can trigger manual actions.
Business JSON-LD for Google Knowledge Panel and rich results.
Article/BlogPosting JSON-LD with author, publisher, and images.
Format, beautify, and validate JSON instantly.
Convert JSON arrays into CSV for spreadsheets.