What is Yeti?
Direct Answer: Yeti is a web crawler operated by Naver, a South Korean search engine, used for indexing websites to provide search results.
Yeti is the web crawler for Naver, a South Korean search engine. It indexes websites to provide search results and power other services on the Naver platform. The crawler is identified by user agents such as 'Mozilla/5.0 (compatible; Yeti/1.1; +http://naver.me/spd)'.
User-Agent Identification
The following user-agent strings identify Yeti in your live traffic data:
Mozilla/5.0 (compatible; Yeti/1.1; +http://naver.me/spd)Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.0 Safari/537.36 (compatible; Yeti/1.1; +http://naver.me/spd)
robots.txt Rules for Yeti
Respects robots.txt: No
This bot does not commit to following robots.txt
Yeti does not officially follow robots.txt directives. The only reliable way to control access is through server-side blocking (IP filtering, user-agent rules in your web server config) combined with log monitoring to verify effectiveness.
Need continuous verification across 500+ bots? Can AI See It automates this.
Crawl Behavior
Frequency:Not Documented
Request Pattern:Not Documented
Crawl Activity Index
Relative crawl activity for Yeti over the past 28 days. Higher values indicate increased crawling intensity compared to the period baseline.
View recent activity data (last 7 days)
| Date | Activity Index |
|---|---|
| Mar 26, 2026 | 88.0 |
| Mar 27, 2026 | 82.7 |
| Mar 28, 2026 | 83.1 |
| Mar 29, 2026 | 81.8 |
| Mar 30, 2026 | 87.3 |
| Mar 31, 2026 | 90.2 |
| Apr 1, 2026 | 88.8 |
Source: Cloudflare Radar
Why track Yeti traffic?
Measure what Naver gives back. Yeti crawls thousands of your pages — but how much traffic does Naver actually send in return? Track referral visits from Naver's search products relative to crawl volume.
Monitor crawl budget and indexation health. Yeti determines which of your pages appear in Naver's search results. Tracking its crawl patterns reveals how often your key pages are visited, what gets ignored, and where crawl budget is wasted.
Detect crawl anomalies early. A sudden drop in Yeti activity can signal indexation problems — before they show up as organic traffic losses.
Catch 4XX and 5XX errors before they hurt rankings. If Yeti hits broken pages or server errors during crawling, those URLs may be dropped from the index. Early detection in your logs lets you fix the issue before it impacts your organic visibility.
Validate that your robots.txt rules are enforced. Configuring robots.txt is one thing — confirming that Yeti actually respects your directives is another. Live traffic validation is the only way to verify.
Why live traffic verification instead of Search Console? Search Console shows what Naver tells you. Live traffic verification shows what actually happened — including AI-related crawling that Search Console doesn't report.
Read: Live traffic verification vs Search Console for crawl monitoring →Log Verification
To verify Yeti traffic in your live traffic data:
- Search access logs for the user-agent strings listed above
- Check if the IP addresses match documented ranges (if provided by Naver)
- Verify the crawl pattern matches documented behavior
- Use reverse DNS lookup for additional verification if available
Note: Observed behavior in production environments may differ from official documentation. Live traffic monitoring provides the only reliable verification of actual bot behavior.
Undocumented Information
The following information is not officially documented for Yeti:
- crawl frequency
- IP verification
- JavaScript rendering
- request pattern
Monitor Yeti alongside 500+ other bots
Track crawl health, detect anomalies, and measure how AI features are changing your referral traffic — all from your live traffic data.
- Crawl frequency, coverage, and error monitoring for Yeti
- Compare traditional organic referrals vs AI-generated referrals
- Detect fake Yeti traffic (user-agent spoofing)
Measure business impact from Yeti
Crawl activity directly impacts organic visibility. The question is: is Yeti crawling the right pages at the right frequency?
- Crawl coverage: which paths and page types Yeti is actually crawling
- Crawl freshness: how recently Yeti visited key URLs
- Health: response code distribution (2xx, 3xx, 4xx, 5xx) with alerts when failed crawls spike
- Referral tracking: Yeti takes — measure what Naver gives back. Track actual visits arriving from Naver's products to your site.
Based on your live traffic data and analytics — not synthetic prompt tests.
Official Documentation
View Official Yeti Documentation →
Information sourced from official documentation. Content generated with AI assistance.