# Naver AI Briefing Monitor – Brand Visibility in AI Search (`leoworks/naver-ai-briefing-monitor`) Actor

Track your brand in Naver's AI briefing (AI 브리핑), the generative answer at the top of Korea's #1 search engine. Capture the answer, cited sources, AI ads and related questions, and see if your brand or competitors are mentioned and recommended.

- **URL**: https://apify.com/leoworks/naver-ai-briefing-monitor.md
- **Developed by:** [Leoworks](https://apify.com/leoworks) (community)
- **Categories:** AI, SEO tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 query checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Naver AI Briefing Monitor – Brand Visibility in AI Search

Naver — Korea's #1 search engine — now answers many searches with an **AI briefing (AI 브리핑)**: a generated answer at the top of the results, with cited sources and even AI-written ads. This Actor tells you **what that answer says, which sources it cites, which ads appear in it, and whether your brand and competitors are mentioned or recommended.**

Think of it as AI-search visibility (GEO/AEO) tracking for Korea.

**Use it to:** track brand mentions in Naver AI answers · see which blogs and sites Naver's AI cites for your category · monitor competitors' visibility in AI search · find AI-briefing ads in your keywords · Korean generative engine optimization (GEO) reporting.

### What you get (one row per query)

| Field | Meaning |
|---|---|
| `hasBriefing` | Whether Naver showed an AI briefing for the query |
| `answerText` | The AI answer (clean text, footnotes removed) |
| `quickAnswer` | The short highlighted answer, when shown |
| `citations[]` | Cited sources: `title`, `url`, `source`, `platform` (Naver Blog, Naver Clip, Naver Influencer, external sites…), `publishedAt` |
| `brandMentions[]` | For each brand/competitor: `mentioned`, `recommended`, `sentiment`, probabilities, and `citedSources` (how many cited sources name it) |
| `adsInBriefing[]` | Ads Naver inserted into the AI briefing: `advertiser`, `text`, `headline` |
| `relatedQuestions[]` | Follow-up questions, when shown |
| `checkedAt`, `checkedAtKst` | Check time (UTC and Korea time) |

### How to use

```json
{
  "queries": ["무선청소기 추천 2026", "콜라겐 효과"],
  "brandNames": ["다이슨"],
  "competitorNames": ["삼성", "LG"]
}
```

Use **brand names** (e.g. `삼성`, `LG`) rather than product-line names; the AI answer usually names the brand. Schedule the Actor to watch how answers change over time.

#### Query tips (observed 2026-10-02, sample of 20 queries)

AI briefings appeared for **8 of 20** test queries. They showed up mostly for **informational, how-to, review and comparison** queries ("콜라겐 효과", "전기포트 세척 방법", "갤럭시 버즈3 후기", "헬리녹스 체어원 vs 체어제로") and rarely for bare "OO 추천" or brand-name-only queries. Queries without a briefing cost only the basic check fee.

### Pricing

Pay only for results — no subscription. You pay the full price only when an AI briefing is actually shown.

| Event | Price | When |
|---|---|---|
| `query-checked` | $0.003 | One query checked on Naver search (whether an AI briefing appears). |
| `briefing-captured` | $0.01 | An AI briefing was shown: answer, citations, related questions, ads and brand judgments captured (added on top of the query check). |

**Cost examples**

| Run | Cost |
|---|---|
| 100 queries, no AI briefing shown | $0.30 |
| 100 queries, all with an AI briefing | $1.50 |
| 100 queries, 40% with an AI briefing (typical in our test) | $0.78 |
| 20 queries checked daily for 30 days, 40% with briefing | $4.68 |

With the free $5 monthly Apify credit you can check about **641 queries** (at a 40% briefing rate).

Queries that fail to load are reported with an `error` field and **not charged**. If you set a maximum cost per run, the Actor stops cleanly when it is reached.

### Accuracy

- AI briefing presence, answer and cited sources matched what a browser shows for 20 test queries.
- Brand mention / recommendation judgments: **97%** agreement with hand labels (38 judgments).

### Limits

| Item | Limit |
|---|---|
| Brands + competitors | Up to 10 per run |
| Surface | PC search (default) or mobile search; in our tests mobile showed briefings slightly less often |
| Personalization | Checks run logged out; answers can change over time and between sessions |
| Ads | Reported when Naver attaches them to the briefing; impression tracking URLs are never called |

### Disclaimer

> Independent tool — not affiliated with, endorsed by or sponsored by NAVER Corp. "Naver" is a trademark of its owner and is used only to describe the data source. AI briefings are generated by Naver and may contain inaccuracies.

### Changelog

See the Changelog tab.

# Changelog

This Actor's version history is a separate document: https://apify.com/leoworks/naver-ai-briefing-monitor/changelog.md

# Actor input Schema

## `queries` (type: `array`):

Korean search queries to check. Informational, how-to, review and comparison queries trigger AI briefings most often (see README).

## `brandNames` (type: `array`):

Brands to check in each AI briefing (Korean or English).

## `competitorNames` (type: `array`):

Competitors to check the same way. Brands + competitors: up to 10 in total.

## `surface` (type: `string`):

PC search shows AI briefings slightly more often in our tests.

## `includeAds` (type: `boolean`):

Also request the ads Naver attaches to the AI briefing.

## `maxConcurrency` (type: `integer`):

Queries checked in parallel.

## `residentialFallback` (type: `boolean`):

Retry failing requests through Korean residential proxy.

## `proxyConfiguration` (type: `object`):

Default Apify datacenter proxy works for most users.

## `healthCheck` (type: `boolean`):

Internal: fail the run when results look degraded (used by the developer's scheduled checks).

## Actor input object example

```json
{
  "queries": [
    "콜라겐 효과",
    "전기포트 세척 방법"
  ],
  "brandNames": [],
  "competitorNames": [],
  "surface": "pc",
  "includeAds": true,
  "maxConcurrency": 5,
  "residentialFallback": true,
  "proxyConfiguration": {
    "useApifyProxy": true
  },
  "healthCheck": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "queries": [
        "콜라겐 효과",
        "전기포트 세척 방법"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("leoworks/naver-ai-briefing-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "queries": [
        "콜라겐 효과",
        "전기포트 세척 방법",
    ],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("leoworks/naver-ai-briefing-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "queries": [
    "콜라겐 효과",
    "전기포트 세척 방법"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call leoworks/naver-ai-briefing-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leoworks/naver-ai-briefing-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/xogJYXLpSObjq2Cnt/builds/ttGgFNyvacarYOLed/openapi.json