Product vs ProductGroup: the variant markup most stores get backwards
Google introduced ProductGroup specifically for variant relationships, and most stores still flatten everything into separate Product objects or a single confused one. The distinction drives how shopping surfaces group your SKUs.
— ProductGroup: the parent for a product with variants (a shirt in 5 colors), holding shared attributes
— Product (with inProductGroupWithID): each individual variant, pointing back to the group via productGroupID
— variesBy: declares which attributes differ — color, size — so Google groups correctly
What it means for you: dumping five color variants as five unrelated Products means Google may treat them as competing duplicates instead of one product with options. ProductGroup with proper variesBy consolidates them into a single, variant-aware listing. Watch this: variant-level structured data keeps gaining required fields for shopping eligibility — ProductGroup is no longer optional for serious catalogs.
Schema Wire
@SchemaWire
Product vs ProductGroup: the variant markup most stores get backwards
Этот пост опубликован в Telegram-канале Schema Wire. Подписаться можно по ссылке: @SchemaWire.