In short. Naver Yeti collects web documents for Naver Search, with request verification through DNS lookups or a published IP range list.
Definition: Naver Yeti is the search crawler that collects web documents for Naver Search. A crawler is a program that visits web pages to collect their content; Yeti identifies itself through the User-Agent field in its requests.
Key facts
- As of October 2026, Naver's search optimization guide names its search crawler Yeti and warns that version details can change without notice.
- Naver's crawler verification guide documents a hostname check ending in
.naver.com, followed by an address lookup that must match the original requesting IP address. - Naver's robots.txt documentation uses
User-agent: Yetifor search crawling rules and requires a plain text file at the site's root.
What does the Yeti user-agent look like?
A user-agent is the identifying string a program sends with a web request. Naver's search optimization guide includes this compact example:
Mozilla/5.0 (compatible; Yeti/1.1; +https://naver.me/spd)
The same guide also shows a longer browser-style string containing Yeti/1.1. Its warning about changing versions matters when reviewing server or firewall rules: a rule tied to one complete example can become outdated. Naver recommends robots.txt for crawler access control because its IP ranges can change.
How is a request verified?
DNS, the Domain Name System, maps domain names to network addresses. A reverse lookup starts with an address and returns a name. Naver's verification procedure starts with the requesting IP address recorded in web server or firewall logs.
The reverse lookup must return a name ending in .naver.com. A forward DNS lookup of that name must then return the original IP address. Both checks form Naver's documented DNS procedure; reading Yeti in the request identifies the claimed crawler name.
For automated checks, the same guide links to Naver's IP range list. This JSON file contains a prefixes array with ipv4Prefix entries describing address ranges. An automated check compares the requesting address with those ranges. Naver warns that the list can change without notice.
How does a website control Yeti access?
The robots.txt file communicates crawling permissions to search robots. Naver's robots.txt guide gives this example for allowing Yeti while disallowing other search crawlers:
User-agent: *
Disallow: /
User-agent: Yeti
Allow: /
The file belongs at /robots.txt and must be accessible as text/plain. The Webmaster Tools robots.txt tool can request retrieval of an updated file and test whether its rules permit crawling a particular page. These checks address the site's crawling permissions; the DNS procedure above addresses the identity of an incoming request.
Related terms
FAQ
Do I need to register my site before Yeti can visit it?
Naver's site registration FAQ says sites can appear in search without Webmaster Tools registration. Registering and verifying ownership gives you reports about crawling, indexing and search exposure.
Can I use robots.txt to protect private information?
Naver's robots.txt guide recommends protecting sensitive content through login or another access restriction in addition to crawling rules.
Sources
- Naver Search Advisor, "Purpose of search engine optimization", undated
- Naver Search Advisor, "How to verify search robots", undated
- Naver Search Advisor, "Configuring robots.txt", undated
- Naver Search Advisor, "naverbot.json" (Search robot IP ranges), undated
- Naver Search Advisor, "Site registration and ownership verification", undated
Check how a page reads to answer engines. Open the GEO score analyzer