Product schema: how to mark up product pages

Google describes two experiences.

name, image with several crawlable images, description, brand, sku, and a global identifier such as gtin or mpn where one exists. offers as an Offer with price, priceCurrency, availability using schema.org values such as InStock, url, and priceValidUntil for time-limited prices. Add aggregateRating and review only for genuine product reviews visible on the page. Retailers should add shipping and return policy details or configure them in Merchant Center.

For products with variants such as size or colour, Google supports ProductGroup with hasVariant listing each Product variant, and variesBy naming the varying properties. Each variant can have its own offer and identifiers. If each variant has its own URL, mark up each page with its variant; if variants are selected on one page, include them in the ProductGroup on that page.

For software, SoftwareApplication, or WebApplication, usually describes the product better than Product, with applicationCategory, operatingSystem, and offers for pricing. serionflow.com uses SoftwareApplication with an offer describing plans. Do not mark up subscription tiers with invented reviews or ratings; only use aggregateRating where genuine user ratings are visible on the page.

Test with the Rich Results Test and monitor Search Console's Product snippets and Merchant listings reports. Keep price and availability in sync with the page; mismatches can cause listings to be disapproved or ignored. Generate markup from the same data that renders the page, never by hand for each product. Our free schema builder generates Product and SoftwareApplication JSON-LD and checks live pages. SerionFlow is the wrong tool for e-commerce product markup; it is built for SaaS pages, and your store platform handles product data.