Naver Search
SafeUser-agent: Yeti
Category: Search Engines
SEO impact if blocked: 10/10
Naver
1 crawler operated by Naver
Who Naver is, for site owners
Naver operates 1 crawler in our directory, filed under Search Engines. Its crawl behaviour is rated safe.
Blocking Naver carries an SEO impact score of 10/10. Blocking impact is rated: Critical - Blocking removes you from search results.
Our recommendation for Naver: Keep it allowed if you want traffic from Naver Search, especially from South Korea.
Naver at a glance
| Operator | Naver |
|---|---|
| Crawler in directory | 1 |
| Categories | Search Engines |
| SEO impact if blocked | 10/10 |
| Crawl behaviour | 1 rated safe |
| Official crawler docs | Naver crawler documentation |
Crawler operated by Naver
What Naver's crawlers are for
Naver runs 1 crawler in our database. Grouped by the job each one does:
- a search engine crawler:
Yeti
The highest-priority token is Tier 3. That makes Naver a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
How site owners treat Naver
None of Naver's tokens were among the names tracked in our robots.txt study of the Tranco top 10,000, which usually means few large sites write rules for them yet. Your own logs are the best evidence of how often they visit.
Writing one policy for Naver
A robots.txt file cannot say "Naver"; it can only name Naver's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Naver fetches through it
User-agent: Yeti
Disallow: /private/
Allow: /- Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
- Name every token you mean. A token you leave out follows
User-agent: *. - Repeat shared rules. A named group ignores the
*group, so copy anyDisallowlines you still want it to obey. - Verify from outside. Run the LLM crawler checker after any change to see the result for each Naver token, including firewall refusals.
Test yourself: does User-agent: Naver block all of Naver's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token Yeti.
Test yourself: if you block one Naver token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each Naver crawler, explained
A one-paragraph brief for every Naver token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- Naver Search (
Yeti, Tier 3): a search engine crawler that builds a search or answer index. Rated safe. Naver Search's operator says it follows robots.txt, so a correctly written Naver Search group is enough to control it. Not tracked in our robots.txt study.
Common mistakes with Naver's crawlers
The errors we see most often with Naver's crawlers in the files and firewalls we test:
- Blocking Naver's crawlers to save bandwidth and then wondering why pages drop out of that search engine. Use crawl-rate settings or caching first.
- Writing a
User-agent: Yetigroup to add one rule for Naver's crawlers and accidentally dropping every rule it used to follow underUser-agent: *. - Disallowing CSS and JavaScript folders, which can stop Naver's crawlers rendering your pages properly.
All three hide inside a file that looks correct, so check Naver's crawlers from outside after every change.
What our own data shows about Naver
Everything below comes from the AI Crawler Check bot database and our two most recent robots.txt scans of the Tranco top 10,000, not from Naver's marketing. Naver has one token in our database, so the whole picture fits in one place.
Yeti in our records
We first recorded Yeti on October 19, 2026. Naver documents it on searchadvisor.naver.com, and we recheck that page before each release. No file in our top-10,000 scans names Yeti, so any rule you write for it puts you ahead of almost every large site.
Among the 63 search engines in our database, Yeti sits 63th by priority (Tier 3), level with AdIdxBot, Amzn-SearchBot, Applebot, baidu. 62 of the 63 share its safe rating. Other operators with a crawler that builds a search or answer index: AddSearchBot (AddSearch, Tier 2), AIWebIndex (Lyrenth, Tier 2), atlassian-bot (Atlassian, Tier 2), AzureAI-SearchBot (Microsoft, Tier 2), Cloudflare-AI-Search (Cloudflare, Tier 2). A policy for Yeti is usually a policy for these too.
A decision record for Yeti
Teams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the Yeti entry reads:
- Operator and job: Naver; it builds a search or answer index.
- Priority and behaviour: Tier 3, rated safe, blocking impact critical.
- Suggested starting point: Allow by default; revisit if it costs you bandwidth.
- Enforcement: Yeti's operator says it follows robots.txt, so a correctly written Yeti group is enough to control it.
User-agent: Yeti
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the Yeti entry once a quarter, or when Naver publishes a new token next to it.
Checking Yeti on your own site
Because Naver runs only Yeti in our records, one check covers the whole operator. Search your access logs for the string Yeti over the last 30 days, note how many requests it made and which paths it asked for, then compare that with what your robots.txt allows. Match the requests against what Naver publishes about the crawler, since that page is the only authority on its behaviour. A Tier 3 crawler rated safe rarely needs more than a quarterly look, and our log checker does the counting for you.
How top sites treat Naver's crawlers
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for Naver's crawlers is tracked by name in our study. For scale, 20.1% of top-site files block at least one AI training crawler and 4.3% refuse every unnamed crawler with User-agent: * and Disallow: /, which would catch Naver's crawlers too.
More questions about Naver
- Will blocking Naver affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of Naver's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for Naver?
- Crawlers cache robots.txt, commonly for up to a day. Expect a change to apply within about 24 hours, and confirm it in your logs.
- Can I allow Naver on some sections and block it on others?
- Yes. Inside the group for
Yeti, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking Naver delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether Naver offers a removal or opt-out process.
- Is a firewall block better than robots.txt for Naver?
- A firewall enforces the decision, while robots.txt asks politely. Many operators recommend robots.txt because blocking their IPs can stop them reading your rules at all. Use robots.txt first, and add a firewall rule only if requests continue.
A five-minute Naver review
- Confirm the token. Compare the user-agent in your logs with the tokens listed on this page. A close spelling is not the same crawler.
- Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
- Write the group. Add or edit one
User-agentgroup per decision and repeat any shared rules inside it. - Publish and wait. Allow about a day for crawlers to fetch the new file.
- Confirm the result. Check your logs, then run the AI crawlability checker to see the outcome from outside, including any firewall layer.
How to block or allow Naver in robots.txt
This rule covers the single crawler Naver operates. Add it to the robots.txt file at the root of your domain.
Block Naver completely
User-agent: Yeti
Disallow: /
Allow Naver explicitly
User-agent: Yeti
Allow: /
These Naver rules ask; they do not enforce. If a Naver token ignores them, block it at the server or CDN. Paths are case-sensitive, and each rule matches the token, not the full user-agent string.
Frequently asked questions about Naver
What crawler does Naver run?
Naver operates 1 crawler in our directory: Naver Search (user-agent Yeti).
Should I block Naver?
Keep it allowed if you want traffic from Naver Search, especially from South Korea. The SEO impact score for blocking is 10/10, where 10 means blocking costs you the most visibility.
How do I block Naver in robots.txt?
Add the following to robots.txt at your domain root: User-agent: Yeti then Disallow: /.
Does blocking Naver hurt my search rankings?
Blocking impact is rated: Critical - Blocking removes you from search results. Naver Search is a search-indexing crawler, so blocking it can remove your pages from the corresponding search results. Block it only if you intend to leave that index. Every crawler in this group is rated the same way, so there is no subset here that is safe to block for ranking purposes.