---
metadata:
- name: generator
content: Diplodoc Platform v5.50.6
alternate:
- https://yandex.com.tr/support/webmaster/en/hcard/markup-processing-rules.md
- https://yandex.com.tr/support/webmaster/tr/hcard/markup-processing-rules.md
---
> **Documentation Index:** Fetch the complete configuration index at https://yandex.com.tr/support/webmaster/en/llms.txt
# Markup processing rules
To add contact information, use the **Site geography** → **Addresses and organizations** form in Yandex Webmaster. Submitting contact information through the form is the same as marking up the site pages. Data submitted through the Yandex Webmaster form is also added to [Yandex Business](http://harita.yandex.com.tr/?where) and displayed in various Yandex services.
Yandex processes cards according to the [rules defined in the format specification](http://microformats.org/wiki/hcard#Human_vs._Machine_readable).
## Data structure requirements {#datastructure}
The classes provided by hCard format can be combined with other CSS classes. For example, the `class` attribute of the card's root element can contain, in addition to the `vcard` class name, any set of non-hCard class names:
```xml
```
The same applies to the elements that are card properties.
There are restrictions on combining hCard classes. It isn't allowed to mark a`vcard` class element with another hCard class. Also, it isn't recommended to nest properties. For example, you can't place a `tel` class element inside an `adr` class element (this structure might be processed incorrectly). An exception is made for nested properties that are explicitly listed in the standard, such as `country-name`, `region`, `locality`, `street-address`, `extended-address`, `postal-code` properties nested in the `adr` property; `latitude` and `longitude` properties nested in the `geo` property, and so on.
## Rules for extracting values {#valueextraction}
In most cases, the property value is the text contained within the element of the corresponding class and visible to the users. Some elements are exceptions:
- The `` element with the `title` attribute: the value of the property is the value of this attribute. Example:
```xml
123-45-67
```
The browser displays the value “123-45-67”, while the value of the `tel` property is “+ 7 (890) 123-45-67”.
- The `` element with the `href` attribute for the URL properties (that is, properties that have a URL for the value, namely `url`, `email`, `logo` and `photo`): the value of the ` href` attribute is assigned as the value of the property.
Example:
```xml
Cafe Camomile
```
The `url` property value is “http://www.cafe.com”.
For the `fn` and `org` properties that are not URL properties, the value is “Camomile Cafe”.
- The `![]()
` element with the `src` attribute for URL properties: the value of the `src` attribute is assigned as the value of the property.
- For the `![]()
` element with the `alt` attribute for non-URL properties: the value of the `alt` attribute is assigned as the value of the property.
Example:
```xml
```
The value of the `logo` property is “images/logo.gif”, and the value of the `fn` and `org` properties is “Camomile Cafe”.
In addition, you can mark _part_ of the element's visible text as the value of the property. To do this, add a nested element with the `value` class to this element.
Example:
```xml
Inquiry office: +7 (890) 123-45-67
```
In this case, the value of the `tel` property is “+7 (890) 123-45-67”.
To make a property value invisible to site visitors (display a different text on the page instead of it, or nothing at all), use a nested element of the `value-title` class with the `title` attribute. In this case, the value of the `title` attribute is assigned as the value of the property.
Examples:
```xml
123-45-67
```
```xml
123-45-67
```
In both cases, the value of the `tel` property is “+7 (890) 123-45-67”. The second option lets you avoid showing a pop-up with the “actual” value of the property whenever the user mouses over the phone number.