Software

Software markup produces structured snippets for application pages. Four types are supported: SoftwareApplication, MobileApplication, WebApplication and VideoGame.

The rule that decides whether anything appears

description is the only required field — but at least two optional properties must also be present for a snippet to be generated. And even then, if Yandex judges the ordinary snippet more informative, it uses that instead. A minimally marked-up page produces nothing at all.

The optional fields, with their quirks

• applicationSubCategory — the category (“Players”, “Races”, “Online game”). Several values are allowed, and the snippet uses the first few up to a combined length of 24 characters. Long category names are simply cut off, so the most descriptive short label should come first.
• fileSize — a bare number is interpreted as kilobytes. Units can be given explicitly (KB, MB, GB), and a site publishing “42” meaning megabytes will advertise 42 kilobytes.
• interactionCount — download count, written in a specific form: UserDownloads:XXX.
• operatingSystem — with its own syntax. Accepted values include win, windows X, xp, vista, Windows Mobile, Mac, iOs, iPhone, iPad, Android. Versions of one system are separated by commas; different systems by a vertical bar: Windows 8 | Android | iOS.
• price and priceCurrency — as properties of a nested Offer, currency in ISO 4217. A price of 0 makes the snippet display “Free”, which is the single most effective value on this list for a free application.

How to implement it

Take the description as given, then add the three or four facts a user actually decides on: price (or zero), size with explicit units, supported systems in the required separator syntax, and downloads. That satisfies the two-optional-property threshold comfortably and produces a snippet that answers the question before the click.