# Naver Search Scraper (네이버 검색 · SERP, Related Keywords) (`magenta_courser/naver-search-scraper`) Actor

Enter keywords and get the Naver integrated search page (통합검색) as flat rows: every result with its section, rank, ad flag, title, URL and snippet, plus Naver's related searches and autocomplete suggestions. No API key, no browser.

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

## Pricing

from $0.08 / 1,000 result rows

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Search Scraper (네이버 검색) | Naver SERP Ranks, Ads, Sections & Related Keywords (2026)

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

[![$0.10 per 1,000 Naver search result rows, as flat JSON with section, rank and ad flag](https://raw.githubusercontent.com/experimory-crypto/naver-map-scraper-examples/main/assets/hero-naver-search-scraper.png)](https://apify.com/magenta_courser/naver-search-scraper)

Enter **keywords** and get the **Naver integrated search page (통합검색)** as flat JSON rows: every result in page order with its section, overall rank, organic rank, ad flag, title, URL and snippet, the shopping price in KRW, plus Naver's related searches (관련 검색어) and autocomplete suggestions (자동완성). No Naver login, no API key, no browser.

A Naver result page is not a list of ten links. It is a stack of sections that changes per keyword: PowerLink ads, shopping, place, brand content, blog and cafe posts, news, clips, knowledge panels. This Actor reads that page top to bottom and tells you what ranks where, and in which kind of section. Part of a small set of Korean data Actors from one maintainer: [Naver AI Briefing](https://apify.com/magenta_courser/naver-ai-briefing-scraper), [Naver News](https://apify.com/magenta_courser/naver-news-scraper), [Naver DataLab trends](https://apify.com/magenta_courser/naver-datalab-trends-scraper) and [Naver Shopping ranks](https://apify.com/magenta_courser/naver-shopping-rank-tracker).

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

### Why choose this Actor?

**$0.10 per 1,000 rows, one price for everything.**<br>
You pay $0.0001 per row saved to the dataset, whatever the row is: a search result, a detected section, a related search or an autocomplete suggestion. The default run for one keyword saved 83 rows (run `H2ul6njOTjHQti8WS`), which is $0.0083.

**The whole page, not one tab.**<br>
Each row says which section it sits in (`sectionType`, `sectionTitle`, `sectionPosition`) and where (`rank` over the whole page, `rankInSection` inside the section). You can see that a keyword is answered by shopping first and blogs fifth before you decide what to publish.

**Ads are flagged and never clicked.**<br>
Paid results carry `isAd: true` and have no `organicRank`. Naver's ad click-tracking links are not returned, because opening one would bill the advertiser; for PowerLink ads `url` is built from the advertiser's display URL instead.

**Flat rows for code and AI agents.**<br>
One required input (`queries`). Every row has the same 25 keys; a value Naver did not show is `null`; numbers are numbers.

**Measured, not estimated.** One keyword, one page, with related searches: 83 rows in 9.2 seconds at 256 MB (run `H2ul6njOTjHQti8WS`, build 0.1.4, 2026-11-11, default datacenter proxy, 2 requests, no retries). Nine keywords, two pages each, with related searches and autocomplete: 852 rows in 68.0 seconds, 35 requests, no retries (run `cTkfcYbDKZqNmngS9`, same build).

### Quick start

The integrated search page for one keyword, with related searches. This is the default input; at the Free-plan price the run above cost about $0.008.

```json
{
  "queries": ["선크림"]
}
```

[Open the Actor input](https://console.apify.com/actors/doXjcJm6Hmigrad2R/input), type keywords one per line (`선크림` means sunscreen), and click **Start**. 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-search-scraper to read the Naver (South Korea) integrated search result page for keywords.

Input (JSON): "queries" is a list of keywords exactly as typed into Naver, Korean works best, e.g. ["선크림", "강남 맛집"] (required). Optional: "maxPages" (1-10, default 1; page 1 is the integrated page, each extra page adds the next 20 web/blog/cafe results), "includeRelatedSearches" (default true), "includeAutocomplete" (default false), "includeAds" (default true), "sort" ("relevance" or "date"), "period" ("all", "1h", "1d", "1w", "1m", "3m", "6m", "1y").

Output: flat dataset rows with a "rowType" field. "result" rows have query, page, rank (ads included), organicRank (null for ads), sectionType (powerlink, brandContent, shopping, place, web, news, influencer, clip, image, shortents, knowledge, other), sectionTitle, sectionPosition, rankInSection, resultType (ad, product, place, web, blog, cafe, kin, influencer, post, news, clip), isAd, title, url, displayUrl, description, sourceName, dateText, publishedAt (ISO, Korea time), price (KRW, shopping only), imageUrl. "section" rows mark a section that is not broken into items. "relatedSearch" and "autocomplete" rows have the keyword in "title" and its order in "rankInSection". Missing values are null. Rows of different keywords can be interleaved: sort by query, then rank.

Run it through the Apify API: POST https://api.apify.com/v2/acts/magenta_courser~naver-search-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-search-scraper.

Price: $0.0001 per dataset row (Free plan). One keyword with maxPages 1 is roughly 40 to 100 rows.
```

#### 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-search-scraper
```

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

### Key features

- **Every section in page order.** PowerLink ads, brand content ads, shopping, place, web / blog / cafe results, news, influencer, clips. `sectionPosition` is the order of the section on its page.
- **Two ranks.** `rank` counts every result of the keyword, ads included, and continues across pages; `organicRank` counts non-ad results only.
- **Result type per row.** `resultType` is one of `ad`, `product`, `place`, `web`, `blog`, `cafe`, `kin` (지식iN question), `influencer`, `post`, `news`, `clip`.
- **Shopping prices as numbers.** `price` is the lowest price shown on the product card, in KRW.
- **Place results with a Naver Map link.** `url` is `https://map.naver.com/p/entry/place/<id>` and `description` is the business category.
- **Dates in two forms.** `dateText` exactly as Naver shows it (`3시간 전`, `2026.05.06.`) and `publishedAt` as ISO 8601 in Korea time.
- **Sections that are not itemized are still reported.** The image grid, AI topic cards (숏텐츠), knowledge panels and anything unknown become one `section` row, so you see that they exist and where they sit.
- **Related searches with Naver's badge.** `relatedSearch` rows keep Naver's order and its badge, for example `많이 찾는` (popular) or `최근 관심` (trending).
- **Autocomplete suggestions** as `autocomplete` rows, in Naver's order (optional).
- **Deeper pages.** `maxPages` up to 10; each extra page adds the next 20 web, blog and cafe results, and a result already returned on an earlier page is not repeated.
- **Sort and period filters** for the web, blog and cafe results: newest first, and last hour to last year.
- **A free run summary.** The key-value store record `RUN_SUMMARY` has the status of each keyword, row counts by type, and the section order of page 1.
- **Clean stop at your cost limit.** Rows stored equal rows charged; keywords that were cut off or not started are marked `budgetLimited`.

### How to scrape Naver search results

#### The integrated search page for several keywords

Keywords are processed four at a time. Each row carries its keyword in `query`.

```json
{
  "queries": ["선크림", "강남 맛집", "삼성전자"],
  "maxPages": 1
}
```

(`강남 맛집` = Gangnam restaurants, `삼성전자` = Samsung Electronics.)

#### Organic results only, without ads

Ad rows are dropped, and a section that contains only ads disappears. `rank` then equals `organicRank`.

```json
{
  "queries": ["캠핑의자"],
  "includeAds": false
}
```

#### Track where a blog post, cafe post or site ranks

Read more of the web / blog / cafe feed with `maxPages`, then filter rows by `url` in your own code. Three pages cover the integrated page plus the next 40 feed results.

```json
{
  "queries": ["선크림 추천"],
  "maxPages": 3,
  "includeRelatedSearches": false
}
```

#### See who advertises on your keywords

Keep ads on and filter `isAd: true`. PowerLink rows have the ad title, ad text (`description`), the advertiser name (`sourceName`) and the display URL.

```json
{
  "queries": ["선크림", "수분크림"],
  "includeAds": true,
  "includeRelatedSearches": false
}
```

#### Keyword expansion: related searches and autocomplete

Both lists come back as rows with the keyword in `title`. Feed them back in as new `queries`.

```json
{
  "queries": ["선크림"],
  "includeRelatedSearches": true,
  "includeAutocomplete": true
}
```

#### Only recent posts, newest first

`sort` and `period` apply to the web, blog and cafe results.

```json
{
  "queries": ["아이폰 17"],
  "maxPages": 2,
  "sort": "date",
  "period": "1w"
}
```

### Input parameters

| Field | Type | Default | Description |
|---|---|---|---|
| `queries` | array of strings | — (required) | Keywords, one per line, as you would type them into Naver. Each is searched separately; duplicates are removed. |
| `maxPages` | integer | `1` | 1 to 10. Page 1 is the integrated search page: ads, shopping, place, news and the first 20 web / blog / cafe results. Each extra page adds the next 20 web / blog / cafe results. |
| `includeRelatedSearches` | boolean | `true` | Add `relatedSearch` rows. One extra small request per keyword. |
| `includeAutocomplete` | boolean | `false` | Add `autocomplete` rows. One extra small request per keyword. |
| `includeAds` | boolean | `true` | Keep paid results (`isAd: true`). `false` returns non-ad results only. |
| `sort` | string | `relevance` | `relevance` (Naver's default) or `date` (newest first), for the web / blog / cafe results. |
| `period` | string | `all` | `all`, `1h`, `1d`, `1w`, `1m`, `3m`, `6m` or `1y`. Only web / blog / cafe results published within the period. |
| `proxyConfiguration` | object | Apify Proxy | Keep the default (datacenter). Switch to RESIDENTIAL with country KR only if the log shows repeated request errors. |

#### How pages and ranks work

Page 1 is the integrated page, which already contains the first 20 results of Naver's blended web / blog / cafe feed. Page 2 continues that feed from result 21, page 3 from result 41, and so on. `rank` and `organicRank` keep counting across pages. Results whose URL was already returned for the keyword are skipped, so an extra page can add slightly fewer than 20 rows: in run `cTkfcYbDKZqNmngS9` page 2 added 17 to 20 rows per keyword.

How many rows page 1 gives depends on the keyword, because Naver decides which sections to show. In the same run, page 1 gave 41 to 82 result and section rows across eight keywords, plus 18 related searches each and 2 to 10 autocomplete suggestions.

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

Rows have a `rowType` field. Every row has every field; missing values are `null`.

| `rowType` | What it is |
|---|---|
| `result` | One search result: an ad, a product, a place, a web page, a blog or cafe post, a 지식iN question, a news article or a clip. |
| `section` | A section Naver showed that this Actor does not break into items: the image grid, AI topic cards (숏텐츠), knowledge panels such as stock quotes, and sections it does not know. |
| `relatedSearch` | One of Naver's related searches (관련 검색어) for the keyword. |
| `autocomplete` | One autocomplete suggestion (자동완성) for the keyword. |

**All fields:**

| Field | Type | Description |
|---|---|---|
| `query` | string | The input keyword this row belongs to. |
| `rowType` | string | `result`, `section`, `relatedSearch` or `autocomplete`. |
| `page` | integer | Page number within the keyword; 1 = the integrated page. `null` for related searches and autocomplete. |
| `rank` | integer | Position among all results of the keyword, ads included, continuing across pages. `null` for non-result rows. |
| `organicRank` | integer | Position among non-ad results only. `null` for ads and non-result rows. |
| `sectionType` | string | `powerlink`, `brandContent`, `shopping`, `place`, `web`, `news`, `influencer`, `clip`, `image`, `shortents`, `knowledge` or `other`. |
| `sectionCode` | string | Naver's own area code of the section, e.g. `pwl_nop`, `shp_gui`, `shs_lis`, `urB_coR`, `nws_all`. |
| `sectionTitle` | string | The section heading as shown on the page (Korean), or an English label when Naver shows no heading. |
| `sectionPosition` | integer | Order of the section on its page, starting at 1. |
| `rankInSection` | integer | Position inside the section. For `relatedSearch` and `autocomplete` rows: position in that list. |
| `resultType` | string | `ad`, `product`, `place`, `web`, `blog`, `cafe`, `kin`, `influencer`, `post`, `news` or `clip`. |
| `isAd` | boolean | `true` for paid results; `null` for non-result rows. |
| `title` | string | Result title. For `section` rows: the section title. For `relatedSearch` and `autocomplete` rows: the keyword. |
| `url` | string | Link of the result (see "Notes" for ads and price-comparison products). For `relatedSearch` and `autocomplete` rows: the Naver search URL of that keyword. |
| `displayUrl` | string | URL or breadcrumb text Naver displays under a web result or an ad, e.g. `www.oliveyoung.co.kr › 선크림`. |
| `description` | string | Snippet. For place results: the business category. For PowerLink ads: the ad text. |
| `sourceName` | string | Site name, news publisher, cafe (community) name or advertiser name. `null` for blog, influencer and clip results. |
| `dateText` | string | Date exactly as Naver shows it, e.g. `3시간 전`, `2026.05.06.`. |
| `publishedAt` | string | `dateText` as ISO 8601 in Korea time (+09:00). Approximate for relative dates. |
| `price` | number | Product price in KRW for shopping results. |
| `imageUrl` | string | Thumbnail URL when Naver shows one. |
| `badge` | string | Badge on a related search, e.g. `많이 찾는` (popular), `최근 관심` (trending). |
| `searchUrl` | string | The Naver URL that was scraped. |
| `scrapedAt` | string | Scrape time (UTC, ISO 8601). |
| `schemaVersion` | integer | Output schema version, currently `1`. |

**Run summary** (key-value store record `RUN_SUMMARY`, not charged): run `status` (`completed`, `partial`, `budgetLimited`, `failed`), row counts by type, `requests`, `retries`, and one entry per keyword with `status`, `stopReason` (`done`, `noResults`, `endOfResults`, `chargeLimitReached`, `notStartedChargeLimit`, `requestFailed`), `pagesScraped`, row counts, `sections` (the section types of page 1 in page order) and `errorMessage`.

#### Output example: PowerLink ad

From run `H2ul6njOTjHQti8WS` (2026-11-11, build 0.1.4), keyword `선크림`. All rows below are unedited.

```json
{
  "query": "선크림",
  "rowType": "result",
  "page": 1,
  "rank": 1,
  "organicRank": null,
  "sectionType": "powerlink",
  "sectionCode": "pwl_nop",
  "sectionTitle": "선크림 관련 광고",
  "sectionPosition": 1,
  "rankInSection": 1,
  "resultType": "ad",
  "isAd": true,
  "title": "달바 비건선크림 1+1 핫딜 2배로 쟁여두기!",
  "url": "https://brand.naver.com/dalba",
  "displayUrl": "brand.naver.com/dalba",
  "description": "비건 선크림11종, 핑크 톤업선크림, 수분광 에센스선크림, 비타민 선크림.",
  "sourceName": "달바",
  "dateText": null,
  "publishedAt": null,
  "price": null,
  "imageUrl": null,
  "badge": null,
  "searchUrl": "https://search.naver.com/search.naver?where=nexearch&ssc=tab.nx.all&query=%EC%84%A0%ED%81%AC%EB%A6%BC",
  "scrapedAt": "2026-11-11T08:16:14.465Z",
  "schemaVersion": 1
}
```

#### Output example: shopping product

Same run. Overall rank 18, fifth non-ad result, second item of the third section.

```json
{
  "query": "선크림",
  "rowType": "result",
  "page": 1,
  "rank": 18,
  "organicRank": 5,
  "sectionType": "shopping",
  "sectionCode": "shs_lis",
  "sectionTitle": "네이버플러스 스토어",
  "sectionPosition": 3,
  "rankInSection": 2,
  "resultType": "product",
  "isAd": false,
  "title": "일리윤 세라마이드 아토 선로션 180ml",
  "url": "https://smartstore.naver.com/main/products/13527136926",
  "displayUrl": null,
  "description": null,
  "sourceName": null,
  "dateText": null,
  "publishedAt": null,
  "price": 13300,
  "imageUrl": "https://shopping-phinf.pstatic.net/main_9107164/91071647279.jpg?type=f300",
  "badge": null,
  "searchUrl": "https://search.naver.com/search.naver?where=nexearch&ssc=tab.nx.all&query=%EC%84%A0%ED%81%AC%EB%A6%BC",
  "scrapedAt": "2026-11-11T08:16:14.465Z",
  "schemaVersion": 1
}
```

#### Output example: web result

Same run. A site result has `sourceName` and `displayUrl`; Naver showed no snippet and no date for this one.

```json
{
  "query": "선크림",
  "rowType": "result",
  "page": 1,
  "rank": 61,
  "organicRank": 45,
  "sectionType": "web",
  "sectionCode": "urB_b3R",
  "sectionTitle": "Web, blog and cafe results",
  "sectionPosition": 11,
  "rankInSection": 1,
  "resultType": "web",
  "isAd": false,
  "title": "선크림 검색 - 올리브영 온라인몰",
  "url": "https://www.oliveyoung.co.kr/store/search/getSearchMain.do?query=%EC%84%A0%ED%81%AC%EB%A6%BC",
  "displayUrl": "www.oliveyoung.co.kr › 선크림",
  "description": null,
  "sourceName": "올리브영 온라인몰",
  "dateText": null,
  "publishedAt": null,
  "price": null,
  "imageUrl": "https://search.pstatic.net/sunny?src=https%3A%2F%2Fimage.oliveyoung.co.kr%2Fcfimages%2Fcontents%2Fplanshop%2Fimage%2F202610200809510908.jpg&type=fff208_208_ar",
  "badge": null,
  "searchUrl": "https://search.naver.com/search.naver?where=nexearch&ssc=tab.nx.all&query=%EC%84%A0%ED%81%AC%EB%A6%BC",
  "scrapedAt": "2026-11-11T08:16:14.465Z",
  "schemaVersion": 1
}
```

#### Output example: news result

From run `cTkfcYbDKZqNmngS9` (2026-11-11, build 0.1.4), keyword `삼성전자`. `dateText` was "5 hours ago", so `publishedAt` is exact to the hour only.

```json
{
  "query": "삼성전자",
  "rowType": "result",
  "page": 1,
  "rank": 22,
  "organicRank": 22,
  "sectionType": "news",
  "sectionCode": "nws_all",
  "sectionTitle": "뉴스",
  "sectionPosition": 5,
  "rankInSection": 1,
  "resultType": "news",
  "isAd": false,
  "title": "\"삼성 거래처도 아닌데 이렇게까지\"…중소기업에 벌어진 일",
  "url": "https://www.hankyung.com/article/202611119762g",
  "displayUrl": null,
  "description": "삼성전자가 국내 기업 가운데 처음으로 동반성장지수 평가에서 15년 연속 최우수 등급을 받았다. 협력회사에 대한 기술·금융 지원과 인력 양성뿐 아니라 거래 관계가 없는 중소기업까지 지원 대상을 확대한 점을 인정받았다. 삼성전자는 11일 동반성장위원회가 발표한 '2026년도 동반성장지수 평가(2025년...",
  "sourceName": "한국경제",
  "dateText": "5시간 전",
  "publishedAt": "2026-11-11T12:00:00+09:00",
  "price": null,
  "imageUrl": "https://search.pstatic.net/common/?src=https%3A%2F%2Fimgnews.pstatic.net%2Fimage%2Forigin%2F015%2F2026%2F11%2F11%2F5352683.jpg&type=fface200_200&expire=2&refresh=true",
  "badge": null,
  "searchUrl": "https://search.naver.com/search.naver?where=nexearch&ssc=tab.nx.all&query=%EC%82%BC%EC%84%B1%EC%A0%84%EC%9E%90",
  "scrapedAt": "2026-11-11T08:04:57.807Z",
  "schemaVersion": 1
}
```

#### Output example: section row and related search

Run `H2ul6njOTjHQti8WS`. The image grid was the eighth section of the page; it is reported, but its images are not listed.

```json
{
  "query": "선크림",
  "rowType": "section",
  "page": 1,
  "rank": null,
  "organicRank": null,
  "sectionType": "image",
  "sectionCode": "urB_imM",
  "sectionTitle": "이미지",
  "sectionPosition": 8,
  "rankInSection": null,
  "resultType": null,
  "isAd": null,
  "title": "이미지",
  "url": null,
  "displayUrl": null,
  "description": null,
  "sourceName": null,
  "dateText": null,
  "publishedAt": null,
  "price": null,
  "imageUrl": null,
  "badge": null,
  "searchUrl": "https://search.naver.com/search.naver?where=nexearch&ssc=tab.nx.all&query=%EC%84%A0%ED%81%AC%EB%A6%BC",
  "scrapedAt": "2026-11-11T08:16:14.465Z",
  "schemaVersion": 1
}
```

```json
{
  "query": "선크림",
  "rowType": "relatedSearch",
  "page": null,
  "rank": null,
  "organicRank": null,
  "sectionType": null,
  "sectionCode": null,
  "sectionTitle": null,
  "sectionPosition": null,
  "rankInSection": 2,
  "resultType": null,
  "isAd": null,
  "title": "선크림 추천",
  "url": "https://search.naver.com/search.naver?where=nexearch&query=%EC%84%A0%ED%81%AC%EB%A6%BC%20%EC%B6%94%EC%B2%9C",
  "displayUrl": null,
  "description": null,
  "sourceName": null,
  "dateText": null,
  "publishedAt": null,
  "price": null,
  "imageUrl": null,
  "badge": "많이 찾는",
  "searchUrl": "https://search.naver.com/search.naver?where=nexearch&ssc=tab.nx.all&query=%EC%84%A0%ED%81%AC%EB%A6%BC",
  "scrapedAt": "2026-11-11T08:16:14.565Z",
  "schemaVersion": 1
}
```

### Advanced usage

#### Find your rank for a list of keywords

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("magenta_courser/naver-search-scraper").call(run_input={
    "queries": ["선크림 추천", "톤업 선크림"],
    "maxPages": 3,
    "includeRelatedSearches": False,
})
mine = "smartstore.naver.com/yourstore"
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
    if row["rowType"] == "result" and row["url"] and mine in row["url"]:
        print(row["query"], row["rank"], row["organicRank"], row["sectionType"], row["isAd"])
```

Schedule the same input daily and store the output to follow rank changes over time. This Actor does not keep a history between runs; each run is a fresh snapshot.

#### Which sections does Naver show for a keyword?

Read `sections` per keyword from the `RUN_SUMMARY` record, or group the rows by `sectionPosition`. For `선크림` in run `H2ul6njOTjHQti8WS` the order was: PowerLink, two shopping sections, brand content, web, clip, web, image, three more web blocks, AI topic cards.

#### Put rows back in page order

Rows of one keyword are stored in page order, but several keywords run in parallel, so rows of different keywords can be interleaved. Sort by `query`, then `page`, `sectionPosition` and `rankInSection`.

#### One call from the command line

```bash
curl -X POST "https://api.apify.com/v2/acts/magenta_courser~naver-search-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries": ["선크림"], "includeRelatedSearches": false}'
```

### How much does it cost to scrape Naver search results?

Pay per event, no subscription. Prices below are the Free-plan prices in effect since 2026-11-11; paid Apify plans get the discount shown.

| Event | Price | Bronze / Silver / Gold and above | When |
|---|---|---|---|
| Result row | **$0.0001** per row | $0.000095 / $0.00009 / $0.00008 | Every row saved to the dataset: `result`, `section`, `relatedSearch` and `autocomplete` rows alike. |
| Actor start | $0.00005 | — | Once per run. |

Not charged: the `RUN_SUMMARY` record, keywords that fail, keywords not started because of your cost limit, and retries.

Worked examples at the Free-plan price. Row counts depend on the keyword; these use the counts measured in the runs named above.

| Job | Rows | Cost |
|---|---|---|
| Default run: 1 keyword, page 1, related searches (83 rows in run `H2ul6njOTjHQti8WS`) | 83 | **$0.0083** |
| 9 keywords, 2 pages, related searches and autocomplete (run `cTkfcYbDKZqNmngS9`) | 852 | **$0.085** |
| 100 keywords daily at about 83 rows each | about 8,300 per day | about **$0.83 per day** |
| Any job | 1,000 | **$0.10** |

To pay less per keyword, turn off what you do not need: `includeRelatedSearches: false` removed 18 rows per keyword in our runs, and `includeAds: false` removes the ad rows.

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, the keyword being read gets `status: "budgetLimited"`, and keywords not started get `stopReason: "notStartedChargeLimit"`.

### Scheduling and integrations

- **Schedules.** In Apify Console, create a daily or weekly schedule with your keyword list to build a rank history in your own storage.
- **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-search-scraper').call({
    queries: ['선크림'],
    maxPages: 1,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
const ads = items.filter((r) => r.rowType === 'result' && r.isAd);
console.log(ads.length, 'ads;', ads.map((r) => r.sourceName).filter(Boolean).join(', '));
```

### FAQ

**Do I need a Naver account or the Naver Search API key?**
No. The Actor reads the public result page of `search.naver.com` without logging in.

**Does it return monthly search volume?**
No. Search volume is not on the result page. For relative search interest over time, use [Naver DataLab Search Trends Scraper](https://apify.com/magenta_courser/naver-datalab-trends-scraper).

**Does it return Naver's AI Briefing?**
Not its content. When Naver shows an AI Briefing, this Actor reports it as a `section` row with `sectionType: "other"` (section code `abL_rtX` in run `cTkfcYbDKZqNmngS9`). For the answer text and its cited sources use [Naver AI Briefing Scraper](https://apify.com/magenta_courser/naver-ai-briefing-scraper).

**How many results per keyword?**
Page 1 is whatever Naver shows on the integrated page: 41 to 82 result and section rows across eight keywords in run `cTkfcYbDKZqNmngS9`. Each extra page adds up to 20 web, blog and cafe results, and `maxPages` goes up to 10.

**Why do some ads or products have `url: null` or a Naver link?**
Ad click-tracking links are never returned. A PowerLink ad gets the advertiser's display URL instead; a shopping ad whose only link is a tracking link gets `url: null` (18 of 107 ad rows in run `cTkfcYbDKZqNmngS9`). Non-ad products in the price-comparison section (`네이버 가격비교`) carry Naver Shopping's own gateway link (`cr3.shopping.naver.com/...`), which is the link Naver puts on the card.

**What happens when Naver blocks or rate-limits a request?**
A failed request is tried up to 5 times in total, each time on a new proxy session, with a growing pause. If page 1 of a keyword cannot be read, that keyword is marked `failed` and nothing is charged for it; if a later page fails you keep the earlier pages (`status: "partial"`). One failed keyword does not stop the run; the run fails only when every keyword failed. The default datacenter proxy needed no retries in the runs named above.

**What does a keyword with no results return?**
Whatever sections Naver still shows. In run `cTkfcYbDKZqNmngS9` a nonsense keyword returned a single `section` row. If Naver shows nothing at all, the keyword gets `stopReason: "noResults"` and no rows.

**Is it legal to scrape Naver search results?**
The Actor collects only publicly visible search results 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로 내려받을 수 있습니다. 검색 결과 행만 필요하면 `rowType`이 `result`인 행을 거르고, 연관 검색어가 필요 없으면 `includeRelatedSearches`를 `false`로 두면 됩니다.

### 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 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 DataLab Search Trends Scraper](https://apify.com/magenta_courser/naver-datalab-trends-scraper) | Korean keywords → search interest (0 to 100) per day, week or month. |
| [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)

검색어를 넣으면 네이버 통합검색 결과 페이지가 결과 한 건당 한 행으로 나옵니다. 각 행에는 섹션 종류(파워링크, 브랜드 콘텐츠, 쇼핑, 플레이스, 웹·블로그·카페, 뉴스, 인플루언서, 클립)와 섹션 순서, 전체 순위(`rank`, 광고 포함), 광고 제외 순위(`organicRank`), 광고 여부(`isAd`), 제목, URL, 요약, 날짜, 쇼핑 가격(원)이 들어 있고, 연관 검색어와 자동완성도 행으로 받을 수 있습니다. 요금은 데이터셋에 저장된 행 1건당 $0.0001(1,000행 $0.10)이며 결과·섹션·연관 검색어·자동완성 행이 모두 같은 값이고, 실행마다 시작 요금 $0.00005가 붙습니다. `maxPages`를 늘리면 페이지마다 웹·블로그·카페 결과가 최대 20건씩 더해집니다(최대 10페이지). 제공하지 않는 것: 월간 검색량, AI 브리핑 본문, 이미지 묶음의 개별 이미지, 게시글 전문, 모바일 검색 화면. 광고 클릭 추적 링크는 반환하지 않으며, 블로그·인플루언서·클립 작성자 이름은 수집하지 않습니다. 로그인 없이 공개된 검색 결과만 읽습니다.

### 中文说明 (Chinese)

输入关键词，即可获得 Naver 综合搜索（통합검색）结果页，每条结果一行。每行包含所属板块类型（PowerLink 广告、品牌内容、购物、地点、网页·博客·Cafe、新闻、达人、短视频）和板块顺序、整体排名（`rank`，含广告）、不含广告的排名（`organicRank`）、是否为广告（`isAd`）、标题、URL、摘要、日期以及购物价格（韩元），还可以把相关搜索词和自动补全建议作为行返回。费用为数据集中每保存一行 $0.0001（1,000 行 $0.10），结果行、板块行、相关搜索词行和自动补全行价格相同，每次运行另收 $0.00005 启动费。增大 `maxPages` 时，每多一页最多增加 20 条网页·博客·Cafe 结果（最多 10 页）。不提供：月搜索量、AI Briefing 正文、图片板块中的单张图片、帖子全文、移动端搜索页面。不返回广告点击跟踪链接，也不采集博客、达人和短视频作者的名称。无需登录，只读取公开的搜索结果。

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

キーワードを入力すると、Naver 統合検索（통합검색）の結果ページが 1 件 1 行で出力されます。各行には、セクションの種類（パワーリンク広告、ブランドコンテンツ、ショッピング、プレイス、ウェブ・ブログ・カフェ、ニュース、インフルエンサー、クリップ）とセクションの順番、全体順位（`rank`、広告を含む）、広告を除いた順位（`organicRank`）、広告かどうか（`isAd`）、タイトル、URL、スニペット、日付、ショッピングの価格（ウォン）が含まれ、関連検索ワードとオートコンプリート候補も行として取得できます。料金はデータセットに保存された 1 行あたり $0.0001（1,000 行で $0.10）で、結果・セクション・関連検索ワード・オートコンプリートの行はすべて同じ価格です。実行ごとに開始料金 $0.00005 がかかります。`maxPages` を増やすと、1 ページごとにウェブ・ブログ・カフェの結果が最大 20 件追加されます（最大 10 ページ）。提供しないもの：月間検索ボリューム、AI ブリーフィングの本文、画像セクション内の個々の画像、投稿の全文、モバイル版の検索画面。広告のクリック計測リンクは返さず、ブログ・インフルエンサー・クリップの投稿者名は収集しません。ログインなしで公開されている検索結果のみを読み取ります。

### Notes

- **Ads.** Rows in the PowerLink and brand content sections are always `isAd: true`. Shopping and place ads are flagged where Naver marks them. Ad click-tracking links (`ader.naver.com`, `adcr.naver.com`, `cr*.naver.com`) are never returned.
- **Shopping links.** Products in the Naver Plus Store section have a product page URL. Non-ad products in the price-comparison section have Naver Shopping's gateway link; shopping ads there have `url: null`.
- **Dates.** `publishedAt` is derived from `dateText`. An absolute date becomes midnight of that day in Korea time; `3시간 전` is rounded to the hour; `2일 전`, `1주 전` and `1개월 전` become midnight of the computed day (a month is counted as 30 days).
- **Cafe links.** Naver Cafe URLs are returned without their one-time query token, so the same post always has the same URL.
- **Personal data.** Names of blog, influencer and clip authors are not collected: `sourceName` is filled only for sites, news publishers, cafes (community names), Naver 지식iN (the service name) and advertisers. Result URLs are returned as Naver links them, so a blog post URL contains the blog's ID. Titles and snippets are user-written text and may contain details their authors chose to publish.
- **What you see is a logged-out result.** The Actor requests `search.naver.com` (not `m.search.naver.com`) through a proxy without cookies or login, so personalised results are not reflected.
- **Sections change.** Naver decides per keyword which sections to show and changes its layout from time to time. A section this Actor does not know appears as `sectionType: "other"` with its `sectionCode`; if a page cannot be parsed at all, the keyword fails with an error message instead of returning partial guesses.
- Not affiliated with Naver.

### Support

Missing a section type, a field, or an output format? Tell us in the **Issues** tab with the run ID. We answer every issue.

# Actor input Schema

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

Keywords to search on Naver, one per line, exactly as you would type them into the Naver search bar. Korean works best, e.g. 선크림 (sunscreen), 강남 맛집 (Gangnam restaurants), 삼성전자 (Samsung Electronics). Each keyword is searched separately; duplicates are removed.

## `maxPages` (type: `integer`):

1 = the integrated search page (통합검색): ads, shopping, place, news and the first 20 web/blog/cafe results. Each extra page adds the next 20 web/blog/cafe results. Results already returned on an earlier page are not repeated.

## `includeRelatedSearches` (type: `boolean`):

Also return Naver's related searches (관련 검색어) for each keyword as rows with rowType "relatedSearch". Costs one extra small request per keyword.

## `includeAutocomplete` (type: `boolean`):

Also return Naver's autocomplete suggestions (자동완성) for each keyword as rows with rowType "autocomplete". Costs one extra small request per keyword.

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

Keep paid results (PowerLink ads, brand content, shopping and place ads). They are returned with isAd = true. Turn off to get only non-ad results.

## `sort` (type: `string`):

Order of the web/blog/cafe results. "relevance" is what Naver shows by default; "date" puts the newest posts first.

## `period` (type: `string`):

Only return web/blog/cafe results published within this period. "all" applies no filter.

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

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

## Actor input object example

```json
{
  "queries": [
    "선크림"
  ],
  "maxPages": 1,
  "includeRelatedSearches": true,
  "includeAutocomplete": false,
  "includeAds": true,
  "sort": "relevance",
  "period": "all",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

All rows (results, sections, related searches, autocomplete suggestions) as dataset items.

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

Per-keyword status (completed, partial, failed, budgetLimited), pages scraped, row counts and the section order of page 1. 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 = {
    "queries": [
        "선크림"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

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

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,magenta_courser/naver-search-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/doXjcJm6Hmigrad2R/builds/nllJXVZsrQtifAcAT/openapi.json
