# Naver DataLab Search Trends Scraper (네이버 데이터랩 트렌드) (`magenta_courser/naver-datalab-trends-scraper`) Actor

Enter Korean keywords and get Naver DataLab search trends (검색어트렌드) as flat rows: one row per keyword and day, week or month with the 0-100 interest ratio, filtered by device, gender and age. More than 5 keywords are put on one common scale. No Naver API key or login.

- **URL**: https://apify.com/magenta_courser/naver-datalab-trends-scraper.md
- **Developed by:** [SUNGHWAN CHO](https://apify.com/magenta_courser) (community)
- **Categories:** SEO tools, Marketing, Business
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.04 / 1,000 trend data points

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 DataLab Trends Scraper (네이버 데이터랩 검색어트렌드) | Korean Search Trends by Keyword, Device, Gender & Age (2026)

**Languages:** English · [한국어](#korean) · [中文](#chinese) · [日本語](#japanese)

[![$0.04 per 1,000 Naver DataLab trend data points, one flat row per keyword and period](https://raw.githubusercontent.com/experimory-crypto/naver-map-scraper-examples/main/assets/hero-naver-datalab-trends-scraper.png)](https://apify.com/magenta_courser/naver-datalab-trends-scraper)

Enter **Korean keywords** and get **Naver DataLab search trends (검색어트렌드)** as flat JSON rows: one row per keyword and day, week or month, with the 0 to 100 search interest ratio, for the device, gender and age bands you choose. More than 5 keywords are put on one common scale. No Naver login, no API key, no browser.

Naver DataLab is Naver's own trend tool for its search engine, comparable to Google Trends. This Actor reads the public DataLab chart for your keywords and returns the numbers behind it. Part of a small set of Korean data Actors from one maintainer: [Naver Search](https://apify.com/magenta_courser/naver-search-scraper), [Naver News](https://apify.com/magenta_courser/naver-news-scraper), [Naver AI Briefing](https://apify.com/magenta_courser/naver-ai-briefing-scraper) and [Naver Shopping ranks](https://apify.com/magenta_courser/naver-shopping-rank-tracker).

> **Free plan:** Apify's $5 monthly credit covers about 125,000 data points with this Actor (at the per-row price; each run adds a $0.00005 start fee).

### Why choose this Actor?

**$0.04 per 1,000 data points.**<br>
You pay $0.00004 per row saved: the value of one keyword for one day, week or month. The default run (two keywords, weekly, the last 12 months) saved 106 rows in run `cwBmExKECTnXeScqq`, which is $0.0042. A keyword Naver has no data for returns no rows and costs nothing.

**More than 5 keywords on one scale.**<br>
Naver compares at most 5 keywords at once, and every comparison has its own 0 to 100 scale. Give this Actor up to 41 keywords and it chains the comparisons through your first keyword, so `ratio` is comparable across all of them. `rawRatio` keeps the value exactly as Naver returned it.

**Audience filters as plain inputs.**<br>
`device` (PC or mobile), `gender` and `ages` (11 age bands from 0-12 to 60+) are the same filters the DataLab page offers, and every row repeats the filters it was fetched with.

**Flat rows for code and AI agents.**<br>
One required input (`keywords`). Dates default to the last 12 months. Each row has the same 17 keys and numbers are numbers.

**Measured, not estimated.** Two keywords, weekly, 12 months: 106 rows in 5.5 seconds at 256 MB (run `cwBmExKECTnXeScqq`, build 0.1.1, 2026-11-11, default datacenter proxy, 2 requests, no retries). Seven keywords, daily, 12 months, two comparisons: 2,190 rows in 38.1 seconds, 4 requests, no retries (run `BaApMHlVoNdnegTik`, same build).

### Quick start

Two trend lines, weekly, for the last 12 months. This is the default input; at the current price the run above cost about $0.004.

```json
{
  "keywords": ["선크림, 썬크림", "수분크림"]
}
```

[Open the Actor input](https://console.apify.com/actors/0Cp2Peu3H2haLHEzv/input), type one keyword per line, and click **Start**. `선크림, 썬크림` adds up two spellings of "sunscreen" into one line; `수분크림` is "moisturizer". Export the dataset as JSON, CSV or Excel.

#### Copy to your AI assistant

Paste this into ChatGPT, Claude, Cursor or another assistant so it can call the Actor for you:

```text
Use the Apify Actor magenta_courser/naver-datalab-trends-scraper to get Naver DataLab search trends (relative search interest on Naver, South Korea) for keywords.

Input (JSON): "keywords" is a list of trend lines (required, up to 41). A line is a keyword as Koreans search it ("선크림"), several spellings added up with commas ("선크림, 썬크림", up to 20), optionally with your own label before a colon ("Sunscreen: 선크림, 썬크림"). Optional: "timeUnit" ("date", "week" or "month", default "week"), "startDate" and "endDate" ("YYYY-MM-DD", data starts 2016-01-01, default the last 12 months ending yesterday in Korea time), "device" ("all", "pc", "mobile"), "gender" ("all", "female", "male"), "ages" (list from "0-12", "13-18", "19-24", "25-29", "30-34", "35-39", "40-44", "45-49", "50-54", "55-59", "60+"; empty = all ages).

Output: one dataset row per keyword and period with keyword, searchTerms, period ("YYYY-MM-DD": the day, the Monday of the week, or the first day of the month), ratio (search interest, comparable across all keywords of the run; 100 = the highest point of the first five keywords), rawRatio (0-100 exactly as Naver returned it), timeUnit, device, gender, ages, startDate, endDate, comparisonGroup, comparedWith, isRescaled, sourceUrl, scrapedAt. These are relative ratios, not search counts. With more than 5 keywords put a popular keyword first: it is the common reference.

Run it through the Apify API: POST https://api.apify.com/v2/acts/magenta_courser~naver-datalab-trends-scraper/run-sync-get-dataset-items with my Apify token as a Bearer token and the input as the JSON body. Or connect the MCP server https://mcp.apify.com?tools=magenta_courser/naver-datalab-trends-scraper.

Price: $0.00004 per row. Rows = keywords x periods, so prefer "week" or "month" for long date ranges.
```

#### Use it over MCP

Add this server to Claude Desktop, Cursor or any MCP client, authenticated with your Apify token:

```text
https://mcp.apify.com?tools=magenta_courser/naver-datalab-trends-scraper
```

The agent only has to fill `keywords`; everything else has a default.

### Key features

- **Daily, weekly or monthly rows.** `period` is the day, the Monday of the week, or the first day of the month, always as `YYYY-MM-DD`.
- **Data from 2016-01-01** up to yesterday in Korea time.
- **Up to 41 keywords per run.** The first 5 form the first comparison; every later comparison holds your first keyword plus 4 new ones, up to 10 comparisons.
- **One common scale.** `ratio` is converted to the scale of the first comparison; `isRescaled`, `comparisonGroup` and `comparedWith` show how each row was obtained.
- **Spelling variants in one line.** `선크림, 썬크림` makes Naver add up both spellings (up to 20 terms per line).
- **Your own labels.** `Sunscreen: 선크림, 썬크림` returns the line as `keyword: "Sunscreen"`, with the actual terms in `searchTerms`.
- **Device, gender and age filters**, repeated on every row.
- **A link back to the chart.** `sourceUrl` is the Naver DataLab result page of that comparison.
- **A free run summary.** The key-value store record `RUN_SUMMARY` has the resolved period and filters, the status of each comparison and the keywords without data.
- **Clean stop at your cost limit.** Rows stored equal rows charged; comparisons that did not fit are marked `budgetLimited`.

### How to scrape Naver DataLab search trends

#### Compare up to 5 keywords, weekly, last 12 months

All five are on Naver's own scale: the highest point among them is 100.

```json
{
  "keywords": ["선크림", "수분크림", "클렌징오일", "립밤", "핸드크림"],
  "timeUnit": "week"
}
```

(Sunscreen, moisturizer, cleansing oil, lip balm, hand cream.)

#### Add up spelling variants and use English labels

```json
{
  "keywords": [
    "Sunscreen: 선크림, 썬크림",
    "Cushion: 쿠션팩트, 쿠션 파운데이션"
  ],
  "timeUnit": "week"
}
```

#### Daily values for a fixed period

```json
{
  "keywords": ["선크림, 썬크림", "수분크림"],
  "timeUnit": "date",
  "startDate": "2026-05-01",
  "endDate": "2026-10-31"
}
```

#### Monthly seasonality since 2016

For `week` and `month` Naver works with whole months, so the period is widened to full months.

```json
{
  "keywords": ["선크림, 썬크림"],
  "timeUnit": "month",
  "startDate": "2016-01-01"
}
```

#### One audience segment: women aged 19 to 29 on mobile

Run the same keywords again with other filters to compare segments. Each run has its own scale, so compare the shape of the curves, not the values, between runs.

```json
{
  "keywords": ["선크림, 썬크림", "수분크림"],
  "timeUnit": "week",
  "device": "mobile",
  "gender": "female",
  "ages": ["19-24", "25-29"]
}
```

#### More than 5 keywords on one scale

Put a reasonably popular keyword first; it is added to every comparison as the common reference.

```json
{
  "keywords": [
    "선크림, 썬크림",
    "수분크림",
    "Cushion: 쿠션팩트, 쿠션 파운데이션",
    "클렌징오일",
    "립밤",
    "핸드크림",
    "토너패드"
  ],
  "timeUnit": "month"
}
```

### Input parameters

| Field | Type | Default | Description |
|---|---|---|---|
| `keywords` | array of strings | — (required) | One trend line per row, up to 41. See "Keyword lines" below. Duplicate lines are dropped. |
| `timeUnit` | string | `week` | `date` (daily), `week` or `month`. |
| `startDate` | string | one year before `endDate` | `YYYY-MM-DD`. Naver has data from 2016-01-01; an earlier date is moved to that day. |
| `endDate` | string | yesterday (Korea time) | `YYYY-MM-DD`. A later date is moved to yesterday. |
| `device` | string | `all` | `all`, `pc` or `mobile`. |
| `gender` | string | `all` | `all`, `female` or `male` (as registered on the Naver account). |
| `ages` | array of strings | `[]` (all ages) | Any of `0-12`, `13-18`, `19-24`, `25-29`, `30-34`, `35-39`, `40-44`, `45-49`, `50-54`, `55-59`, `60+`. |
| `proxyConfiguration` | object | Apify Proxy | Keep the default (datacenter). Switch to RESIDENTIAL with country KR only if the log shows repeated request errors. |

#### Keyword lines

| You write | Naver measures | `keyword` in the output |
|---|---|---|
| `선크림` | searches for 선크림 | `선크림` |
| `선크림, 썬크림` | both spellings added up (up to 20 terms) | `선크림` |
| `Sunscreen: 선크림, 썬크림` | both spellings added up | `Sunscreen` |

A line must not contain `__` (Naver DataLab does not accept it).

#### How more than 5 keywords are put on one scale

Naver sets the highest point among the compared keywords to 100, separately for every comparison. Keywords 1 to 5 form comparison 1. Every later comparison holds your first keyword plus up to 4 new ones. Because the first keyword appears in every comparison, the Actor can compute how the two scales relate (the sum of the first keyword's values in comparison 1 divided by the sum of its values in the later comparison, over the same periods) and multiply the later values by that factor.

So `ratio` can be above 100 for a keyword that is more popular than everything in comparison 1. In run `BaApMHlVoNdnegTik`, `핸드크림` (hand cream) was fetched in comparison 2, where its peak was `rawRatio: 100`; on the common scale that peak is `ratio: 114.41861`.

Limits: if the first keyword has no search volume in a comparison, there is nothing to align on and `ratio` is `null` for that comparison's rows (use `rawRatio`). If comparison 1 fails, the later ones are skipped. The first keyword's own rows come from comparison 1 only.

### What data can you extract from Naver DataLab?

One row per keyword and period.

| Field | Type | Description |
|---|---|---|
| `keyword` | string | Name of the trend line: your label, or the first search term of the input line. |
| `searchTerms` | string | The search terms Naver added up for this line, comma-separated. |
| `period` | string | `YYYY-MM-DD`: the day, the Monday of the week, or the first day of the month. |
| `ratio` | number | Search interest, comparable across all keywords of the run. 100 = the highest point among the keywords of the first comparison in the selected period. `null` only when the first keyword has no search volume to align on. |
| `rawRatio` | number | The 0 to 100 value exactly as Naver returned it for this keyword's own comparison. |
| `timeUnit` | string | `date`, `week` or `month`. |
| `device` | string | `all`, `pc` or `mobile`. |
| `gender` | string | `all`, `female` or `male`. |
| `ages` | string | `all` or the selected age bands, comma-separated. |
| `startDate`, `endDate` | string | The period that was requested from Naver, after defaults and widening to full months. |
| `comparisonGroup` | integer | Which Naver comparison the keyword was fetched in. Always `1` with up to 5 keywords. |
| `comparedWith` | string | All keywords of that comparison, comma-separated. |
| `isRescaled` | boolean | `true` when `ratio` was converted from `rawRatio` to the scale of the first comparison. |
| `sourceUrl` | string | The Naver DataLab result page for this comparison. |
| `scrapedAt` | string | Fetch time (UTC, ISO 8601). |
| `schemaVersion` | integer | Output schema version, currently `1`. |

**Run summary** (key-value store record `RUN_SUMMARY`, not charged): `status` (`completed`, `partial`, `budgetLimited`, `failed`), `rowsSaved`, the resolved `timeUnit`, `startDate`, `endDate`, `device`, `gender`, `ages`, `requests`, `retries`, and one entry per comparison with `keywords`, `status`, `rows`, `keywordsWithoutData` and `errorMessage`.

#### Output example: weekly row

From run `cwBmExKECTnXeScqq` (2026-11-11, build 0.1.1), the default input. Unedited. `period` is the Monday of the week.

```json
{
  "keyword": "선크림",
  "searchTerms": "선크림, 썬크림",
  "period": "2025-11-03",
  "ratio": 31.36391,
  "rawRatio": 31.36391,
  "timeUnit": "week",
  "device": "all",
  "gender": "all",
  "ages": "all",
  "startDate": "2025-11-01",
  "endDate": "2026-11-10",
  "comparisonGroup": 1,
  "comparedWith": "선크림, 수분크림",
  "isRescaled": false,
  "sourceUrl": "https://datalab.naver.com/keyword/trendResult.naver?hashKey=N_2b24d0d5229592854056f1537ef549dd",
  "scrapedAt": "2026-11-11T08:16:27.889Z",
  "schemaVersion": 1
}
```

#### Output example: rescaled daily row from a second comparison

From run `BaApMHlVoNdnegTik` (2026-11-11, build 0.1.1): seven keyword lines, daily, mobile, female, ages 19 to 29. Unedited. This keyword was sixth in the input, so it was fetched in comparison 2 and converted to the scale of comparison 1.

```json
{
  "keyword": "핸드크림",
  "searchTerms": "핸드크림",
  "period": "2025-12-09",
  "ratio": 114.41861,
  "rawRatio": 100,
  "timeUnit": "date",
  "device": "mobile",
  "gender": "female",
  "ages": "19-24, 25-29",
  "startDate": "2025-11-11",
  "endDate": "2026-11-10",
  "comparisonGroup": 2,
  "comparedWith": "선크림, 핸드크림, zzqqxxnonexistentkw",
  "isRescaled": true,
  "sourceUrl": "https://datalab.naver.com/keyword/trendResult.naver?hashKey=N_122bd8e76e4ebe9ba4d1e47e85c7bf71",
  "scrapedAt": "2026-11-11T08:11:47.007Z",
  "schemaVersion": 1
}
```

The third keyword of that comparison was a made-up word for testing. Naver had no data for it, so it produced no rows and is listed under `keywordsWithoutData` in `RUN_SUMMARY`.

#### Output example: monthly row

From run `UvMzUMW7M4dhPQ9rX` (2026-11-15, build 0.1.1), input `timeUnit: "month"`, `startDate: "2024-01-15"`, `endDate: "2025-12-20"`. Unedited. The period was widened to full months (`2024-01-01` to `2025-12-31`), which gave 24 rows per keyword; May 2024 was the peak of the two keywords.

```json
{
  "keyword": "선크림",
  "searchTerms": "선크림, 썬크림",
  "period": "2024-05-01",
  "ratio": 100,
  "rawRatio": 100,
  "timeUnit": "month",
  "device": "all",
  "gender": "all",
  "ages": "all",
  "startDate": "2024-01-01",
  "endDate": "2025-12-31",
  "comparisonGroup": 1,
  "comparedWith": "선크림, 수분크림",
  "isRescaled": false,
  "sourceUrl": "https://datalab.naver.com/keyword/trendResult.naver?hashKey=N_70e872b460035b60d8539ca819a36c97",
  "scrapedAt": "2026-11-15T14:03:53.646Z",
  "schemaVersion": 1
}
```

### Advanced usage

#### Find each keyword's peak month

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("magenta_courser/naver-datalab-trends-scraper").call(run_input={
    "keywords": ["선크림, 썬크림", "핸드크림", "립밤"],
    "timeUnit": "month",
    "startDate": "2022-01-01",
})
peaks = {}
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
    best = peaks.get(row["keyword"])
    if row["ratio"] is not None and (best is None or row["ratio"] > best["ratio"]):
        peaks[row["keyword"]] = row
for keyword, row in peaks.items():
    print(keyword, row["period"], row["ratio"])
```

#### Rank a shortlist of candidate keywords

Send up to 41 candidates in one run with a well-known keyword on the first line, then average `ratio` per `keyword`. Because all rows share one scale, the averages can be ranked against each other.

#### Compare audience segments

Run the same keywords once per segment (for example `gender: "female"` and `gender: "male"`). Naver rescales every query to its own peak, so values from two runs are not on the same scale: compare when each curve rises and falls, or the ratio between keywords inside each run.

#### Check what was actually requested

`startDate` and `endDate` on every row, and in `RUN_SUMMARY`, are the dates sent to Naver after defaults, the 2016-01-01 lower bound, the "yesterday" upper bound and widening to full months.

#### One call from the command line

```bash
curl -X POST "https://api.apify.com/v2/acts/magenta_courser~naver-datalab-trends-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keywords": ["선크림, 썬크림", "수분크림"], "timeUnit": "month"}'
```

### How much does it cost to scrape Naver DataLab?

Pay per event, no subscription. The price below has been in effect since 2026-11-11 and is the same on every Apify plan (this Actor has no plan-tier discount).

| Event | Price | When |
|---|---|---|
| Trend data point | **$0.00004** per row | Every row saved to the dataset: one keyword for one period. |
| Actor start | $0.00005 | Once per run. |

Not charged: the `RUN_SUMMARY` record, keywords without data, comparisons that fail, retries.

Rows = keywords with data × periods. Worked examples:

| Job | Rows | Cost |
|---|---|---|
| Default run: 2 keywords, weekly, last 12 months (run `cwBmExKECTnXeScqq`) | 106 | **$0.0042** |
| 2 keywords, monthly, 24 months (run `UvMzUMW7M4dhPQ9rX`) | 48 | **$0.0019** |
| 6 keywords with data, daily, 12 months (run `BaApMHlVoNdnegTik`) | 2,190 | **$0.088** |
| 41 keywords, monthly, 2016-01 to 2026-10 (130 months) | up to 5,330 | up to **$0.21** |
| Any job | 1,000 | **$0.04** |

Set **Maximum cost per run** in the console to cap a run. It stops cleanly: only the rows that fit the budget are stored and charged, and the comparisons that did not fit are marked `budgetLimited` in `RUN_SUMMARY`.

### Scheduling and integrations

- **Schedules.** In Apify Console, create a weekly or monthly schedule and leave `startDate` and `endDate` empty: every run then covers the 12 months ending yesterday. Each run is a fresh snapshot on its own scale; the Actor keeps no history between runs.
- **Webhooks and automation.** Send the dataset to Slack, Google Sheets, Make, Zapier or n8n with Apify integrations, or call your own endpoint with a webhook when a run finishes.
- **API clients.** Any HTTP client works; official clients exist for Python (`apify-client`) and JavaScript (`apify-client`).

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

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('magenta_courser/naver-datalab-trends-scraper').call({
    keywords: ['선크림, 썬크림', '수분크림'],
    timeUnit: 'week',
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
const latest = items.filter((r) => r.period === items[items.length - 1].period);
console.log(latest.map((r) => `${r.keyword}: ${r.ratio}`).join(', '));
```

### FAQ

**Do I need a Naver account or the Naver DataLab API key?**
No. The Actor reads the public DataLab search-term trend page without logging in, so there is no API key and no API quota of your own to manage.

**Does it return search volume?**
No. DataLab publishes ratios only: the highest point among the compared keywords in the selected period is 100 and everything else is scaled to it. A ratio of 50 means half as many searches as that peak. Absolute search counts are not available here.

**Can I compare numbers from two different runs?**
Not directly. Change the keywords, the period or a filter and Naver's scale changes. Compare rows of one run with each other. To compare many keywords, send them in one run (up to 41).

**Why is `ratio` above 100?**
With more than 5 keywords, 100 is the highest point of the first comparison. A keyword fetched in a later comparison that is more popular than that gets a `ratio` above 100. `rawRatio` never exceeds 100.

**Why does a weekly run start a few days after my start date?**
For `week` and `month` the period is widened to full months, and `period` is the Monday of each week. In run `cwBmExKECTnXeScqq` the requested period was 2025-11-01 to 2026-11-10; the first row was the week of Monday 2025-11-03 and the last the week of 2026-11-02, 53 rows per keyword.

**Why did a keyword return no rows?**
Naver has no trend data for it in the selected period and filters. Check the spelling or widen the filters. The keyword is listed under `keywordsWithoutData` in `RUN_SUMMARY` and nothing is charged for it.

**What happens when Naver rejects a request?**
A comparison is tried up to 5 times in total, each time on a new proxy session, with a growing pause. A query that Naver itself rejects (for example unusual characters) is not retried; that comparison is marked `failed` with Naver's reason. If one comparison fails, the others are still saved; the run fails only when no data could be fetched. The default datacenter proxy needed no retries in the runs named above.

**Does it cover Shopping Insight or regional trends?**
No. Only the search-term trend (검색어트렌드) part of DataLab is read.

**Is it legal to scrape Naver DataLab?**
The Actor reads a public page with aggregate statistics and does not log in. Whether your use is allowed depends on Naver's terms of service, your purpose and your local law; checking that is your responsibility.

**네이버 데이터랩 검색어 트렌드를 엑셀로 받을 수 있나요?**
네. 실행이 끝나면 데이터셋을 JSON·CSV·Excel로 내려받을 수 있습니다. 키워드가 5개를 넘어도 한 번에 넣으면 `ratio`가 같은 기준으로 맞춰져 나옵니다.

### More Korean data Actors

[![Naver AI Briefing Scraper: $0.002 per AI Briefing found](https://raw.githubusercontent.com/experimory-crypto/naver-map-scraper-examples/main/assets/hero-naver-ai-briefing-scraper.png)](https://apify.com/magenta_courser/naver-ai-briefing-scraper)

[![Naver Shopping Rank Tracker: top 1,000 ranks for any keyword](https://raw.githubusercontent.com/experimory-crypto/naver-map-scraper-examples/main/assets/hero-naver-shopping-rank-tracker.png)](https://apify.com/magenta_courser/naver-shopping-rank-tracker)

| Actor | What you put in → what you get |
|---|---|
| [Naver Search Scraper](https://apify.com/magenta_courser/naver-search-scraper) | Keywords → the Naver integrated search page as rows: section, rank, ad flag, title, URL, snippet, related searches. |
| [Naver AI Briefing Scraper](https://apify.com/magenta_courser/naver-ai-briefing-scraper) | Search queries → Naver's AI answer, its cited sources, and whether your domain is cited. |
| [Naver News Scraper](https://apify.com/magenta_courser/naver-news-scraper) | Keywords or article URLs → Naver News articles with publisher, times, URLs and optional full text. |
| [Naver Blog, Cafe & News Search Scraper](https://apify.com/magenta_courser/naver-blog-cafe-search-scraper) | Keywords → blog, cafe and news search results with title, URL, snippet and publish time. |
| [Naver Shopping Scraper & Keyword Rank Tracker](https://apify.com/magenta_courser/naver-shopping-rank-tracker) | Shopping keywords → ranked products with price, store, rating, reviews and stock. |
| [Naver Map Scraper](https://apify.com/magenta_courser/naver-place-search-scraper) | Keyword → businesses with address, phone, coordinates, rating, review counts. |
| [Naver Map Reviews Scraper](https://apify.com/magenta_courser/naver-place-reviews-scraper) | Place IDs or Naver Map URLs → visitor reviews with rating, text, dates, keyword codes and owner reply. |
| [Naver Place Multi-Location Review Monitor](https://apify.com/magenta_courser/multi-location-review-monitor) | Your locations → new reviews, owner replies added or edited, unanswered counts per location. |
| [Naver Place Rank Tracker](https://apify.com/magenta_courser/naver-place-rank-tracker) | Keywords + your place IDs → your rank in Naver Map search, with change since the last run. |
| [Kakao Map Reviews Scraper](https://apify.com/magenta_courser/kakaomap-reviews-scraper) | Kakao Map place IDs → visitor reviews, no reviewer personal data. |
| [Kakao Map Scraper](https://apify.com/magenta_courser/kakaomap-place-search-scraper) | Keyword → Kakao Map businesses, same field names as the Naver Map Actor. |
| [Korea MCP Server: Naver, Kakao Map](https://apify.com/magenta_courser/korea-local-data-mcp) | An MCP server with Naver Map search, Naver Place reviews and Kakao Map search as tools. |

Code examples for these Actors: [github.com/experimory-crypto/naver-map-scraper-examples](https://github.com/experimory-crypto/naver-map-scraper-examples).

### 한국어 안내 (Korean)

키워드를 넣으면 네이버 데이터랩 검색어트렌드 값이 키워드와 기간(일·주·월)마다 한 행으로 나옵니다. 각 행에는 0~100 기준의 검색 관심도 비율(`ratio`), 네이버가 돌려준 원래 값(`rawRatio`), 기간, 그리고 조회에 쓴 기기(PC·모바일)·성별·연령대 조건이 들어 있습니다. 네이버는 한 번에 5개까지만 비교하지만, 이 Actor는 첫 번째 키워드를 기준으로 비교를 이어 붙여 최대 41개 키워드를 같은 기준으로 맞춥니다. 쉼표로 여러 표기를 한 줄에 합칠 수 있고(최대 20개), 2016-01-01부터 한국 시간 기준 어제까지 조회됩니다. 요금은 행 1건당 $0.00004(1,000행 $0.04)이며 요금제 등급별 할인은 없고, 실행마다 시작 요금 $0.00005가 붙습니다. 데이터가 없는 키워드는 행이 나오지 않고 과금되지 않습니다. 제공하지 않는 것: 실제 검색량(횟수), 쇼핑인사이트, 지역별 트렌드, 서로 다른 실행 사이에서 바로 비교할 수 있는 값. 로그인 없이 공개된 집계 통계만 읽으며 개인정보는 다루지 않습니다.

### 中文说明 (Chinese)

输入关键词，即可获得 Naver DataLab 搜索词趋势（검색어트렌드）数据，每个关键词的每个周期（日、周、月）一行。每行包含以 0–100 为基准的搜索热度比值（`ratio`）、Naver 返回的原始值（`rawRatio`）、周期，以及查询时使用的设备（PC、移动端）、性别和年龄段条件。Naver 一次最多比较 5 个关键词，本 Actor 以第一个关键词为基准把多次比较串联起来，最多可将 41 个关键词换算到同一基准。可以用逗号把多种写法合并为一行（最多 20 个），数据范围从 2016-01-01 到韩国时间的昨天。费用为每行 $0.00004（1,000 行 $0.04），没有按套餐等级的折扣，每次运行另收 $0.00005 启动费。没有数据的关键词不会产生行，也不收费。不提供：实际搜索量（次数）、购物洞察（쇼핑인사이트）、地区趋势，以及可在不同运行之间直接比较的数值。无需登录，只读取公开的汇总统计，不涉及个人信息。

### 日本語ガイド (Japanese)

キーワードを入力すると、Naver DataLab の検索語トレンド（검색어트렌드）の値が、キーワードと期間（日・週・月）ごとに 1 行で出力されます。各行には、0〜100 を基準とした検索関心度の比率（`ratio`）、Naver が返した元の値（`rawRatio`）、期間、そして取得時に指定したデバイス（PC・モバイル）、性別、年齢層の条件が含まれます。Naver が一度に比較できるのは 5 個までですが、この Actor は 1 番目のキーワードを基準に比較をつなぎ、最大 41 個のキーワードを同じ基準にそろえます。カンマで複数の表記を 1 行にまとめることができ（最大 20 個）、2016-01-01 から韓国時間の前日までのデータを取得できます。料金は 1 行あたり $0.00004（1,000 行で $0.04）で、プラン等級による割引はなく、実行ごとに開始料金 $0.00005 がかかります。データがないキーワードは行が出力されず、課金もされません。提供しないもの：実際の検索数（回数）、ショッピングインサイト、地域別トレンド、異なる実行の間でそのまま比較できる値。ログインなしで公開されている集計統計のみを読み取り、個人情報は扱いません。

### Notes

- **Ratios, not search counts.** 100 is the highest point among the compared keywords in the selected period; the scale changes whenever the keywords, the period or a filter changes.
- **Dates.** `period`, `startDate` and `endDate` are calendar dates in Korea time; `scrapedAt` is UTC. The default period is the 12 months ending yesterday in Korea time.
- **Week and month.** The period is widened to full months (the end is never later than yesterday). `period` is the Monday of the week or the first day of the month.
- **Rounding.** `ratio` is rounded to 5 decimal places; `rawRatio` is Naver's value unchanged.
- **Requests.** One comparison is two requests to Naver, with a pause of 1 to 2 seconds between comparisons. A run with 41 keywords makes 10 comparisons.
- **Personal data.** None. DataLab publishes aggregate statistics only; the gender and age filters select an aggregate, not individual users.
- Not affiliated with Naver.

### Support

Missing a field, another filter, a different output format? Tell us in the **Issues** tab with the run ID. We answer every issue.

# Actor input Schema

## `keywords` (type: `array`):

One trend line per row. Write a keyword as Koreans search it, e.g. 선크림. To add up several spellings into one line, separate them with commas: 선크림, 썬크림 (up to 20). To give the line your own name, put it before a colon: Sunscreen: 선크림, 썬크림. Up to 41 keywords per run; with more than 5, the first keyword is used as the common reference, so put a popular one first.

## `timeUnit` (type: `string`):

One row per day, week or month. For week and month Naver works with whole months, so the period is widened to full months.

## `startDate` (type: `string`):

First day of the period, as YYYY-MM-DD. Naver has data from 2016-01-01. Leave empty for one year before the end date.

## `endDate` (type: `string`):

Last day of the period, as YYYY-MM-DD. Leave empty for yesterday (Korea time), the latest day Naver publishes.

## `device` (type: `string`):

Count searches from all devices, PC only or mobile only.

## `gender` (type: `string`):

Count searches from all users, women only or men only (as registered on the Naver account).

## `ages` (type: `array`):

Count only searches from these age bands. Leave empty for all ages.

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

Proxy settings. The default Apify datacenter proxy works for Naver DataLab. Switch to RESIDENTIAL with country KR only if the log shows repeated request errors.

## Actor input object example

```json
{
  "keywords": [
    "선크림, 썬크림",
    "수분크림"
  ],
  "timeUnit": "week",
  "device": "all",
  "gender": "all",
  "ages": [],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `trendPoints` (type: `string`):

One row per keyword and period, as dataset items.

## `runSummary` (type: `string`):

Resolved period and filters, status of each comparison, keywords without data. Not billed.

# 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 = {
    "keywords": [
        "선크림, 썬크림",
        "수분크림"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("magenta_courser/naver-datalab-trends-scraper").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 = {
    "keywords": [
        "선크림, 썬크림",
        "수분크림",
    ],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("magenta_courser/naver-datalab-trends-scraper").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 '{
  "keywords": [
    "선크림, 썬크림",
    "수분크림"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call magenta_courser/naver-datalab-trends-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,magenta_courser/naver-datalab-trends-scraper"
        }
    }
}
```

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/0Cp2Peu3H2haLHEzv/builds/A4u4Y9EXnzyKwBz4x/openapi.json
