What is the minimum schema markup needed for a product to show a price in Google search results?

A Product schema with a nested Offer object containing at least three properties: price (the numeric price), priceCurrency (the ISO 4217 currency code, such as USD), and availability (a Schema.org URL such as https://schema.org/InStock). Without these three properties on the Offer object, price display is not eligible.

Does every product page on my site need its own schema?

Yes. Each product page should have its own Product schema with the specific name, image, price, and identifiers for that product. A generic schema on a category page does not associate structured data with individual products.

How do I include review stars in Google search results for my products?

Add an AggregateRating object nested inside your Product schema, with ratingValue, reviewCount, and bestRating properties. The rating data must match the visible rating on the page — Google's quality guidelines prohibit hidden or fabricated rating scores.

What is the correct format for the availability property in Offer schema?

Availability should be a Schema.org URL, not a plain text string. Use https://schema.org/InStock, https://schema.org/OutOfStock, or https://schema.org/PreOrder. Using the string InStock without the full URL is a common implementation error that passes basic validation but reduces reliability.

Can I use the same schema for a product with multiple variants (sizes, colors)?

For products with variants, each variant can be represented as a separate Offer with its own price and availability, or as a top-level Product with multiple Offer objects. The best approach depends on whether each variant has its own URL — if so, each should have its own Product schema on its own page.

My products have sales prices — how do I represent current price vs. original price in schema?

The Offer price property should reflect the current selling price. To show a sale, you can include both the current price (in price) and use priceValidUntil to indicate when the sale ends. Some implementations also use lowPrice and highPrice properties on AggregateOffer, but standard individual product pricing uses the single price property.

Does ecommerce schema affect Google Shopping tab appearances as well as organic search?

Yes. Google uses Product structured data both for organic rich results (star ratings, price in regular search) and as a signal for Google Shopping free listings. Accurate and complete product schema increases eligibility for both placement types.

What is a GTIN and do I need one for product schema?

A GTIN (Global Trade Item Number) is a standardized product identifier — barcodes on retail products are GTINs. Google recommends including a GTIN (gtin8, gtin12, gtin13, or gtin14) when one exists for your product. For products without manufacturer GTINs (custom, handmade, or private-label products), using sku or mpn instead is acceptable.

Can I add product schema to a Shopify store without coding?

Many Shopify themes include basic product schema by default. For more complete schema including AggregateRating and specific Offer properties, Shopify apps or theme customization may be needed to add properties the default theme omits.

Will product schema help my category pages rank better?

Product schema belongs on individual product pages, not category pages. Category pages are better served by CollectionPage or ProductCollection schema types. Adding Product schema to a category page that lists multiple products without individual product detail may produce validation errors.

How often should I update product schema to reflect price changes?

Product schema should be updated whenever the price or availability changes. A persistent mismatch between schema price and displayed price is a quality guideline violation that Google may act on. Automated schema generation that reads price data directly from your product database eliminates this synchronization problem.

What is the difference between the Product schema and the ItemList schema for ecommerce?

Product schema marks up an individual product page with its specific properties. ItemList schema marks up a list of products on a category or search results page, listing each item's URL and position in the list. Both have distinct use cases and are not interchangeable.

Schema Generator for Ecommerce

Which schema types ecommerce pages need, what properties Google requires for rich results, and how to implement them without validation errors

Ecommerce product pages require a different schema strategy than local business pages. The schema types that matter for product rich results — Product, Offer, and Review — each have specific required properties, and the relationship between them (an Offer is nested inside a Product, a Review is linked to the Product entity) must be correctly structured for Google's rich result eligibility.

The Three Schema Types Ecommerce Pages Need

Ecommerce product pages typically need three schema types working together. Product is the primary type and wraps the others — it carries the product name, description, image, and identifier properties. Offer is nested inside Product and carries the pricing information: price, priceCurrency (as an ISO 4217 code like USD, GBP, EUR), and availability (as a Schema.org URL like https://schema.org/InStock). AggregateRating is also nested inside Product and carries the overall rating information: ratingValue and reviewCount.

The nesting relationship matters. An Offer object defined outside the Product object, or defined as a sibling rather than a child, does not associate the price with the product. Google's structured data parser requires the offers property on the Product to contain the Offer — the structure is @type: Product, offers: { @type: Offer, price: ... }.

Required Properties for Google Shopping Rich Results

Google requires the following properties on the Product type for shopping rich result eligibility: name, image (a URL pointing to the product image), description, and at least one product identifier — either sku (your internal stock keeping unit), mpn (manufacturer part number), or a GTIN variant (gtin8, gtin12, gtin13, or gtin14). On the nested Offer object, Google requires price, priceCurrency, and availability.

The most common implementation errors are: missing the Offer block entirely (product shows in search without price), incorrect priceCurrency format (using $ instead of the ISO code USD), and unavailability mismatch (schema says InStock but the page shows out of stock, which Google detects and may penalize).

Review and AggregateRating Implementation

AggregateRating enables the star rating display in Google search results. It requires ratingValue (a numeric value between 0 and 5), reviewCount (the total number of reviews used to calculate the aggregate), and bestRating (typically 5). Google's policy requires that the rating data on the schema matches the rating display visible to users on the page — a hidden or fabricated rating score violates Google's structured data quality guidelines.

Individual Review objects can be included in a reviews array on the Product. Each Review requires author (as a Person or Organization object), reviewBody (the text of the review), and datePublished. Review markup is optional but provides additional signals for schema richness.

Ecommerce Schema Types — Required vs. Optional Properties

Properties marked Required must be present for rich result eligibility. Optional properties add rich result features but do not affect base eligibility.

Schema Type	Required Properties	Optional High-Value Properties
Product	name, image, description, sku or mpn or gtin	brand, color, material, category
Offer (nested in Product)	price, priceCurrency, availability	priceValidUntil, seller, shippingDetails
AggregateRating (nested in Product)	ratingValue, reviewCount	bestRating, worstRating
Review (in reviews array on Product)	author, reviewBody, datePublished	reviewRating, name (review headline)

Schema Generator for Ecommerce

The Three Schema Types Ecommerce Pages Need

Required Properties for Google Shopping Rich Results

Review and AggregateRating Implementation

Ecommerce Schema Types — Required vs. Optional Properties

Sources & Further Reading

Frequently Asked Questions

Request a Custom Tool