Regional search engines overview
In several markets a regional search engine leads instead of Google: Yandex in Russian-language search, Baidu in China, Naver in South Korea, Seznam in the Czech Republic, and Coc Coc in Vietnam. Recognising their crawlers matters because being indexed by them is how you reach those audiences.
Why regional engines matter
Google's global lead is not uniform. In some markets a local engine holds a leading or substantial share, and search behaviour there flows through it rather than Google. If you target such a market, your visibility depends on that engine's crawler reaching and indexing your pages.
Treating Googlebot coverage as a proxy for all search visibility can be misleading for these audiences. The local engine's crawler is the relevant signal.
- Yandex — strong in Russian-language search (token YandexBot)
- Baidu — leads Chinese-language search (token Baiduspider)
- Naver — leads South Korean search (token Yeti)
- Seznam — notable share in the Czech Republic (token SeznamBot)
- Coc Coc — Vietnam-focused browser and search (token coccocbot)
What this means for operators
First, decide which markets matter to you; only then do the corresponding crawlers become relevant. There is no benefit to chasing every regional engine if you do not serve that audience.
Second, verification and documentation quality vary. Google and Bing publish robust verification methods; several regional engines document primarily in their own languages with more limited verification options. Treat their user agents as claims, confirm behaviour in each engine's own documentation, and never fabricate tokens or IP ranges to fill gaps.
How it appears in analytics and logs
Seeing YandexBot, Baiduspider, Naver Yeti, SeznamBot, or CocCocBot reflects a regional engine crawling you for an audience where it leads. Their absence may mean weaker visibility in that market, even if Googlebot crawls you fully.
Diagnostic use case
Decide which regional search crawlers to allow and monitor based on the markets you target, rather than assuming Google coverage is sufficient everywhere.
What WebmasterID can help detect
WebmasterID classifies regional search crawlers server-side and shows each separately from human traffic, so you can see which regional engines are crawling you without parsing logs by hand.
Common mistakes
- Assuming Googlebot coverage guarantees visibility in every market.
- Chasing regional crawlers for markets you do not actually serve.
- Expecting Google-style verification to work identically for every regional engine.
Privacy and accuracy notes
Market relevance here is a coarse, region-level note, never an exact visitor location. Crawler identification uses only user agents and documented verification. WebmasterID records these crawlers as bot events, separate from human analytics.
Related pages
- YandexBot — Yandex's web crawler
YandexBot is the main crawler for Yandex, a search engine with a strong presence in Russian-language search. It uses the YandexBot robots.txt token and can be verified through reverse DNS, where the IP should resolve into a Yandex domain, confirmed by a matching forward lookup.
- Naver Yeti — South Korea search crawler
Yeti is the web crawler operated by Naver, the search and content portal that holds a leading share of search in South Korea. Its robots.txt token is Yeti. Naver provides webmaster tooling and documentation, much of it in Korean, so some specifics are marked partially verified.
- CocCocBot — Vietnam search crawler
CocCocBot is the crawler for Coc Coc, a browser and search engine focused on the Vietnamese market with features tuned for Vietnamese-language text. Its robots.txt token is coccocbot. Documentation is largely in Vietnamese, so some specifics are marked partially verified.
- Bot intelligence
See regional search crawlers separated from human traffic.
Sources and verification notes
- Yandex — robot verification documentationExample of a regional engine's crawler documentation; see each engine for its own.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.