User-triggered fetcherYandex reviewed September 2026

YandexSearchShop

YandexSearchShop is a Yandex agent that downloads product catalogs in YML files by users' requests. Yandex says these files are often placed in directories prohibited for indexing, and that general robots.txt rules do not apply to the agent, though it has its own YandexSearchShop token. Verify it by reverse DNS to yandex.ru, yandex.net or yandex.com with forward DNS confirmation.

OperatorYandex
User-agent tokenYandexSearchShop
PurposeUser-triggered fetcher
robots.txt tokenYandexSearchShop
Honors robots.txtPartially, see notes
Published IP rangesNo official range file
VerificationReverse 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.
Reverse DNS suffixyandex.ru, yandex.net, yandex.com
Full user-agent example (from the operator)Mozilla/5.0 (compatible; YandexSearchShop/1.0; +http://yandex.com/bots)

What YandexSearchShop does

In access logs the agent identifies itself as Mozilla/5.0 (compatible; YandexSearchShop/1.0; +http://yandex.com/bots). Yandex says the requests download product catalogs in YML files, and that the downloads happen by users' requests. Yandex also notes that these catalog files are often placed in directories prohibited for indexing, so a site owner may see this agent requesting paths that are closed to indexing. Yandex documents nothing about request frequency, and it does not say whether the agent executes JavaScript.

Yandex states that general robots.txt rules do not apply to YandexSearchShop. A rule addressed to the YandexSearchShop token is the documented control. Blocking it prevents the user-requested catalog downloads Yandex describes; the operator does not document any further effect on search indexing. Allowing it lets those YML fetches proceed even from directories otherwise closed to indexing. Yandex publishes no IP range list for this agent, so verification is by reverse DNS with a forward lookup, or through the IP address check tool in Yandex Webmaster.

Operator note. It does not take into account the general rules in robots.txt.

Controlling YandexSearchShop with robots.txt

Use the token YandexSearchShop in robots.txt. Yandex documents limits on how this bot applies robots.txt; see the operator note.

Block everything
User-agent: YandexSearchShop
Disallow: /
Allow everything
User-agent: YandexSearchShop
Allow: /

Verifying a request is really YandexSearchShop

Anyone can put YandexSearchShop 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.

Reverse DNS check
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 YandexSearchShop?

Only if you do not want Yandex to download your YML product catalogs at users' request. Yandex documents no other effect of blocking it. If you do block it, address the YandexSearchShop token directly, since Yandex says general robots.txt rules do not apply to this agent.

How do I verify YandexSearchShop?

Run a reverse DNS lookup on the requesting IP and confirm the hostname ends in yandex.ru, yandex.net or yandex.com, then resolve that hostname forward and check it returns the same IP. Yandex also provides an IP address check tool in Yandex Webmaster. Yandex publishes no IP range list for this agent.

Does YandexSearchShop obey robots.txt?

Partially. Yandex says general robots.txt rules do not apply to YandexSearchShop, which fits its job of fetching catalog files from directories often prohibited for indexing. The agent has its own YandexSearchShop token, so directives written for that token are the way to control it.

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.