# Naver Search Scraper (`axiomworks/naver-search-scraper`) Actor

Scrape Naver (네이버) web search results for one or many queries in Korean or any language. Get title, URL, display URL, site name, snippet, query, position and page for up to 100 organic results per query. No Naver login or API key needed.

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

## Pricing

from $0.35 / 1,000 results

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

### What does Naver Search Scraper do?

Naver Search Scraper extracts organic web search results from Naver (네이버 검색), South Korea's largest search engine. You give it one or more search queries, in Korean or any other language, and it returns a clean dataset with the title, target URL, display URL, site name, snippet and ranking position of each result. No Naver login and no API key are needed.

It is useful for Korean SEO and rank tracking, market and competitor research in South Korea, source and lead discovery, and building datasets of Korean-language web content. The details that matter, all true to how the Actor works:

- Only organic web results are collected. Ads, Naver-internal cards and Naver-owned pages are skipped.
- Multiple queries per run, and one failing query does not stop the others.
- Up to 100 results per query. Naver itself serves roughly 130 results per query in total.
- Every result carries its 1-based position within the query and the Naver result page it was found on.
- It uses Naver's mobile web search, which is server-rendered, so no browser is needed and runs stay fast and light.

### What data can you get?

Each dataset item is one Naver search result.

| Field | Description | Example |
|---|---|---|
| `id` | Stable SHA-1 hash of the query and result URL | `8fd3f911f0389529f0e92a60409b21390e54dc1b` |
| `sourceUrl` | Naver search results page the result was read from | `https://m.search.naver.com/search.naver?query=...&where=m_web&start=1` |
| `query` | The search query the result belongs to | `서울 맛집` |
| `position` | 1-based rank of the result within its query | `3` |
| `page` | 1-based Naver result page the result was found on (15 results per page) | `1` |
| `title` | Title of the result, truncated to 300 characters | `서울맛집 맛집 인기검색 순위` |
| `url` | Destination URL of the result | `https://www.siksinhot.com/search?keywords=...` |
| `displayUrl` | URL as displayed by Naver under the site name (empty if not shown) | `www.siksinhot.com › search › 서울맛집` |
| `siteName` | Site name as displayed by Naver (empty if not shown) | `식신` |
| `snippet` | Result description, truncated to 600 characters (empty if none) | `2주 전 식신이 추천하는 서울맛집...` |
| `date` | Date shown before the snippet, ISO `YYYY-MM-DD` (null if Naver shows none) | `2026-05-01` |
| `scrapedAt` | ISO 8601 UTC timestamp of the scrape | `2026-09-29T18:51:20.864995+00:00` |

### How to use Naver Search Scraper

1. Open Naver Search Scraper in Apify Console and go to the Input tab.
2. Add one or more search queries under Search queries, for example `서울 맛집` or `python tutorial`.
3. Set Max results per query, from 1 to 100.
4. Leave the proxy setting as it is. Enable Apify Proxy only if Naver blocks your runs.
5. Click Start and wait for the run to finish.
6. Open the Output tab and export the dataset as JSON, CSV, Excel or HTML.

### Input

| Field | Type | Default / prefill | Description |
|---|---|---|---|
| `queries` | array of strings | prefill `["서울 맛집"]` | Search terms to look up on Naver web search. Korean or any language. Each query is scraped separately. |
| `maxResults` | integer 1 to 100 | default and prefill `15` | Maximum results to extract per query. Naver returns 15 results per page. |
| `proxyConfiguration` | object | prefill `{"useApifyProxy": false}` | Optional. Runs work without a proxy in most cases. If Naver blocks your runs, enable Apify Proxy, residential recommended. |

`queries` is required and must contain at least one non-empty term; otherwise the Actor stops immediately with a clear message.

Example input:

```json
{
  "queries": ["서울 맛집", "python tutorial"],
  "maxResults": 30,
  "proxyConfiguration": { "useApifyProxy": false }
}
```

### Output

Below are real items from a run with the query `서울 맛집`.

