Webmaster
How Yandex indexes sites
A site on search results page

Description of elements processed by Yandex

Required elements

For an organization's card to be processed by Yandex correctly, it must strictly comply with the hCard format. For example, the root element of the card must be an element of the vcard class. Other elements (called properties) are nested inside the root element.

In addition, for the card to be accepted into the Organizational registry database, it must contain the following properties:

The content requirements for these properties are listed below.

fn and org

Name of organization.

The hCard standard requires that the values of the fn and org properties must match for cards that describe organizations. It is recommended that you mark up the organization name with both of these classes within one element:

<span class="fn org">...</span>

adr

Address of organization.

The address must be sufficiently detailed so that it can be found on the map. Please note that cards are processed only for the following four countries: Russia, Ukraine, Belarus, and Kazakhstan

The following nested properties will be processed for the adr class element (each of them may only be indicated once):

  • country-name — country;

  • region — federal constituency + region;

  • locality — town, city or village;

  • street-address — street, building, house, etc. (street address detailed enough to identify the house/building);

  • extended-address — here you can specify the entrance, floor, office, etc., i.e. information on the location within a building, the name of the shopping mall or business center, and any other description that is not considered part of the proper address;

  • postal-code — postal code.

For correct address identification, you must specify the locality name (the locality property). If the name does not uniquely identify the city, town or village (e.g. Oak Village), you must also specify the region (the regionproperty).

Note. 

We recommend that you mark up only physical location addresses (i.e. those that help people find you) and not registered addresses.

A card may contain more than one address. This is possible if an organization has several branches or locations with the same name and identical contact data (website, unified call center, etc.). If the branches have different names, telephone numbers or email addresses, we recommend creating a separate card (vcard class element) for each branch.

tel

Telephone number (including area code).

The following format is preferable: +{country code} ({area code}) {number}, for example: +7 (890) 123-45-67, +375 (12) 345-67-89. If you would like to display the telephone number in a different format for users, you may use the <abbr> element.

You can specify several telephone numbers in a single card.

Example:

<div class="vcard">
  <div>
    <a class="fn org url" href="http://www.camomile-cafe.com">Cafe Camomile</a>
  </div>
  <div class="adr">
    <span class="locality">Sunny City</span>,
 <span class="street-address">21 Romantic Avenue</span>
  </div>
  <div class="tel">Telephone:
    <abbr class="value" title="+ 7 (890) 123-45-67">123-45-67</abbr>
  </div>
  <div class="tel">
    <abbr class="type" title="fax">Fax:</abbr>
 <abbr class="value" title="+ 7 (890) 123-45-89">123-45-89</abbr>
  </div>
</div>

You can find detailed information on which HTML fragments are accepted as property values in the section titled Markup processing rules.

Example of a card that contains the minimum required information

<div class="vcard">
  <div>Cafe <span class="fn org">Camomile</span></div>
  <div class="adr">
    <span class="locality">Sunny City</span>,
 <span class="street-address">21 Romantic Avenue</span>
  </div>
  <div class="tel">Telephone: 
    <abbr class="value" title="+ 7 (890) 123-45-67">123-45-67</abbr>
  </div>
</div>

Supported elements

In addition to the required properties fn and org, adr, and url, Yandex also processes the following properties:

We recommend that you specify as many of these properties as possible. This will enable Yandex to display the most complete information about your business to users.

category

Description of the organization's activities.

By filling in this property, you help Yandex assign your organization to a certain heading in the Organizational registry and thus speed up processing of the card by the Yandex service. Therefore, if you can include a description of your organization's activities in the contact information, you should mark it up using the category property.

You may specify several categories in a single card, for example:

<div class="vcard">
  <div>
    <span class="category">Cafe</span>-<span class="category">culinary</span>
 <span class="fn org">Camomile</span>
  </div>
  <div class="adr">
    <span class="locality">Sunny City</span>,
 <span class="street-address">21 Romantic Avenue</span>
  </div>
  <span class="url">
    <span class="value-title" title="http://www.camomile-cafe.com"/>
  </span>
</div>

You can also add the category property, which is invisible to site visitors, by using, for example, a nested element of the value-title class with the title attribute:

<div class="vcard">
  <div>
    <a class="fn org url" href="http://www.camomile-cafe.com">Camomile</a>
  </div>
  <div class="adr">
    <span class="locality">Sunny City</span>,
 <span class="street-address">21 Romantic Avenue</span>
  </div>
  <span class="category">
    <span class="value-title" title="cafe"/>
  </span>
