Description of the elements processed by Yandex

Yandex accepts an organisation card into Yandex Business only when it strictly conforms to hCard: the root element must carry the vcard class, and all properties must sit inside it.

The three mandatory properties

• fn and org — the organisation name, set to the same value. The recommended form is both classes on one element: <span class="fn org">.
• adr — the address, detailed enough to find the business on a map. Nested properties: country-name, region, locality, street-address, extended-address (floor, office, business centre), postal-code. locality is required, and where a place name is not unique, region becomes required too.
• tel — with the city code, preferably +{country} ({city}) {number}.

Cards are processed for four countries only: Russia, Ukraine, Belarus and Kazakhstan. That single line decides whether any of this applies to a given business.

The rule for branches

Multiple addresses may sit in one card when the branches share a name and contact details — one site, one call centre. Where branches differ in name, telephone or email, create a separate vcard for each. And Yandex asks for actual addresses people can visit, not registered legal addresses.

Supported optional properties

category (helps Yandex Business classify the business faster; several allowed), email (several allowed, as text or mailto: link), geo with nested latitude and longitude (one per card, and it speeds geocoding), url, and workhours. Yandex recommends supplying as many as possible — each one is something more users see about the business.

Displaying one value and publishing another

The <abbr> element with a title attribute lets the page show a short local number while the markup carries the full international form. The value-title pattern does the same for values that should not be visible at all, such as coordinates or an internal category.