```json
[
  {
    "title": "서울 맛집 Top100",
    "url": "https://www.diningcode.com/list.dc?query=%EC%84%9C%EC%9A%B8",
    "displayUrl": "www.diningcode.com › 서울",
    "siteName": "다이닝코드",
    "snippet": "서울 맛집 멕시칼리 (멕시코요리, ★4.6), 서령 본점(평양냉면, ★4.6), 오레노라멘 본점(라멘, ★4.5) 등 10,000곳 이상의 전체 순위,식당정보,방문자리뷰,사진 등을 확인하세요.",
    "date": null,
    "id": "62a2d442caf19aed79e20705befdc53ad9063cf8",
    "sourceUrl": "https://m.search.naver.com/search.naver?query=%EC%84%9C%EC%9A%B8+%EB%A7%9B%EC%A7%91&where=m_web&start=1",
    "query": "서울 맛집",
    "position": 1,
    "page": 1,
    "scrapedAt": "2026-09-29T18:51:20.864995+00:00"
  },
  {
    "title": "맛집 - 라이브 서울",
    "url": "https://tv.seoul.go.kr/video/c/2659?curationType=user",
    "displayUrl": "tv.seoul.go.kr › video",
    "siteName": "라이브서울",
    "snippet": "서울에는 특색있는 전통시장이 많으며, 그 중 110년의 역사를 자랑하는 광장시장이 있습니다. 먹거리가 풍부한 광장시장에서 꼭 먹어봐야 할 음식들을 영상으로 만나보세요.",
    "date": null,
    "id": "9e4905738de55c3061e67ad7ab5fd8c6961e3d22",
    "sourceUrl": "https://m.search.naver.com/search.naver?query=%EC%84%9C%EC%9A%B8+%EB%A7%9B%EC%A7%91&where=m_web&start=1",
    "query": "서울 맛집",
    "position": 2,
    "page": 1,
    "scrapedAt": "2026-09-29T18:51:20.864995+00:00"
  },
  {
    "title": "서울맛집 맛집 인기검색 순위",
    "url": "https://www.siksinhot.com/search?keywords=%EC%84%9C%EC%9A%B8%EB%A7%9B%EC%A7%91",
    "displayUrl": "www.siksinhot.com › search › 서울맛집",
    "siteName": "식신",
    "snippet": "2주 전 식신이 추천하는 서울맛집 맛집 인기검색 순위의 맛집 리스트결과는 143506건 입니다. 서울맛집 맛집 인기검색 순위 가볼만한 곳의 메뉴, 위치, 연락처, 예약등의 매장정보를 식신이 소개합니다.",
    "date": null,
    "id": "03f40fcd22aff5d33f098e49f086013ab090a0e5",
    "sourceUrl": "https://m.search.naver.com/search.naver?query=%EC%84%9C%EC%9A%B8+%EB%A7%9B%EC%A7%91&where=m_web&start=1",
    "query": "서울 맛집",
    "position": 3,
    "page": 1,
    "scrapedAt": "2026-09-29T18:51:20.864995+00:00"
  }
]
```

### How much does it cost?

Naver Search Scraper uses pay-per-event pricing, charged per result saved to the dataset. You are never charged for a result you did not get. Apify's free plan credit covers small runs, so you can test a few queries at no cost. See the Pricing tab of this Actor for the exact price per result on each plan.

Cost scales with the number of queries and the results per query, so a run with 3 queries and 30 results each produces at most 90 results. You can also set a maximum cost per run in the run options, and the Actor stops when that limit is reached.

### Use with the API

Python:

```python
import os

from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("axiomworks/naver-search-scraper").call(run_input={
    "queries": ["서울 맛집", "python tutorial"],
    "maxResults": 30,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["query"], item["position"], item["title"], item["url"])
```

