Variant information missing from structured data

What it detects

A product with multiple purchasable options (size, color, style) has no hasVariant / additionalProperty structure describing them.

Why it matters

Agents need each purchasable variant addressable with its own SKU and price; collapsing variants into a single undifferentiated Product hides real choices and can lead an agent to buy the wrong option.

How to fix

- Check the Product JSON-LD for a product whose page shows multiple options (size, color, material, style) — look for `hasVariant` or `additionalProperty` in the schema. - If the product has multiple purchasable variants, restructure the JSON-LD as a `ProductGroup` with a `hasVariant` array of `Product`/`ProductModel` entries, each with its own `sku` and `offers`. - For simple attribute-only differences (not separately purchasable), add `additionalProperty` (`PropertyValue`) entries instead. - Verify: confirm each variant surfaced in the UI has a corresponding entry in `hasVariant` (or `additionalProperty`) with matching price/availability.

References

• schema.org
• JSON-LD 1.1 (W3C)