Supported schemas from Schemaorg

Product information

Ask AI about this page

2 min read

Product markup is what produces a price-bearing snippet in Yandex results. It needs two schemas working together: Product plus either Offer for a single price or AggregateOffer for a range. Marking up Product alone produces nothing.

The required fields

  • name (Text) — on Product.
  • description (Text) — on Product.
  • price (Number) on Offer, or lowPrice on AggregateOffer. With lowPrice, the snippet reads “from N” — which Yandex recommends where price varies by size, volume or configuration.
  • priceCurrency (Text) — an ISO 4217 code, on either offer type.

Conditions that decide whether a snippet appears at all

  • One product per page. A page showing different products produces no structured snippet. Category and listing pages are therefore not candidates, however well marked up.
  • Language must be Russian, English, Belarusian, Ukrainian, Turkish, Tatar or Kazakh.
  • Availability. If availability on the Offer says the product is out of stock, the price is not displayed.
  • If you are in the Yandex Market partner programme, the snippet shows the price from Yandex Market, not from your markup.

The clause with teeth

Yandex reserves the right to use the marked-up data or not, in whole or in part, in any of its services, and accepts no responsibility for the accuracy of what appears. More importantly: a site found to be supplying low-quality or incorrect information through markup is banned from the partner programme and loses its structured snippets.

That turns price accuracy into a search-visibility issue rather than a customer-service one. Markup that drifts out of step with the checkout — a stale price, an availability flag never updated, a currency left at the template default — is the exact failure mode this rule punishes.

Practical implementation

Generate the markup from the same data source that renders the visible price, never as a separate template block. Any arrangement in which someone could update one without the other will eventually diverge, and the divergence is invisible until the snippet is already wrong.

Alien Road

So setzen wir das um

We wire product markup to the same field that prints the price on the page, and we check availability is genuinely dynamic — a hardcoded InStock is the most common defect we find, and it is precisely the “incorrect information” the partner-programme ban is written for. The one-product-per-page rule is worth stating early too, because clients routinely ask for category pages to be marked up and no snippet is possible there.

Verwandte Leistungen

Teilen

© Copyright 2026 Alien Road. All rights reserved.