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

Scrape Naver Search (search.naver.com) - South Korea's #1 search engine. Returns organic results (title, URL, domain, snippet, source name) from the web / blog / cafe / news tabs. Korean SERP, no login required.

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

## Pricing

from $3.00 / 1,000 results

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

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Naver Search Scraper

Scrape [Naver Search](https://search.naver.com/search.naver) — South Korea's #1 search engine. Returns organic results with **title, URL, domain, snippet and source name** from the **web / blog / cafe / news** tabs. Korean SERP, no login required. Uses curl\_cffi (chrome131 impersonation) with lazy Apify AUTO proxy escalation.

### What this actor does

- **Four tabs:** `webSearch` (default), `blogSearch`, `cafeSearch`, `newsSearch` — server-rendered organic blocks
- **Pagination** via Naver's `start` parameter, early-stop on empty pages, cross-page URL dedupe
- **Filters:** result keyword (title/snippet/domain/source), domain allow-list (`naver.com`, `blog.naver.com`, …)
- **Block detection:** 403/429/451/503 or content markers missing → lazy-engage Apify AUTO datacenter proxy + backoff
- **Empty fields are omitted**; every record carries `sourceUrl`, `scrapedAt`, `recordType`

### Output per result

- `title`, `url`, `domain`, `sourceName`, `snippet`
- `resultUrl` (= `url`)
- Blog/cafe records additionally carry `date` (post date / relative date)
- News records additionally carry `date`, `naverNewsUrl` (n.news.naver.com mirror), `pressUrl` (media.naver.com press profile)
- `serpUrl` (the SERP page it came from), `recordType: "searchResult" | "error"`, `scrapedAt`

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `mode` | select | `webSearch` | `webSearch` / `blogSearch` / `cafeSearch` / `newsSearch` |
| `searchQuery` | string | `비비바` | Query (Korean or any language) |
| `containsKeyword` | string | – | Title/snippet/domain substring filter |
| `domain` | string | – | Domain allow-list (`namu.wiki`, `blog.naver.com`) |
| `maxItems` | int | `20` | Hard cap (1–500) |

#### Example: web search for a Seoul restaurant

```json
{
  "mode": "webSearch",
  "searchQuery": "서울 맛집",
  "maxItems": 30
}
```

#### Example: blog results only, filtered by domain

```json
{
  "mode": "blogSearch",
  "searchQuery": "비비바",
  "domain": "blog.naver.com",
  "maxItems": 10
}
```

#### Example: latest news articles

```json
{
  "mode": "newsSearch",
  "searchQuery": "서울 맛집",
  "maxItems": 20
}
```

### Anti-bot notes

Plain `curl` gets rate-limited; `curl_cffi` chrome131 + browser UA returns 200 with real organic results (verified locally: 15 results/page for `비비바`, `apple`). The `image` and `kin` tabs are JS-rendered (results not present in the SSR HTML) and are therefore **not exposed** — documented rather than faked.

### Data source

search.naver.com SERP HTML (SSR organic blocks). No login required.

### Limitations

- The `image` and `kin` tabs are JS-only and not supported.
- Naver currently serves the **same merged result set** for the blog and cafe tabs (`where=blog` and `where=cafe` both return blog+cafe posts — Naver unified these tabs in the current UI). `blogSearch` and `cafeSearch` outputs may therefore be identical; both modes are kept as they mirror Naver's tab API.
- Blog/cafe organic blocks carry the post URL on the Keep button (`data-url`); for the small subset of blocks without it (editor-recommended posts) the URL is resolved through Naver's `ader.naver.com` click-tracker (307 redirect).
- Snippets are extracted from the SSR block text with boilerplate tokens removed; occasional nav residue is possible.
- Invalid queries produce typed `recordType: "error"` records (no silent drops).

# Actor input Schema

## `mode` (type: `string`):

Which Naver search tab to scrape.

## `searchQuery` (type: `string`):

Korean or any-language query, e.g. `비비바` or `서울 맛집`.

## `containsKeyword` (type: `string`):

Only keep results whose title, snippet, domain or source name contains this substring (case-insensitive).

## `domain` (type: `string`):

Only keep results from this domain (exact host or suffix, e.g. `naver.com` or `blog.naver.com`).

## `maxItems` (type: `integer`):

Hard cap on emitted records.

## Actor input object example

```json
{
  "mode": "webSearch",
  "searchQuery": "비비바",
  "maxItems": 20
}
```

# Actor output Schema

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

Dataset containing all scraped Naver search results.

# 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 = {
    "mode": "webSearch",
    "searchQuery": "비비바",
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("crawlerbros/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 = {
    "mode": "webSearch",
    "searchQuery": "비비바",
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("crawlerbros/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 '{
  "mode": "webSearch",
  "searchQuery": "비비바",
  "maxItems": 20
}' |
apify call crawlerbros/naver-search-scraper --silent --output-dataset

```

## MCP server setup

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