Promptwatch Logo

adsnaver

adsnaver is tied to paid search advertising, not Naver's general web index.
Naveradsnaver
Search Engine CrawlerAdvertising

What is adsnaver?

adsnaver is tied to paid search advertising, not Naver's general web index. Naver periodically sends it to URLs registered in the advertising system, including business-channel homepages and final landing pages attached to keywords or ad material.

The crawler reads the public content of a landing page so Naver can assess site quality and relate the ad to suitable user searches. That information contributes to ad matching and ranking. A request is therefore part of ad review and delivery operations, even when no shopper has clicked the ad at that moment.

Naver's current documentation calls the user agent Ads-Naver/1.1. The request can also contain Windows, AppleWebKit, Chrome, and Safari tokens because the crawler retrieves page resources such as JavaScript and CSS. Detection should retain the Ads-Naver product name instead of classifying the browser-shaped form as human traffic.

Nothing in the supplied evidence identifies this crawler as an AI training source. Its documented visibility effect is on Naver search ads, where the fetched page can be checked, matched, and ranked. It should not be credited with organic Naver indexing or inclusion in AI answers.

Relevant for AI search

Is adsnaver relevant for AI search?

Yes. adsnaver collects pages for an AI product, so what it can crawl influences how AI systems describe your brand.

adsnaver feeds a search index that also powers that engine's AI answer features and overviews. One crawl can serve a classic results page and a generated summary, so blocking it costs you both the rankings you would expect and a growing share of AI answers built on the same index.

How to handle adsnaver

Advertisers should keep each registered landing page reachable if they want Naver to evaluate it for ad quality and relevance. Do not register account pages or other URLs that should not be fetched. If a landing page is retired, update the ad configuration as well as the website.

This valid group covers the product token in Naver's current user agents and the normalized token in the directory metadata:

User-agent: Ads-Naver
User-agent: adsnaver
Disallow: /

Compliance is partial. the directory marks robots support true, but the record description and Naver's ad guidance say registration is treated as consent and registered URLs may be collected despite general robots.txt restrictions. Other Naver help text indicates that an Ads-Naver-specific block can prevent download, so verify the exact case in ad diagnostics and server logs. To stop collection reliably, remove the URL from the ad system or request a stop through Naver Ads support; a server block can also prevent access but may disrupt ad review and delivery.

Examples

  • An advertiser changes the price and offer text on a registered landing page, then watches for an Ads-Naver revisit before checking the ad's review status.
  • An analytics team removes browser-shaped Ads-Naver requests from human sessions so resource fetching does not inflate visitor counts.
  • A campaign manager retires a landing page in Naver Ads and at the origin instead of expecting a wildcard robots rule alone to stop collection.

Frequently asked questions about adsnaver

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

Naver documents visits to sites and final landing URLs registered for its search advertising products. The crawler periodically collects their publicly rendered content.

Be the brand AI recommends

Monitor your brand's visibility across ChatGPT, Claude, Perplexity, and Gemini. Get actionable insights and create content that gets cited by AI search engines.

Promptwatch Dashboard