Naver AI Overview Monitor — Korean AI Briefing & Brand Citations

Naver AI Overview Monitor helps Korean AEO / GEO teams and AI agents extract Naver's public AI Briefing (AI Overview / AI 브리핑) for search queries into structured JSON: answer text, cited sources, related questions, media, and optional brand or domain match.

Built for Apify: run via Console, API, schedules, or MCP (apify--naver-ai-overview-monitor). Billing is Pay per event plus Apify platform usage; the live Pricing tab is the current source of truth.

Best fit for this Actor

• Use this Actor when you need the current Naver AI Briefing answer and citation list for Korean informational keywords.
• Prefer question-style Korean queries (for example 당뇨병 증상) and Apify Residential proxies with country KR.
• Start with the Console prefill, confirm briefingPresent and references[], then batch more keywords.
• For Google AI Overviews outside Korea, continue with Google AI Overviews Scraper when you need Google AIO citations.
• For brand-name mentions across ChatGPT / Perplexity / Claude / Gemini, then use AI Search Brand Monitor.
• Sibling routing: keep Naver Briefing work here; keep Google AIO and multi-LLM reputation work on the linked Actors above.

Practical scenario

A Korean beauty brand tracks whether 선크림 추천 cites their domain. They paste the keyword, set targetDomain to their site, run weekly, and download the dataset. Each row shows whether an AI Briefing appeared, which domains Naver cited, and whether brandMatch.matched is true so the AEO team can prioritize content before the next campaign.

Quick start input

{
  "query": "당뇨병 증상",
  "targetDomain": "namu.wiki",
  "device": "desktop",
  "includeRelatedQuestions": true,
  "includeMedia": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "KR"
  }
}

Provide query, queries, or both (merged and de-duplicated, max 50).

How to use

1. Open the Actor in Apify Console
2. Enter a Korean informational query such as 당뇨병 증상
3. Optionally set targetDomain or brandNames
4. Keep Proxy on Apify Residential with country KR
5. Start the Actor and download JSON / CSV from the dataset

What data you get

Field	Description
query	Search query checked
briefingPresent	Whether Naver showed an AI Briefing
answerMarkdown	Briefing answer text
textBlocks[]	Paragraph blocks
references[]	Cited sources (index, title, url, domain, snippet, source)
referenceCount / uniqueDomainCount	Citation counts
media[] / relatedQuestions[]	Optional media and follow-ups
brandMatch	Domain / brand-name match when configured
source	camoufox or serpapi
scrapedAt	ISO collection time

Example output (one query)

{
  "query": "당뇨병 증상",
  "device": "desktop",
  "serpUrl": "https://example.com/naver-search-serp?q=diabetes-symptoms",
  "briefingPresent": true,
  "answerMarkdown": "당뇨병의 주요 증상에는 다음이 포함됩니다…",
  "textBlocks": ["당뇨병의 주요 증상에는 다음이 포함됩니다…"],
  "references": [
    {
      "index": 1,
      "title": "당뇨병 - 관련 의학 정보",
      "url": "https://example-hospital.example/diabetes",
      "domain": "example-hospital.example",
      "snippet": null,
      "source": null
    }
  ],
  "referenceCount": 4,
  "uniqueDomainCount": 4,
  "media": [],
  "relatedQuestions": [{ "question": "당뇨병 진단 기준은?" }],
  "brandMatch": {
    "targetDomain": "namu.wiki",
    "matched": false,
    "position": null,
    "citedUrl": null,
    "matchCount": 0,
    "brandNameHits": []
  },
  "source": "camoufox",
  "scrapedAt": "2026-01-15T12:00:00.000Z",
  "warnings": []
}

OUTPUT and RUN_SUMMARY in the default key-value store hold outcome, itemsPushed, and charged event counts. Download the dataset as JSON, CSV, Excel, or HTML.

Pricing

This Actor uses Pay per event plus Apify platform usage. The live Pricing tab is the current source of truth for billing details.

Event	Price
Actor start	$0.00005
naver-ai-overview (primary)	$0.012 per resolved query
brand-match-detected	$0.005 when a brand or domain match is recorded

A ten-query monitoring sample with no brand hits is ten naver-ai-overview events plus start and Residential platform usage. Rows may show briefingPresent: false when Naver omits a Briefing; the query is still resolved when a dataset row is saved.

Use through the API

curl -X POST "https://api.apify.com/v2/acts/khadinakbar~naver-ai-overview-monitor/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"query":"당뇨병 증상","targetDomain":"namu.wiki","proxyConfiguration":{"useApifyProxy":true,"apifyProxyGroups":["RESIDENTIAL"],"apifyProxyCountry":"KR"}}'

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('khadinakbar/naver-ai-overview-monitor').call({
  query: '당뇨병 증상',
  targetDomain: 'namu.wiki',
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Use with AI agents through Apify MCP

Check Naver AI Briefing for 당뇨병 증상 with targetDomain namu.wiki. Return briefingPresent, references domains, and brandMatch. Read the dataset overview view and OUTPUT.outcome after the run. Budget: about $0.012 per query plus Residential KR platform usage. Scope: public Naver AI Briefing rows only. Provenance: source plus scrapedAt on each row.

Connect via https://mcp.apify.com. MCP tool: apify--naver-ai-overview-monitor. Keep concurrency low on the first call.

Best results

• Prefer informational Korean queries for stable Briefing yield
• Use Residential KR proxies for the primary Camoufox path
• Keep concurrency at one worker while confirming yield
• Supply optional serpApiKey only when you want SerpApi BYOK fallback; the caller must supply their own key for the run, and the value is never written to the dataset, output, or logs
• Confirm OUTPUT.outcome and itemsPushed before treating an empty dataset as finished work

Builder's note

I found that baking one Residential proxy URL into the Camoufox launch options reused a dead exit across every retry, so this Actor rotates sessions through Apify proxyConfiguration instead. I also found that Naver Open API Search products omit AI Briefing, which is why the public integrated-search page plus structural “AI 브리핑” parsing is the primary path, with optional SerpApi BYOK as a caller-supplied recovery route.

Responsible use

Use only for lawful collection and analysis of public Naver Search AI Briefing content you are authorized to access. Follow applicable laws and Naver’s terms. Naver is a trademark of its respective owner. This independent Actor is not affiliated with, associated with, or endorsed by Naver Corp. SerpApi is a trademark of its respective owner. This Actor is not affiliated with or endorsed by SerpApi.

Support

Open an issue on the Actor’s Issues tab for feedback or custom workflow help.