<b>ProductGroup vs variesBy: the variant markup most catalogs get wrong</b>

<b>ProductGroup vs variesBy: the variant markup most catalogs get wrong</b>

Google formalized <code>ProductGroup</code> with <code>hasVariant</code> and <code>variesBy</code> so a parent product can declare its color/size axes while each variant carries its own <code>sku</code>, <code>gtin</code> and price. Most stores still publish 40 near-duplicate <code>Product</code> nodes and wonder why their snippets cannibalize each other.

The right shape — one <code>ProductGroup</code>, variants linked by <code>inProductGroupWithID</code>, and <code>variesBy</code> pointing at the literal property paths (<code>https://schema.org/color</code>). That tells the parser the relationship instead of making it guess.

What it means for you — consolidating variant markup cuts duplicate-content noise and gives Merchant listings a cleaner price range. It also stops AI shopping agents from treating one product as a dozen.

Watch this: variant-aware shopping results are expanding; flat catalogs get left behind.