Elements description

The full property set Yandex reads from an hRecipe page, including several extensions that are not part of the open standard.

General requirements

One recipe per page, marked with the hrecipe root class, and that recipe must be the main content of the page. It must be fully displayed and visible to visitors — nothing hidden behind a tab or a collapsed panel.

Required

• fn — the dish name, plain text.
• ingredient — every ingredient marked individually, as text or HTML. Nested: name (a Yandex extension), type and value for unit and quantity, or amount for a free-form quantity instead of those two.

Recommended

• instructions — one per recipe; individual steps may carry instruction (a Yandex extension). Yandex asks that the heading itself, “Cooking method”, stay outside the property.
• yield — portions, one per recipe, text value.
• duration — ISO 8601. The value-title pattern displays “an hour and a half” while publishing PT1H30M.
• photo and result-photo — several photos allowed, at the root or inside instructions, taking the src of an img. The finished-dish image must additionally carry result-photo, a Yandex extension, and it is the single field that most improves the snippet.
• author — text, or a nested hCard, and several are allowed.
• nutrition — with Yandex’s own nested properties: calories, fat, saturatedFat, unsaturatedFat, carbohydrates, sugar, fiber, protein, cholesterol, servingSize.

Further Yandex extensions

category (dish type, one per recipe), sub-category, cuisine-type and weight.

The conclusion to draw

More than half the properties that make a good recipe snippet here are not in the hRecipe standard. Building from the open specification produces valid markup and a weaker result. This page is the specification to build against for Yandex, and the console validator is the only tool that checks against it.