JavaScript:

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

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('axiomworks/naver-search-scraper').call({
    queries: ['서울 맛집', 'python tutorial'],
    maxResults: 30,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
process.stdout.write(JSON.stringify(items, null, 2));
```

cURL:

```bash
curl -X POST "https://api.apify.com/v2/acts/axiomworks~naver-search-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries": ["서울 맛집"], "maxResults": 15}'
```

Connect Naver Search Scraper to Zapier, Make, n8n, Google Sheets, Slack and other tools through Apify integrations, or use webhooks to trigger your own workflow when a run finishes. Schedule it in Apify Console, for example daily, to track Naver rankings over time.

### Use with AI agents (MCP)

Naver Search Scraper can be called by AI assistants such as Claude, ChatGPT and Cursor through the Apify MCP server at `https://mcp.apify.com`. The server exposes the tools `search-actors` and `call-actor`, and this Actor's typed input and output schemas let an agent set the queries and read the results without guessing.

To load this Actor directly, add it to your MCP client configuration:

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=axiomworks/naver-search-scraper"
    }
  }
}
```

Example prompts you can type into your agent:

- "Search Naver for 서울 맛집 and list the top 10 sites with their URLs."
- "Use Naver Search Scraper to check which sites rank for 'python tutorial' on Naver and summarize the top 20 results."
- "Get the first 30 Naver web results for three Korean product keywords and give me a table of site name and position."

### FAQ

**How many results can I get per query?**
Up to 100 per query in this Actor. Naver itself serves roughly 130 per query, 15 per page. Queries with few matches return fewer.

**Is this the same as what I see on naver.com?**
It uses Naver's mobile web search, which lists organic web results. Positions can differ slightly from the desktop page and from personalized results. Blog, cafe, news, shopping and place tabs are not included.

**Do I need a proxy to scrape Naver?**
Usually not. Runs work without a proxy in most cases. If you see blocked or empty runs, for example an HTTP 403, HTTP 429 or a CAPTCHA page, enable Apify Proxy in the proxy field, with the residential group if possible.

**A query returned nothing. Why?**
The run logs the reason for each failed query. If every query returns nothing, the run fails so you notice. If only some do, the others are still saved. Check that the query is spelled as you would type it in Naver.

**How fast is it?**
It fetches 15 results per page and retries transient failures up to 3 times, so a query of 100 results takes a handful of page requests. Several queries in one run are processed one after another.

**How often does the data change?**
Every run fetches live results, so rankings reflect the moment of the run. Schedule the Actor daily or weekly to track changes in Naver rankings over time.

**Can I scrape Naver blogs, cafes or shopping?**
No. This Actor covers organic web search results only.

### Is it legal to scrape Naver?

This Actor collects only publicly visible search results. It does not log in and does not access private content. You are responsible for how you use the data. Follow privacy law such as GDPR and CCPA when you store or process any personal data that appears in results, respect Naver's terms of service, keep request volume reasonable, and use the output lawfully. This is general information, not legal advice.

### Feedback

Found a bug or want a new field? Open an issue in the Issues tab of this Actor. Feature requests and examples of queries that behaved unexpectedly are welcome.

# Actor input Schema

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

One or more search terms to look up on Naver web search, in Korean or any language. Each query is scraped separately and results are tagged with their query.

## `maxResults` (type: `integer`):

Maximum number of results to extract for each query (1-100). Naver returns 15 results per page and roughly 130 results in total per query (min 1, max 100).

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

Optional. Runs work without a proxy in most cases. If Naver blocks your runs (HTTP 403, 429 or CAPTCHA), enable Apify Proxy, residential recommended.

## Actor input object example

```json
{
  "queries": [
    "서울 맛집"
  ],
  "maxResults": 15,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `dataset` (type: `string`):

All results in the dataset

# 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": [
        "서울 맛집"
    ],
    "maxResults": 15,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("axiomworks/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": ["서울 맛집"],
    "maxResults": 15,
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("axiomworks/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": [
    "서울 맛집"
  ],
  "maxResults": 15,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call axiomworks/naver-search-scraper --silent --output-dataset

```

## MCP server setup

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