What ProductGroup does
ProductGroup is a schema.org type for a set of products that differ only in a few attributes, such as size or colour. Each variant is still a Product with its own SKU, price and availability. The group ties them together and says which attributes vary. Google documents this as product variant structured data for merchant listings; see Google’s product variants guide.
A complete example
A T-shirt sold in two sizes and two colours. The example uses placeholder URLs and values.
{
"@context": "https://schema.org",
"@type": "ProductGroup",
"name": "Organic cotton T-shirt",
"url": "https://example.test/products/tee",
"brand": { "@type": "Brand", "name": "Example" },
"productGroupID": "TEE-01",
"variesBy": ["https://schema.org/size", "https://schema.org/color"],
"hasVariant": [
{
"@type": "Product",
"sku": "TEE-01-S-BLK",
"name": "Organic cotton T-shirt, small, black",
"size": "S",
"color": "Black",
"image": "https://example.test/img/tee-black.jpg",
"offers": {
"@type": "Offer",
"url": "https://example.test/products/tee?variant=s-black",
"price": "25.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
}
},
{
"@type": "Product",
"sku": "TEE-01-M-WHT",
"name": "Organic cotton T-shirt, medium, white",
"size": "M",
"color": "White",
"image": "https://example.test/img/tee-white.jpg",
"offers": {
"@type": "Offer",
"url": "https://example.test/products/tee?variant=m-white",
"price": "25.00",
"priceCurrency": "USD",
"availability": "https://schema.org/OutOfStock"
}
}
]
}
The properties that matter
productGroupID: the parent ID, often the parent SKU. Keep it stable; if your product feed has an item group ID, use the same value.variesBy: the attributes that change between variants, as schema.org URLs such ashttps://schema.org/sizeandhttps://schema.org/color.hasVariant: the list of variantProductobjects. Each one carries the attribute values named invariesBy.- Variant
offers: price, currency and availability belong on each variant, because they can differ. - Variant identifiers:
skuand, where you have one,gtin, so the variant can be matched to your feed.
If each variant has its own page, a variant page can instead mark up a single Product and point back with isVariantOf or inProductGroupWithID. Pick one pattern per site and use it consistently.
Common mistakes
- Prices in the markup that differ from the page. The price and availability shown to shoppers must match the markup for the selected variant.
- Variant URLs that all return the same content. If
?variant=URLs do not preselect the variant, use the one product URL and rely on the variant list. - Attributes named in
variesBybut missing on variants. Every variant should carry a value for each varying attribute. - A ProductGroup with one variant. A single item is a
Product, not a group. - Markup that disagrees with the product feed. Different IDs, prices or availability between the page and Merchant Center can cause disapprovals.
Check it
Run the page through Google’s Rich Results Test to confirm the markup parses as merchant listing data, and check the Merchant listings report in Search Console after Google recrawls. Shipwork’s free audit reads the structured data on sampled product pages and flags missing price, availability and identifier fields, and the schema generator builds starter JSON-LD you can adapt.
Shipwork reads the structured data on sampled product pages and flags variants missing price, availability or identifiers. Free, no account, no signup. Paste your store address.
Generate structured dataQuestions
What is ProductGroup schema?
Do I need ProductGroup if each variant has its own URL?
Does ProductGroup markup guarantee rich results?
Keep reading