What is Product schema and why does it matter?

Product schema (technically Product JSON-LD per schema.org) is a structured data markup that tells Google, Bing, and other search engines explicit facts about a product on your page — name, price, currency, availability, brand, GTIN, ratings, reviews. When properly implemented, it enables rich results in Google's SERPs: star ratings, price displays, "in stock" badges, and product carousels. Google's 2025 search-feature data shows pages with valid Product schema earn 28% more clicks than pages without, even at the same SERP position. Beyond Google Search, Product schema feeds Google Shopping (free product listings since 2020), Bing Shopping, and AI search engines like Perplexity that cite structured data sources. For ecommerce, Product schema is a baseline requirement, not a nice-to-have. As of 2026, Google has begun deprioritizing pages that submit product data via Merchant Center but lack matching JSON-LD on the canonical product page — the two must be consistent for full rich-result eligibility.

What's the difference between JSON-LD, Microdata, and RDFa?

These are three formats for embedding the same Schema.org structured data into a webpage. JSON-LD is a separate block in the HTML head or body, parsed independently from the visible content. Microdata uses inline HTML attributes (itemprop, itemscope, itemtype) that mix structure with markup. RDFa uses similar inline attributes but with a different attribute syntax. Google explicitly recommends JSON-LD as the preferred format since 2017, and it's now used by 89% of structured-data-enabled pages per Web Almanac 2025. JSON-LD's advantages: (1) cleanly separated from visible markup, (2) easier to inject dynamically via JavaScript, (3) doesn't require restructuring HTML to add structured data, (4) maintainable independently from design changes. Microdata still works but ages poorly; RDFa is rarely used outside academic and government sites. Our generator outputs JSON-LD only — paste it into your page as a block.

What fields are required for Product schema rich results?

Google's 2026 Product rich-result requirements list these as required: name (the product title), and at least one of either offers (price information) or aggregateRating or review. To earn the full rich snippet (with stars, price, and availability), you need: name, image (1+ high-quality URLs), offers.price, offers.priceCurrency (ISO 4217 like "USD"), offers.availability ("https://schema.org/InStock", "OutOfStock", "PreOrder", etc), offers.url, aggregateRating.ratingValue, aggregateRating.reviewCount, review.author, review.reviewRating, review.reviewBody. Recommended-not-required fields: brand, sku, gtin/gtin13/mpn, description, color, size, material. The 2024 Google update strict-requires offers.url and offers.priceValidUntil for time-sensitive pricing; missing those triggers a Search Console warning even if the rich result appears initially. Test your schema with Google's Rich Results Test (search.google.com/test/rich-results) before deploying.

How do I add reviews and ratings to Product schema?

Add aggregateRating for the overall star rating across all reviews, and individual review objects for each user review you want to display. Format: aggregateRating: { "@type": "AggregateRating", ratingValue: "4.7", reviewCount: "342", bestRating: "5", worstRating: "1" }; then review: [{ "@type": "Review", author: { "@type": "Person", name: "Jane Doe" }, reviewRating: { "@type": "Rating", ratingValue: "5" }, reviewBody: "Excellent product, exactly as described." }]. The reviews displayed must be verifiable on the page itself — Google's 2024 Reviews & Ratings policy explicitly requires the schema to match what users actually see on the page. Don't include ratings or reviews you haven't actually collected. Don't use third-party-only ratings (Trustpilot, Yelp) without first-party reviews on the page; Google penalizes mismatch. Aggregate ratingValue should be at least 4 reviews, and the math should add up — a "4.8 from 247 reviews" claim should be defensible from the actual reviews you display.

Should the Product schema match my Google Merchant Center feed?

Yes, exactly. Google's 2025 Merchant Center policy requires schema and feed consistency for "free product listings" and Google Shopping ads. Mismatched price, availability, or product identifier between the two will trigger account-level warnings and gradual deprioritization. The best practice is to treat the JSON-LD on your product page as the source of truth, then derive your Merchant Center feed (XML, CSV, or Content API) from the same data layer. Use the same SKU or ID, the same GTIN, the same priceCurrency, the same availability status. When you change a price or run a sale, both must update simultaneously — usually within 30 minutes. Stale feeds that say "$29" while the page shows "$24 (sale)" are the most common warning in Merchant Center diagnostics. Tools like ChannelAdvisor, GoDataFeed, and Rule-based feeds in Shopify Markets handle the sync automatically; for custom platforms, build the schema and feed from the same product database query.

Can I have multiple Product schemas on a single page?

