Strict microdata—Products

The product-page counterpart to strict catalogue markup. Marking a page with the Product schema, its offers property carrying an Offer or AggregateOffer, gives that data the highest priority when the robot crawls the page — above other sources Yandex might otherwise use.

What “priority” buys

Yandex draws product information from several places: the page itself, Yandex Market, submitted feeds. Where they disagree, strict microdata decides. That matters in two common situations — a Market feed that has drifted out of date, and a product whose details were taken from an aggregator rather than from you.

The structure

Product for the item, with offers containing:

• Offer for a single price.
• AggregateOffer for a range, where lowPrice produces a “from N” snippet.

The same conditions as ordinary product markup apply: one product per page — a page showing several yields no structured snippet — supported page language, and an availability value, since an out-of-stock offer suppresses the price.

The obligation that comes with priority

If your markup is authoritative, its errors are authoritative too. Yandex’s product rules are explicit that a site supplying low-quality or incorrect information through markup is banned from the partner programme and loses its structured snippets. Taking priority over other sources means accepting responsibility for being right.

How to implement it safely

Generate price, currency and availability from the same values that render on the page, never from a separate block a developer maintains by hand. Any arrangement where the two can diverge will eventually diverge, and the divergence is invisible until the snippet is already wrong.