Yeti/Naverbot

Search EnginePurpose·Search indexSafety·SafeSEO impact·CriticalBlocked by·Not yet measuredSnapshot·2026-04

01 /Overview

Yeti/Naverbot is a search-engine crawler operated by Naver. Its job is to find, fetch, and index web pages so they can be returned in organic search results.

Traffic is regular and bounded by your robots.txt. Allowing it is generally how your site stays discoverable through the corresponding search engine, blocking it almost always reduces visibility there.

For most sites, search-engine crawlers are still the largest source of bot traffic and the largest source of human visitors that follow.

See Yeti/Naverbot on your own site

02 /Identification

Match the User-Agent header on incoming requests against the pattern below.

regex

Yeti/Naverbot

For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.

03 /Control

The polite way is a robots.txt rule. Compliant agents respect it; the others ignore it.

robots.txt

User-agent: Yeti/Naverbot Disallow: /

Test a URL

Paste any URL on your site and we'll fetch its robots.txt to check whether Yeti/Naverbot is allowed.

04 /Technical fingerprint

Renders JavaScript

IP verification

DNS reverse lookup

Crawl frequency

Continuous

Honors robots.txt

Yes

Honors Crawl-delay

Yes

05 /Expected behavior

Expect steady, polite crawling. Yeti/Naverbot works through your site according to its own schedule and respects standard robots.txt directives.

The Naver bot family

Naver runs 10 bots in total. Each one is a separate user-agent so you can allow or block them independently.

Search Engine

Link Unfurler

Training Crawler

HyperCLOVA-Bot

AI Search Index

Cue-Bot

Common questions

Should I let Yeti/Naverbot through?

In most cases, yes. Blocking traditional search crawlers reduces organic-search visibility. Allowing is the default for almost all sites. If volume gets noisy, rate-limit it before you block it outright.

Does blocking Yeti/Naverbot affect my Google rankings?

Only on Naver Yeti/Naverbot feeds. Each search engine runs its own crawler, so blocking Yeti/Naverbot only removes you from that one index. Your visibility on Google, Bing, or anything else is untouched.

How do I confirm a request is really from Yeti/Naverbot?

Look at the User-Agent header in your access logs and match it against the strings listed above. Worth knowing that the User-Agent is easy to fake, so this check tells you "the traffic claims to be Yeti/Naverbot", not "the traffic is genuinely Yeti/Naverbot". If you need stronger guarantees, look for a reverse-DNS check or wait for Naver to publish IP ranges.

What happens to my traffic if I block Yeti/Naverbot?

Your pages drop out of Naver's index, which means losing the organic share you get from that engine. Not catastrophic if Naver is a minor player, much more painful if it's a meaningful source of your traffic. Check your analytics for Naver's actual referral share before deciding.

How is Yeti/Naverbot different from Naver's other bots?

Naver splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Naver family above to see which ones actually matter for your site.

What's the cleanest way to control Yeti/Naverbot?

Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.

References

Verify everything above against the operator's own documentation.

Naver Webmaster ToolsDocumentation for Yeti, Naver's primary crawler.

Agent Directory See all bots

Yeti/Naverbot

Search EnginePurpose·Search indexSafety·SafeSEO impact·CriticalBlocked by·Not yet measuredSnapshot·2026-04

01 /Overview

Yeti/Naverbot is a search-engine crawler operated by Naver. Its job is to find, fetch, and index web pages so they can be returned in organic search results.

For most sites, search-engine crawlers are still the largest source of bot traffic and the largest source of human visitors that follow.

See Yeti/Naverbot on your own site

02 /Identification

Match the User-Agent header on incoming requests against the pattern below.

regex

Yeti/Naverbot

For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.

03 /Control

The polite way is a robots.txt rule. Compliant agents respect it; the others ignore it.

robots.txt

User-agent: Yeti/Naverbot Disallow: /

Test a URL

Paste any URL on your site and we'll fetch its robots.txt to check whether Yeti/Naverbot is allowed.

04 /Technical fingerprint

Renders JavaScript

IP verification

DNS reverse lookup

Crawl frequency

Continuous

Honors robots.txt

Yes

Honors Crawl-delay

Yes

05 /Expected behavior

Expect steady, polite crawling. Yeti/Naverbot works through your site according to its own schedule and respects standard robots.txt directives.

The Naver bot family

Naver runs 10 bots in total. Each one is a separate user-agent so you can allow or block them independently.

Search Engine

Link Unfurler

Training Crawler

HyperCLOVA-Bot

AI Search Index

Cue-Bot

Common questions

Should I let Yeti/Naverbot through?

Does blocking Yeti/Naverbot affect my Google rankings?

How do I confirm a request is really from Yeti/Naverbot?

What happens to my traffic if I block Yeti/Naverbot?

How is Yeti/Naverbot different from Naver's other bots?

What's the cleanest way to control Yeti/Naverbot?

References

Verify everything above against the operator's own documentation.

Naver Webmaster ToolsDocumentation for Yeti, Naver's primary crawler.