Product Schema Generator
Fill in your product details and get valid schema.org Product structured data (JSON-LD), ready to paste into your page for rich results in Google and Google Shopping.
Product details
Generated output
<script type="application/ld+json">
{
"@context": "https://schema.org/",
"@type": "Product",
"name": "Wireless Noise-Cancelling Headphones",
"image": [
"https://example.com/images/headphones.jpg"
],
"description": "Over-ear Bluetooth headphones with active noise cancellation and 30-hour battery life.",
"sku": "ACM-WH-100",
"gtin13": "0614141999996",
"brand": {
"@type": "Brand",
"name": "Acme Audio"
},
"offers": {
"@type": "Offer",
"priceCurrency": "EUR",
"price": "199.99",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.6",
"reviewCount": "128"
}
}
</script>Paste this into the <head> of the matching product page. Validate with Google's Rich Results Test before publishing.
Test it in Google's Rich Results TestWhy Product schema markup matters
Structured data is how you tell search engines exactly what's on a page in a language they understand. For products, the schema.org/Product type, expressed as JSON-LD, captures the name, price, availability, brand, identifiers and ratings that power rich results.
When Google can read your product data confidently, it can show price and review stars directly in the search results and surface your products in free listings and the Shopping tab. Those richer listings stand out and typically earn a higher click-through rate than a plain blue link.
The catch is accuracy and coverage. Markup has to match the visible page, stay current as prices and stock change, and exist on every product, not just a handful. Hand-writing JSON-LD per product doesn't scale and drifts out of date the moment something changes.
WISEPIM generates and maintains structured data across your entire catalog from your real product information, so every page is eligible for rich results without manual upkeep. This free tool shows you what good markup looks like for a single product.
That's schema for one product.
WISEPIM generates valid, up-to-date structured data for every product in your catalog automatically, and keeps it in sync with your real prices, stock and reviews. No hand-editing JSON.
Related free tools
See all toolsPeople also search for
Frequently asked questions
What is Product schema markup?
Product structured data (schema.org/Product, written as JSON-LD) tells search engines the key facts about a product, name, price, availability, rating and more. Google uses it to show rich results with price and review stars, which can lift click-through from search.
Where do I put the generated JSON-LD?
Paste the full <script type="application/ld+json"> block into the <head> (or anywhere in the body) of the product page it describes. Each product page should have its own markup that matches the visible content exactly.
Which fields does Google require?
For a valid Product result Google needs name plus either an offer (price + availability), a review, or an aggregateRating. Adding brand, GTIN and image strengthens eligibility, especially for Google Shopping and free product listings.
Does the markup have to match the page?
Yes. Structured data must reflect the visible price, availability and reviews on the page. Mismatched or invented data (for example fake ratings) violates Google's guidelines and can trigger a manual action. WISEPIM generates accurate schema from your real product data across the whole catalog.
How do I test that my Product schema is valid?
Paste the page URL or the JSON-LD block into Google's Rich Results Test, which confirms the markup is parseable and lists any missing required or recommended fields. The Schema Markup Validator checks syntax against schema.org more broadly. Run a test after every change, valid markup is what makes a page eligible for rich results, though Google still decides when to show them.
JSON-LD, Microdata or RDFa, which format should I use?
Use JSON-LD. Google recommends it, it sits in a single script block instead of being woven through your HTML, and it is far easier to generate and maintain at catalog scale. Microdata and RDFa are still supported but mix markup into the page body, which is harder to keep correct. This tool outputs JSON-LD for that reason.