YandexMarket
Yandex operates YandexMarket, the robot used by Yandex Market. It sends "Mozilla/5.0 (compatible; YandexMarket/1.0; +http://yandex.com/bots)" or a 2.0 variant, and honors the YandexMarket robots.txt token, though only version 1.0 takes general rules into account. Site owners verify it by reverse DNS to a yandex.ru, yandex.net or yandex.com host with forward confirmation, or with the Yandex Webmaster IP check tool.
Mozilla/5.0 (compatible; YandexMarket/1.0; +http://yandex.com/bots)What YandexMarket does
Two versions appear in logs. YandexMarket/1.0 sends "Mozilla/5.0 (compatible; YandexMarket/1.0; +http://yandex.com/bots)" and YandexMarket/2.0 sends the same string with the version number changed. Yandex's crawler reference says only that this is the robot used by Yandex Market; it does not say what pages it requests, how often, or whether it renders them. Yandex gives it no search-index role in that reference, so it is listed here under the general "other" category rather than as a search-engine crawler.
The difference between the two versions is how they read robots.txt. Yandex documents that YandexMarket/1.0 takes general robots.txt rules into account, so a User-agent: * block applies to it. YandexMarket/2.0 does not, so it follows only a rule group that names YandexMarket directly. A site owner who wants to restrict both versions should add an explicit YandexMarket group rather than rely on a wildcard. Blocking that token withholds the site's pages from whatever Yandex Market does with them; Yandex's documentation does not describe that use further.
Verification uses the method Yandex documents. Reverse-resolve the requesting IP and confirm the hostname ends in yandex.ru, yandex.net or yandex.com, then forward-resolve it and check that it returns the same address. Yandex Webmaster also has an IP address check tool for site owners who prefer not to run the lookups by hand. Yandex publishes no IP range file, so there is no address list to match against.
Operator note. Yandex documents two versions. YandexMarket/1.0 takes into account the general rules in robots.txt; YandexMarket/2.0 ('Mozilla/5.0 (compatible; YandexMarket/2.0; +http://yandex.com/bots)') does not.
Controlling YandexMarket with robots.txt
Use the token YandexMarket in robots.txt. Yandex documents limits on how this bot applies robots.txt; see the operator note.
User-agent: YandexMarket
Disallow: /User-agent: YandexMarket
Allow: /Verifying a request is really YandexMarket
Anyone can put YandexMarket in a User-Agent header. Reverse DNS lookup on the requesting IP must return a host ending in yandex.ru, yandex.net or yandex.com, and a forward DNS lookup of that host must return the same IP. Yandex Webmaster also provides an IP address check tool.
host <request-ip>
# expect a hostname ending in yandex.ru, yandex.net, yandex.com
host <that-hostname>
# expect it to resolve back to <request-ip>Common questions
Should I block YandexMarket?
Yandex says only that this is the robot used by Yandex Market, so blocking it withholds your pages from whatever that service does with them. The documentation gives no more detail on the use. If you block, name YandexMarket explicitly, because version 2.0 ignores general User-agent: * rules.
Why does YandexMarket ignore my wildcard rule?
Yandex documents two versions. YandexMarket/1.0 takes general robots.txt rules into account; YandexMarket/2.0 does not. If a 2.0 request reaches a page you blocked under User-agent: *, that is expected behavior. Add a rule group with User-agent: YandexMarket to cover both versions.
How do I verify YandexMarket?
Run a reverse DNS lookup on the IP and check that the hostname ends in yandex.ru, yandex.net or yandex.com, then a forward lookup to confirm it resolves back to the same IP. Yandex Webmaster also has an IP address check tool. No IP range list is published for this robot.
Sources
Every fact on this page was checked against Yandex's own documentation, listed below, and re-checked by a second reviewer before publication. Reviewed September 2026.
Related crawlers
This registry documents how operators describe their own bots so site owners can identify and control them. It does not publish third-party IP lists or guess at undocumented behaviour. To see how your own site responds to automated visitors, the bot detection scanner reads a URL's live response and names the protection it finds.