Visora
Sign up
Back to news

· News

Schema.orgStructured dataProduct

Schema.org ProductGroup update clarifies variant modeling for AI parsers

The Schema.org community release notes for September 2025 refined ProductGroup modeling guidance—how merchants connect parent products, variants, and offers so parsers (including AI crawlers) understand SKU families without treating each color swatch as an unrelated entity.

What merchants should implement

  • ProductGroup with hasVariant pointing to Product nodes per SKU
  • Consistent name patterns: base product name plus variant attributes in structured fields, not only in titles
  • Shared FAQ at group level with variant-specific specs in child Product nodes
  • Offer linkage per variant with accurate price and availability

Why AI surfaces care

Comparison prompts ("compare sizes", "which color has better battery") require entity graphs. Flat Product markup without grouping produces duplicate or conflicting citations in merchant test panels run after the schema update.

Common mistakes

  • Only parent URL marked up; variants lack individual Product JSON-LD
  • hasVariant URLs that 404 or redirect break group integrity
  • FAQPage attached only to parent while sizing answers differ by variant

Visora angle

Visora audit flags ProductGroup completeness on Shopify and headless stacks. After implementing group graphs, re-run audit and Monitor prompts for multi-variant comparison intents within fourteen days—typical window for recrawl and re-citation in industry notes.

Source: Schema.org release notes, September 2025.

Go deeper

News tells you what changed. Our blog explains how to adapt schema, FAQs, and measurement.

Visit the GEO Knowledge Hub

https://geovisora.com/en/news/schema-org-product-group-update