Product Schema Generator

Product schema is structured data that describes a product for sale using Schema.org's Product type. It tells search engines exactly what you're selling by defining properties like the product name, description, brand, SKU, price, currency, availability, condition, and customer reviews in a standardized, machine-readable format.

The markup sits in a JSON-LD script tag on your product page. Search engines read it alongside your visible page content and use the data to generate rich results, sometimes called product snippets, that display key details like price, availability, and star ratings right in the search listing.

For ecommerce sites, product schema is one of the highest-impact types of structured data you can implement. It directly influences how your products appear in search results, Google Shopping, and Google's product knowledge panels.

Product rich results enhance your standard search listing with additional information pulled from your schema markup. The most common elements include star ratings with review counts, price or price range, availability status like "In Stock" or "Out of Stock," and sometimes the seller name.

These details appear below your page title and URL in the search listing. On mobile, they can be especially prominent, with colored price tags and bold availability badges that draw the eye immediately. For shopping-related queries, Google may also pull product schema data into dedicated shopping carousels and product knowledge panels that sit at the top of the results page.

The visual advantage is significant. A product listing with a 4.7 star rating, a visible price, and an "In Stock" label earns far more clicks than a plain blue link showing the same product. Searchers can evaluate your product at a glance before deciding whether to visit your page, which means the traffic you do get tends to be more qualified.

Product schema supports a wide range of properties, but some carry more weight than others when it comes to earning rich results and providing useful information to search engines.

Name. The product name as it appears on your page. Keep it clean and specific. "Men's Waterproof Hiking Boot - Size 10" is better than stuffing keywords into the name field.

Description. A concise summary of the product. This should match or closely reflect the description visible on your page. Don't use this field to stuff keywords or write marketing fluff that doesn't appear in the actual page content.

Brand. The manufacturer or brand name. This is a recommended property that Google uses to associate your product with a known brand entity, which can improve how your listing appears in branded searches.

SKU, GTIN, MPN. Product identifiers help search engines match your product to their product catalog. GTIN (Global Trade Item Number) is particularly valuable because it's a universal identifier used across retailers. If you have a UPC, EAN, or ISBN, those are all forms of GTIN. Including at least one product identifier significantly improves your chances of appearing in Google Shopping results.

Offers. This is where pricing and availability live. The Offer object nested inside your Product schema includes the price, currency (as an ISO 4217 code like USD or EUR), availability status, condition (new, used, refurbished), seller information, and valid date ranges for the price. At minimum, you need a price and currency for Google to display pricing in rich results.

Aggregate rating. If your product has customer reviews, include the aggregateRating property with the average rating value, the rating scale (usually 1 to 5), and the total number of reviews. This generates the star rating display in search results, which is one of the strongest visual drivers of click-through rate.

Images. Include at least one high-quality product image URL. Google recommends multiple images showing different angles. Images should be of the actual product, not lifestyle shots or graphics with promotional text overlaid.

The Offer property is a nested object within your Product schema that describes the terms under which the product is available for purchase. It's arguably the most important part of product schema because it contains the data searchers care about most, namely price and availability.

A basic Offer includes a price, priceCurrency, and availability. The availability value uses a predefined set of Schema.org options including InStock, OutOfStock, PreOrder, BackOrder, SoldOut, and OnlineOnly, among others. Google recognizes these values and maps them to the availability badges you see in search results.

If your product has multiple variants with different prices, like size or color options, you can include multiple Offer objects inside an offers array. Each offer represents a different variant with its own price, availability, and optional properties like SKU. This is common for clothing, electronics with storage tiers, and any product sold in multiple configurations.

For products with sale pricing, you can include both the regular price and the sale price, along with a priceValidUntil date that tells search engines when the discount expires. Google may display the original price with a strikethrough alongside the sale price in rich results, which is a strong visual incentive for searchers comparing options.

Reviews aren't required for product schema to be valid, but they're one of the most impactful properties you can include. Star ratings in search results consistently improve click-through rates, and products without ratings look less trustworthy sitting next to competitors that display them.

There are two ways to include reviews. The aggregateRating property shows the overall average rating and review count, which generates the familiar star display. The review property lets you include individual reviews with specific author names, review body text, and individual ratings.

Google has strict guidelines about review markup. The reviews must come from your own site, not imported from third-party platforms. They must be genuine reviews from real customers about the specific product on that page. Using fake reviews, importing reviews from other sites, or applying aggregate ratings from one product to a different product page can result in manual actions.

If you don't have reviews yet, it's better to leave the rating properties out entirely than to fabricate data. Focus on collecting genuine reviews through post-purchase emails, on-site prompts, or loyalty programs, and add the schema once you have real data to work with.

Product schema and Google Merchant Center serve overlapping but different purposes, and understanding the distinction helps you get the most out of both.

Product schema is structured data on your website that any search engine can read. It qualifies your pages for organic product rich results, the enhanced listings that appear in standard search results with pricing and ratings.

Google Merchant Center is a separate platform where you upload a product feed for Google Shopping. That feed powers the Shopping tab, free product listings, and paid Shopping ads. Merchant Center gives you more control over product data and is required for running Shopping ad campaigns.

The two work best together. Product schema on your pages improves your organic search listings. A Merchant Center feed expands your presence into Shopping results and ads. Google can cross-reference both data sources, and consistency between them strengthens the accuracy signals search engines look for.

If you're running an ecommerce site, implement product schema on your product pages and maintain a Merchant Center feed. They complement each other and cover different parts of the search landscape.

Yes. Products with variants like different sizes, colors, or configurations can be represented in a few different ways depending on how your site is structured.

Single page with multiple offers. If all variants live on one product page, include multiple Offer objects inside the offers array. Each offer can have its own price, SKU, availability, and identifying properties. This is the most common approach for products with minor variations.

Separate pages per variant. If each variant has its own URL, each page should have its own complete Product schema with a single Offer. You can use the isSimilarTo or isRelatedTo properties to link variant pages together, though Google doesn't currently use those for rich results.

Product groups. Schema.org has a ProductGroup type for products that share a common description but differ on certain properties. This is a newer approach that's gaining support but isn't yet widely used in rich results. For now, the multiple offers approach on a single page is the safest bet.

Inaccurate pricing. The price in your schema must match the price on your page at all times. If your prices change frequently due to sales, dynamic pricing, or currency conversion, your schema needs to update automatically. Google compares your markup against your visible content, and mismatches can cost you your rich results.

Using aggregate ratings with no real reviews. Don't add a 5-star aggregateRating based on zero or fabricated reviews. Google actively penalizes this. Only include ratings when you have genuine, verifiable customer reviews on your site.

Missing product identifiers. Leaving out GTIN, MPN, or SKU makes it harder for Google to match your product to its catalog. This can limit your visibility in Shopping results and product knowledge panels. If you have these identifiers available, always include them.

Applying product schema to non-product pages. Category pages, brand overview pages, and blog posts about products shouldn't use Product schema. The markup belongs on individual product pages where a single product is the focus and can be purchased. Google expects one clearly defined product per schema block.

Forgetting to update availability. A product marked as InStock in your schema but showing as sold out on the page creates a bad user experience and violates Google's guidelines. If your inventory changes frequently, make sure your schema generation is dynamic and reflects real-time stock status.

Not specifying currency. Including a price without a priceCurrency value makes the data ambiguous. Always include the ISO 4217 currency code. A price of "49.99" means nothing to a search engine without knowing whether that's USD, EUR, GBP, or something else.