Yes — for category or collection pages with multiple products, use an ItemList wrapper containing multiple Product nodes, or a series of independent Product JSON-LD blocks. Google supports both patterns. ItemList is preferred for SERP carousel eligibility (the "Best of" or "Top picks" rich result format). Independent Product blocks work for editorial roundup content like "Best Linen Aprons of 2026" — Google will cite individual products from the structured data even on listicle-style pages. Don't add 50+ products in a single ItemList; cap at 10-15 to avoid bloating the page. Also avoid adding Product schema to product-search results pages (e.g., /shop?color=blue) — those are dynamic and have stale-cache risk. Apply Product schema to canonical product detail pages and curated landing pages only. Google Search Console will flag duplicate Product schemas across multiple URLs without canonical signals as a structured data error.

What is GTIN, MPN, and SKU and which do I need?

GTIN (Global Trade Item Number) is the universal product identifier — UPC (12 digits, North America), EAN (13 digits, EU), ISBN (books), ASIN (Amazon proprietary). MPN (Manufacturer Part Number) is the brand-assigned SKU. SKU (Stock Keeping Unit) is your internal warehouse identifier. Google's 2025 schema guidance prefers GTIN for Merchant Center integration; if your products don't have GTINs (most handmade or custom products), use MPN + brand. Provide all three when available. The format: gtin13: "0012345678901" (13-digit, leading zeros preserved as a string), mpn: "ACME-MUG-12OZ-SAGE", sku: "MUG-001". Don't fabricate GTINs — Google validates against authoritative GS1 databases. For products without manufacturer GTINs, the GS1 organization sells them ($300+/year company prefix); only required if you sell on Amazon or major marketplaces. For DTC ecommerce, MPN + brand is sufficient.

How does Product schema interact with Google Shopping?

Product schema is the foundation for Google Shopping organic listings (free since 2020) and ads. Your product detail page schema feeds the Shopping tab when Google's crawler visits it; if a Merchant Center feed exists, both signals are used together. The Merchant Center feed offers richer attribute coverage (color, size variants, age group, gender, condition) but the on-page schema must remain consistent. For pages without a Merchant Center feed, well-formed Product schema alone can earn Google Shopping organic placement, though the visibility is generally lower than with a feed. The 2025 Google Shopping update added "Product Studio" image generation for sellers; that feature uses the Product schema as a starting point. Beyond Google, Bing Shopping, Pinterest Product Pins, and Facebook Catalog all consume similar structured data. Set up the schema once, syndicate everywhere.

Should I include offers.priceValidUntil for sales?

Yes for any time-bounded pricing. Google's 2024 update made priceValidUntil effectively required for sales, deals, and limited-time offers — without it, the rich result may strip the sale price and show only regular pricing. Format: priceValidUntil: "2026-05-15" (ISO 8601 date, end of validity). Once the date passes, your schema must update to either remove priceValidUntil or extend it; stale priceValidUntil values trigger Search Console warnings. For evergreen pricing without a sale period, omit the field entirely (don't use 9999-12-31 as a placeholder — Google flags that pattern). Combine with priceSpecification for more complex pricing structures: tiered pricing, recurring subscriptions, member-only pricing. Subscription products benefit from offers: { "@type": "Offer", priceSpecification: { "@type": "UnitPriceSpecification", price: "29.00", referenceQuantity: { "@type": "QuantitativeValue", value: "1", unitCode: "MON" } } }.

How often should I validate my Product schema?

Run Google's Rich Results Test on a sample of product pages monthly, and review Search Console Structured Data reports weekly. Key metrics: warnings (require fixing for full eligibility), errors (block rich results entirely), and trend in valid items count (sudden drops indicate widespread breakage from a deploy). Google's 2025 schema policy changes are announced in the Search Central blog roughly every 90 days; subscribe and review changes against your current implementation. Common breakage patterns: a developer updates the product detail template and accidentally hard-codes an old price into the schema, causing site-wide mismatch with the live price. Or a third-party Shopify app injects competing schema that conflicts with your custom JSON-LD. Or a CMS migration drops the block entirely. Monitoring tools: Search Console (free), DeepCrawl, OnCrawl, Sitebulb (paid). Set up alerts for >5% error-rate spikes.

Do I need Product schema for digital products and SaaS?

