Movies

Film markup uses schema.org/Movie and feeds Yandex’s film snippets. Every field is recommended rather than required, but one has a strict rule attached.

The rating pair

aggregateRating requires two properties used together: ratingValue (the current rating, a positive number) and bestRating (the maximum possible, also positive). Supplying a rating without its scale is meaningless — 4 out of 5 and 4 out of 10 are different claims — and Yandex enforces the pairing.

The remaining fields

• genre, description, inLanguage, contentRating (age restrictions), isFamilyFriendly (Boolean).
• dateReleased and dateCreated — release date and year of shooting, which are distinct.
• duration in ISO 8601: PT1H30M for ninety minutes.
• director, actor, producer (Person) and award — each one in its own element. Three directors means three separate itemprop elements, not one comma-separated string.
• musicBy (Person or MusicGroup), productionCompany (Organization).

The pattern worth copying

Yandex’s example puts the fixed technical values — content rating, duration, dates, language, family-friendly flag, production company — in meta elements, while names and descriptions are marked on the visible links and text that were already on the page. That separation is the practical template for any entity markup: invisible facts in meta, visible facts on the elements that already display them, so the markup cannot drift away from what the user sees.

Applicability

This schema is for film catalogues and cinema listings, and it is worth reading even if you never mark up a film. The one-element-per-person rule and the rating pair rule apply the same way to books, courses and events, and both are among the most frequent causes of markup that validates loosely and produces nothing.

The standard reservation

Yandex may use the data fully, partially or not at all, in any of its services.