Botcard · All tokens

Yeti

Naver's robots.txt guide says the Naver search robot follows the rules written in robots.txt. Its examples use User-agent: Yeti. If the site root has no robots.txt file, the robot treats every page as collectable. The same guide says a search robot may still request a favicon, or a JavaScript or CSS file, when the page that includes that file is allowed to be collected. The identification guide names Yeti as the robot for general Naver search. Ads-Naver and Blueno are separate tokens. This check matches the whole token.

robots.txt token
Yeti
Operator
Naver
Kind
search
robots.txt
obeys. The vendor says this crawler obeys robots.txt on automatic crawls.
HTTP user-agent
Mozilla/5.0 (compatible; Yeti/1.1; +https://naver.me/spd) The identification guide at https://searchadvisor.naver.com/guide/seo-basic-firewall also publishes Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko; compatible; Yeti/1.1; +https://naver.me/spd) Chrome/W.X.Y.Z Safari/537.36. The version can change without notice.
IP list
https://searchadvisor.naver.com/doc/naverbot.json The identification guide links this JSON prefix list and says the list can change without notice. Fetched on 2026-10-18, HTTP 200, creationTime 2024-07-12. Botcard does not copy the prefixes. The guide's reverse-DNS check looks for a hostname ending in .naver.com and then confirms the forward lookup. Botcard does not copy the example address.
Source
robots.txt 설정하기. Retrieved 2026-10-18.

JSON

curl -s https://whosthatbot.com/v1/crawlers/yeti

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Yeti on /docs and allows *. The call does not fetch a host.

curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: Yeti\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["yeti"]}}}'

That call returns fetched_target false. This row is disallow via group Yeti, rule Disallow: /.