Schema · Free

Free Product Schema Generator

Generate Product schema with offer pricing, availability, identifiers (SKU, MPN, GTIN), and condition fields. Schema.org-compliant JSON-LD ready to paste into your product page head.

  • No signup, no email required
  • Works entirely in your browser
  • Output you can copy and paste directly
  • Built by a working SEO team, not gated by upsells

Product details

Output

JSON-LD
// Add at least name and price to generate.
Open Rich Results Test

What it does

Product schema is the structured-data type for individual products for sale — physical goods, digital downloads, software, subscriptions. It tells Google and other search engines about your product's name, image, price, availability, and identifying codes (SKU, MPN, GTIN). The output qualifies your product page for product rich results in Google search and Google Shopping.

This generator produces a complete Product object with a nested Offer for pricing, schema-compliant enum values for availability and condition, and optional brand / identifier fields. Hand-formatting Product JSON-LD is error-prone (wrong availability URLs, missing Offer wrapper, malformed price format) — this tool handles all of that for you.

Why Product schema still matters

Product schema remains one of the highest-leverage structured-data types in 2026. The reasons:

  • Product rich results. Pages with valid Product schema can earn the dedicated product card in Google search — image, price, rating, availability all shown directly in the SERP. Users click these at higher rates than plain blue-link results.
  • Google Shopping eligibility. Product schema is part of the Merchant Center feed equivalence — products marked up well can appear in Shopping results without a paid feed.
  • AI Overview product comparisons. When users search for product comparisons, AI Overview pulls structured pricing and availability directly from Product schema. Pages without it get summarized but not cited.
  • Voice commerce. Voice assistants surfacing products read availability and price directly from structured data. No schema = no voice surface.

How to use this generator

  1. Add the product name and price. The two strictly required fields. Price as a plain number ("49" not "$49").
  2. Add an image URL. Fully-qualified URL pointing to the primary product image. 1200×1200 or larger renders best in product rich results.
  3. Set availability and condition. Use the schema.org enum URLs from the dropdowns — these are structured values Google requires. "In stock / New" is the default for most cases.
  4. Add identifiers if you have them. SKU is your internal code. MPN is the manufacturer part number (for physical products). GTIN is the universal product code — UPC, EAN, ISBN. Including these is optional but helps Google Shopping match your product to existing entities.
  5. Set price valid until. Required by Google for sale prices. For non-sale ongoing pricing, set to a distant future date.
  6. Copy the output into the <head> of your product page. Validate with the Rich Results Test.

Product schema best practices

  • Availability must match reality. If the page shows "in stock" but the schema says "out of stock" (or vice versa), Google penalizes the rich result eligibility.
  • Price must match the visible price. Mismatch is one of the most common reasons products lose their rich result. Update both whenever you change pricing.
  • Use priceValidUntil for sales. Required by Google for sale prices. Without it, Google may stop showing the discounted price after a few weeks.
  • Include identifiers when you have them. GTIN especially helps your product map to known catalog entries in Google Shopping.
  • One Product per page. Variant products (color, size) need ProductGroup or separate URLs. Stacking multiple Product objects on a single URL fails validation.
  • Pair with Review or AggregateRating only when real. Adding fake review data is one of the fastest paths to a manual action. If you have third-party reviews on Trustpilot, G2, etc., pull from there.

Frequently asked questions

What's the minimum required for valid Product schema?

Product name and price (inside an Offer). Everything else is optional but recommended. Image, availability, and condition strongly improve rich-result eligibility.

Why is the availability field a URL?

Schema.org availability values are enums expressed as URLs — https://schema.org/InStock, https://schema.org/OutOfStock, etc. The full URL is the spec; abbreviated forms (just 'InStock') sometimes work but the full URL is safer.

Should I add reviews to my Product schema?

Only if you have real reviews on the page itself. Self-serving fake reviews are explicitly banned by Google's structured-data guidelines and risk a manual action that removes ALL rich results from your site. If you have third-party reviews (Trustpilot, G2), mark those up with proper attribution.

What's the difference between SKU, MPN, and GTIN?

SKU is your internal product code — invented by you, used in your inventory system. MPN is the manufacturer's part number — used for OEM parts and physical components. GTIN is the universal barcode (UPC in North America, EAN in Europe, ISBN for books). Include whichever you have; GTIN is most valuable for Google Shopping mapping.

Do I need separate Product schema for each variant?

For variants that differ in price, image, or availability — yes, ideally on their own URLs with their own schema. For purely cosmetic variants (color of a same-priced item), one Product with multiple offers can work but is harder to validate. The cleanest pattern is one URL per variant.

What if my product is a digital download or service?

Product schema works for digital and service offerings too. Set itemCondition to NewCondition (digital products are always 'new'), include availability as InStock, and set priceValidUntil for any sale pricing.

Will this tool log my data?

No. Everything runs in your browser. The fields you fill never leave your device — there is no server endpoint and nothing to log.