Naver
Ads-Naver
Collects page information for Naver advertising.
Ad reviewPurposeWeb search
HTTP identifierYeti
IdentityVerify beyond the name
THE SIGNAL
What this visit tells you
Naver search discovery should be measured separately from visits sent by its results.
URL coverage
Crawl errors
Repeat crawls
Your next move
Check Korean-language landing pages and Naver’s crawler-verification guidance.
The technical details
MarkdownHow to identify it
Look for the Yeti identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.
How to check identity
Use Naver’s current crawler IP information or forward-confirmed reverse DNS under naver.com, as described in Search Advisor.
Access and robots.txt
Use a Yeti robots.txt group to control Naver search crawling. Review the rules on the same host as the requested page.
Optional full-site opt-out. Merge with existing rules only if intended. robots.txt does not secure private content.
User-agent: Yeti
Disallow: /Seeing 403 or 404 responses?
403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.
Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.
SourcesReviewed 2026-09-14
Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.
APOSTL PulseSee Yeti in context
See their requests. Find the pages that matter.
See your agent trafficKEEP EXPLORING