For SaaS, use SoftwareApplication schema instead of Product (or in addition). For digital downloads (ebooks, courses, templates), Product schema is appropriate with offers, name, image, description. The key fields adapt: instead of physical-product attributes (color, weight), digital products use fileFormat, fileSize, contentSize. Subscription SaaS pricing fits SoftwareApplication's offers field with priceCurrency and price; for tiered pricing, use multiple Offer nodes. Google's rich-result eligibility for SaaS is more limited than for physical goods — you won't earn a star rating from the Search SERP for SoftwareApplication unless reviews are also marked up, and the rich snippet appears less consistently for software than for physical products. For courses, use Course schema (a different type) with name, provider, description, hasCourseInstance. Each schema type has its own SERP feature surface; pick the type that matches what you're actually selling.

How does this compare to Yoast, RankMath, or Schema App?

Yoast SEO ($99-449/year for the premium tier with structured data) auto-generates Product schema on WordPress for WooCommerce stores, with reasonable defaults. RankMath (free for basic, $59-499/year for premium) does the same with broader configurability. Schema App ($25-300/mo) is enterprise-focused with a visual schema builder and audit features. Our generator is free, produces clean JSON-LD output you paste into any framework (Next.js, Webflow, Shopify, plain HTML), and exposes all the optional fields most plugins skip — gtin variants, multiple offer prices, aggregateRating with reviewCount, individual reviews. We don't auto-update when product data changes (it's a one-time output you paste into your template), and we don't sync with Merchant Center. For a single landing page or static product page, our tool is fastest. For a 5,000-product Shopify or WooCommerce catalog with dynamic pricing, the auto-generating plugins are worth the cost; pair them with our tool for special landing pages or campaign-specific schemas.

Free Product Schema Generator

Generate Product JSON-LD schema for ecommerce SERP rich results. Price, reviews, availability. Free, instant.

4.6on G2

4.8on Trustpilot

Used by 25,000+ marketers

Product Name

Image URL

Description

Brand

ID Properties

sku

gtin8

gtin13

gtin14

mpn

Aggregate Rating

Aggregate rating value

Number of ratings

Highest value allowed

Lowest value allowed

Offer Type

JSON-LD Schema

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "",
  "image": [],
  "description": ""
}

What this tool does

Product Schema Generator delivers fast, reliable results for generate product json-ld schema for ecommerce serp rich results. price, reviews,.

Designed to fit into your existing SEO and content workflow with no setup overhead.

How to use it

Five steps.

Enter product details

Provide product name, description, image URL, brand, SKU, GTIN/MPN, and category — these populate the required Product schema fields.

Add pricing and availability

Enter price, currency (USD/EUR/GBP), availability (InStock/OutOfStock/PreOrder), and priceValidUntil for sales.

Add ratings and reviews

Optionally add aggregate rating, review count, and individual review snippets — must match what's actually displayed on the page.

Generate JSON-LD

Click Generate to produce a clean JSON-LD block ready to paste into your page <head>.

Validate and deploy

Test via Google's Rich Results Test (search.google.com/test/rich-results), paste into your page, and monitor Search Console for warnings.

When teams use it

Six common workflows.

Shopify store earning Google rich snippets

A direct-to-consumer Shopify store with 200+ products needs valid Product schema with reviews, GTINs, and Merchant Center alignment to earn star-rating SERP results and free Shopping organic placements driving 28%+ more clicks.

Etsy seller migrating to a custom site

A handmade goods seller moving from Etsy to a custom Webflow or WooCommerce site needs Product schema with MPN (no GTINs for handmade), aggregateRating built from imported Etsy reviews, and proper offers.priceCurrency for international buyers.

Affiliate publisher running product roundups

A product roundup blog ("Best Linen Aprons of 2026") needs ItemList wrapper with individual Product nodes for each linked product, helping Google generate the carousel rich result and driving outbound affiliate clicks from search.

B2B SaaS marketing landing pages

A B2B SaaS marketing team building campaign landing pages for a flagship product (using SoftwareApplication or Product schema) needs structured data that surfaces in Google's sidebar knowledge panel and AI overview citations.

Ecommerce migrating off WooCommerce/Shopify

An ecommerce team rebuilding on a headless stack (Next.js + Sanity, Astro + Stripe) needs hand-rolled Product schema for each product detail page, dynamically generated from the CMS data with all the rich fields the SaaS plugins normally provide.

Marketplace operator displaying multiple sellers

A marketplace platform listing products from 50+ sellers needs Product schema per listing with seller as part of the offers field (offers.seller), distinguishing each seller's pricing and availability while maintaining a unified product entity.

Platform guides

Integrate with major platforms.

Next.js / React

Generate the JSON-LD in Grigora's tool.
In your product page component, render the schema as <script type="application/ld+json" dangerouslySetInnerHTML={{ __html: JSON.stringify(schema) }} />.
Place it inside <Head> from next/head (Pages Router) or in the <head> of layout.tsx (App Router).
Validate via Google Rich Results Test before deploying.
Monitor Search Console > Enhancements > Products for warnings.

