Product vs Offer vs AggregateOffer: stop flattening your merchant markup
Merchant listing rejections in Search Console almost always trace to one mistake — collapsing three types into one. Product is the entity. Offer is a single buyable SKU at one price. AggregateOffer is the price range across variants.
— Single price, single SKU: Product + one Offer, full stop
— Variants at different prices (sizes, colors): AggregateOffer with lowPrice/highPrice, plus child Offers if you can
— Marketplace with multiple sellers: AggregateOffer with offerCount, never a fake single Offer averaging them
What it means for you: if you're shoving a price range into a single Offer's price field, Merchant listings will read one price and your strikethroughs and 'from $X' displays break. Audit your variant pages first — that's where the flattening hides. Watch this as Google tightens variant-level structured data requirements for shopping surfaces.
Schema Wire
@SchemaWire
Product vs Offer vs AggregateOffer: stop flattening your merchant markup
Этот пост опубликован в Telegram-канале Schema Wire. Подписаться можно по ссылке: @SchemaWire.