`Ads-Naver`

Naver Search Ads says Ads-Naver visits final landing URLs registered in the ads center and collects the public content of those pages so ads can be matched and ranked. Registering the URL is treated as permission to collect, and the robot does not consult robots.txt. The FAQ shows that a file with User-agent: * and Disallow: / still does not stop collection of a registered landing page. To stop collection, the advertiser sends the URL to the ads customer center. That request is not a robots.txt rule. This check still reports the RFC 9309 decision and does not apply the ads-center exception. The identification guide names this token separately from Yeti. This check matches the whole token.

robots.txt token: Ads-Naver
Operator: Naver
Kind: ads_check
robots.txt: does_not_follow. The vendor says this crawler does not follow robots.txt rules.
HTTP user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko; compatible; Ads-Naver/1.1; +https://naver.me/adsn) Chrome/W.X.Y.Z Safari/537.36 The FAQ says the Chrome version in this string changes and that a firewall should match the Ads-Naver token, not one Chrome version. Document fetches and resource fetches use the same user-agent. The version can change without notice.
IP list: None on the cited page. The FAQ does not publish an IP list. It says a reverse DNS name must end in .naver.com and points to the Search Advisor guide for IP details. Botcard does not copy addresses.
Source: 광고용 웹수집 검색로봇 'Ads-Naver'가 뭔가요?. Retrieved 2026-10-18, page says updated 2026-08-12.

JSON

curl -s https://whosthatbot.com/v1/crawlers/ads-naver

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Ads-Naver on /docs and allows *. The call does not fetch a host.

curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: Ads-Naver\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["ads-naver"]}}}'

That call returns fetched_target false. This row is disallow via group Ads-Naver, rule Disallow: /.