Shopify (theme.liquid)

Open Online Store > Themes > Edit Code.
Locate templates/product.liquid or sections/product.liquid.
Add a {% schema %} block with the generated JSON-LD, replacing static values with Liquid variables (product.title, product.price, etc).
Save and preview.
Validate via Google Rich Results Test on a live product URL.

WordPress (WooCommerce)

Use Yoast SEO Premium or RankMath for auto-generated Product schema (recommended).
For custom schema, paste the JSON-LD into a Custom HTML block on the product template via the theme builder.
Disable the plugin's native schema if running both, to avoid duplicate-schema errors.
Validate via Google Rich Results Test.
Confirm appears in Search Console > Enhancements > Products within 7-14 days.

Webflow

Open the product page template in Designer.
Go to page settings > Custom Code > Inside <head> tag.
Paste the generated JSON-LD wrapped in <script type="application/ld+json">.
For dynamic CMS pages, replace static values with CMS field references using Webflow's embed system.
Publish and validate.

Plain HTML / Static Site Generators (Astro, 11ty)

Generate the JSON-LD per product page.
Add to the page <head> as <script type="application/ld+json">{ ... }</script>.
For static site generators, template the schema using the page's frontmatter or data file.
Build the site and verify the schema is included in the rendered HTML.
Validate each product URL via Google Rich Results Test.

Grigora vs. alternatives

Side-by-side.

Capability	Product Schema Generator	Yoast SEO	RankMath	Schema App	Manual
Free tier available	Yes — unlimited	Premium only ($99+/yr)	Free + premium	No	No
JSON-LD output (preferred format)	Yes	Yes	Yes	Yes	Yes
All optional fields exposed (GTIN/MPN/etc)	Yes	Limited	Yes	Yes	Yes
Aggregate rating + review nodes	Yes	Yes	Yes	Yes	Yes
Auto-sync with product database	No (manual)	Yes (WooCommerce)	Yes (WooCommerce)	No	Yes
Visual schema builder	No (text input)	No	Limited	No	Yes
Pricing for solo founder	Free	$99-449/yr	Free or $59-499/yr	Free + paid	$25-300/mo
Works outside WordPress	Yes (any framework)	No	No	Yes	Yes

Common errors and fixes

Eight issues users hit.

Schema price doesn't match displayed price

Cause: Schema was hard-coded with old price, then sale was applied to the page CSS.

Fix: Generate schema dynamically from the same data layer that renders the visible price; never hard-code prices in JSON-LD.

Missing offers.priceValidUntil for sale pricing

Cause: Used a sale price in the schema without the validity end date.

Fix: Add priceValidUntil with the sale end date in ISO 8601 format; remove the field once the sale ends.

Reviews schema with no visible reviews on page

Cause: Marked up aggregate ratings from a third-party platform that aren't shown on the page itself.

Fix: Either display the reviews on the page (matching the schema) or remove the schema; Google penalizes phantom-review markup.

Invalid GTIN format

Cause: Stripped leading zeros from GTIN-13 by storing as integer.

Fix: Store GTINs as strings preserving leading zeros; validate against GS1 length rules (8, 12, 13, or 14 digits).

Multiple conflicting Product schemas on same page

Cause: A Shopify app injected its own schema in addition to the theme's native schema.

Fix: Audit which schemas are present (View Source > search "application/ld+json"), disable the redundant one in the app settings.

Schema in <body> instead of <head>

Cause: Pasted JSON-LD inside the page content without specifying location.

Fix: Either location works for Google; <head> is preferred. Confirm the script tag is properly closed and not inside a <p> or other text element.

Aggregate rating math doesn't add up

Cause: Claimed "4.8 from 247 reviews" but only 12 reviews exist on the page.

Fix: Make the aggregateRating reflect actual review count and be defensible from displayed data; Google audits.

Mismatched currency between schema and Merchant Center

Cause: Schema uses "USD" but Merchant Center feed uses "EUR" for the same SKU.

Fix: Pick one source of truth (usually the schema) and align all downstream feeds; Merchant Center will warn on mismatch.

Original data

2026 study.

+28%

Click uplift for pages with valid Product schema vs without

89%

Pages using JSON-LD vs Microdata in 2025

Minimum review count Google displays in star rating snippet

14 days

Default Search Console deprioritization for stale priceValidUntil

Frequently asked questions

Twelve answers.

Related free tools

Other utilities.

Try Product Schema Generator now

Free, unlimited, no signup.

Try the Tool