</div>

You can find detailed information on which HTML fragments are accepted as property values in the section titled Markup processing rules.

email

Email address.

You can specify several email addresses in a single card.

An email address may be displayed as plain text or as a link.

Example:

<div class="vcard">
  <div>
    <a class="fn org url" href="http://www.camomile-cafe.com">Cafe Camomile</a>
  </div>
  <div class="adr">
    <span class="locality">Sunny City</span>,
 <span class="street-address">21 Romantic Avenue</span>
  </div>
  <div class="email">camomile@camomile-cafe.com</div>
</div>

You can find detailed information on which HTML fragments are accepted as property values in the section titled Markup processing rules.

geo

Geolocation coordinates corresponding to the address, specified in degrees.

If this information is available to you, we recommend that you include it into a card since it helps to geocode your location.

A card may not contain more than one element of the geo class.

Nested properties must be specified for this property:

  • latitude — geographic latitude;

  • longitude — geographic longitude.

The coordinates are usually made invisible to site visitors by using, for example, a nested element of the value-title class with the title attribute:

<div class="vcard">
  <div>
    <a class="fn org url" href="http://www.camomile-cafe.com">Cafe Camomile</a>
  </div>
  <div class="adr">
    <span class="locality">Sunny City</span>,
 <span class="street-address">21 Romantic Avenue</span>
  </div>
  <span class="geo">
    <span class="latitude">
     <span class="value-title" title="55.792188"/>
    </span> 
 <span class="longitude">
     <span class="value-title" title="37.764956"/>
    </span>
  </span>
</div>

If you need to display the coordinates on the page, we recommend that you specify them in degrees, minutes and seconds:

<div class="vcard">
  <div>
    <a class="fn org url" href="http://www.camomile-cafe.com">Cafe Camomile</a>
  </div>
  <div class="adr">
    <span class="locality">Sunny City</span>,
 <span class="street-address">21 Romantic Avenue</span>
  </div>
  <div class="geo">
    <abbr class="latitude" title="55.792188">Latitude: 55°47′31.88″ N</abbr>
 <abbr class="longitude" title="37.764956">Longitude: 37°45′53.84″ E</abbr>
  </div>
</div>

You can find detailed information on which HTML fragments are accepted as property values in the section titled Markup processing rules.

url

A link to the official site of the organization.

The link should preferably point to the main page of the site (or to the page of the branch if the card contains branch information). For example, a card resides on the page http://www.camomile-cafe.com/contacts.html, and the url property has the value http://www.camomile-cafe.com.

The hCard standard allows more than one element of the url class. However, when a card is added to the Organizational registry, only the most suitable one will be selected.

If you display a site address in the contact information block, you can assign the url class to the <a> element:

<a class="url" href="...">...</a>

On the other hand, if your contact information does not contain a URL, you can make the url property invisible to site visitors by using the following syntax:

<span class="url"><span class="value-title" title="..."/> </span>

You can find detailed information on which HTML fragments are accepted as property values in the section titled Markup processing rules.

workhours

The business hours of the organization.

The hCard standard does not include this property; Yandex added it as an extension.

To specify the business hours, we recommend the format used in the Organizational registry, for example:

  • Mon-Fri 9:00-18:00

  • Mon-Fri 9:00-18:00, Lunch 13:00-14:00; Sat-Sun 10:00-17:00, Lunch 13:30-14:00

  • Mon-Sat 11:00-20:00, Sun 12:00-24:00

  • daily 10:00-24:00

  • around the clock

However, you may specify the business hours in any format you like.

Example:

<div class="vcard">
  <div>
    <a class="fn org url" href="http://www.camomile-cafe.com">Cafe Camomile</a>
  </div>
  <div class="adr">
    <span class="locality">Sunny City</span>,
 <span class="street-address">21 Romantic Avenue</span>
  </div>
  <div>Open
    <span class="workhours">daily from 11:00 to 24:00</span>
  </div>
</div>

Other elements

Yandex currently ignores the remaining properties stipulated by the hCard format. You can, however, include them in the organization's card if you want to make them available to other services. For example, if your contact information contains a logo, use the logo property.

The complete list of properties is presented in the official format specification under the section titled Property List.

Rate this article
Thank you for your feedback!