# Naver Scraper - Places, Blogs, News & Cafe Leads (`scrapesage/naver-scraper`) Actor

Scrape Naver into clean structured data. Get Korean local business leads with phone, address, rating and coordinates, plus blog, news and cafe search results with the full article text. No browser, no login, runs in seconds.

- **URL**: https://apify.com/scrapesage/naver-scraper.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Lead generation, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 business leads

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/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 Scraper - Places, Blogs, News & Cafe Leads

Turn **Naver**, South Korea's dominant search portal, into clean structured data: **Korean local
business leads with phone numbers and addresses**, plus **blog, news and cafe** search results with
the **full article body**, not just a snippet.

No browser, no login, no cookies. This actor runs on plain HTTP against Naver's own
server-rendered pages, so runs finish in **seconds** and cost a fraction of a browser-based scraper.

### What you get

#### `places` - Korean local business leads

The lead-generation mode. Every business comes back with contact and location data ready for
outreach or market mapping.

| Field | Notes |
|---|---|
| `name`, `category`, `businessCategory`, `categories` | Business name + Naver's own category codes |
| **`phone`** | **The contact number - populated for the large majority of listings** |
| `roadAddress`, `address`, `fullAddress`, `commonAddress` | Full Korean address, all four Naver formats |
| `latitude`, `longitude` | Map coordinates, ready for geo analysis |
| `visitorReviewScore`, `visitorReviewCount`, `blogCafeReviewCount`, `bookingReviewCount`, `totalReviewCount` | Full review picture |
| `conveniences`, `options`, `paymentMethods` | Amenities, service options, accepted payments |
| `menuCount`, `topMenus` | Menu items with prices *(businesses that publish a menu)* |
| `topReviews`, `microReview` | Actual visitor review text *(listings with recent reviews)* |
| `imageUrl`, `imageUrls`, `imageCount` | Photos |
| `bookingUrl`, `talkTalkUrl`, `hasBooking`, `hasNaverPay` | Booking / chat channels *(opt-in per merchant)* |
| `representativePrice`, `bookingReviewScore` | *Beauty lane only - hair & beauty listings* |
| **`leadScore`** | 0-100 contactability score, so you can sort the best leads to the top |
| `placeUrl`, `mapUrl` | Direct Naver Place and Naver Map links |

#### `blogs` / `news` / `cafes` - Naver search results

| Field | Notes |
|---|---|
| `title`, `snippet`, `publishedDate` / `publishedRelative` | Result basics |
| **`fullText`, `textLength`** | **The complete post or article body** when `includeDetails` is on |
| `bloggerName`, `blogId`, `blogUrl`, `likeCount`, `commentCount`, `categoryName` | Blogs |
| `publisher`, `publishedAt`, `reporter`, `section`, `naverNewsUrl`, `originalUrl` | News |
| `cafeName`, `cafeUrl`, `isAd` | Cafes - paid placements are flagged, not silently mixed in |

### Honest scope - what this actor does NOT do

We would rather tell you up front than have you discover it on your first run.

- **Naver Shopping is not included.** `search.shopping.naver.com` answers automated requests with
  HTTP 418 on every lane we tested, so shopping is **not offered** rather than shipped broken.
- **Only two Naver Place lanes are offered** (`general` and `beauty`). Naver's other Place verticals
  (`/cafe/list`, `/hospital`, `/attraction`, `/accommodation`, `/place`) either 404 or render zero
  businesses server-side. `general` covers every business type anyway - the *query* picks the
  category, e.g. `강남 카페`, `부산 치과`, `홍대 헬스장`.
- **Opening hours are not returned.** Naver loads them through a later request and leaves the field
  null in the page payload, measured across 122 live businesses. Rather than ship a permanently
  empty column, we removed it. Blog tags and news thumbnails were dropped for the same reason.
- **Naver Place ignores `?page=`.** Page 2 returns the identical businesses. Depth therefore comes
  from sweeping the `regions` list (each region is a different map anchor and a different result
  set), not from paging - which is why `regions` exists.

### Reliability

Naver rate-limits by IP. This actor rotates a pool of independently-primed Korean residential proxy
sessions, one egress IP each, and **validates the payload rather than the status code** - a 200 that
came back without the expected data is treated as a throttle, rotated and retried.

- A transient block **never throws**. The run ends **Succeeded** with a status message and, on
  pay-per-event, **you are billed nothing for zero results**.
- Every run carries a **wall-clock budget** from `ACTOR_TIMEOUT_AT` and stops cleanly before the
  platform can kill it, so a run can never end **TIMED-OUT**. Proven: an unbounded run under a 120 s
  timeout finished Succeeded in 64 s with 36 complete records and a status message.
- Empty or malformed input runs a small real sample instead of failing.

### Input

```json
{
  "mode": "places",
  "placeType": "general",
  "queries": ["강남 카페"],
  "regions": ["서울", "부산"],
  "includeDetails": true,
  "maxItems": 50
}
```

| Field | Description |
|---|---|
| `mode` | `places` | `blogs` | `news` | `cafes` |
| `queries` | Search terms, Korean or English |
| `placeType` | `general` (any business type) or `beauty` |
| `regions` | Places only - sweep these regions for depth |
| `includeDetails` | Adds full article text / business detail fields |
| `maxItems` | `0` = unlimited (still stops safely before the timeout) |
| `sortBy` | `relevance` or `recent` |

### Use with AI assistants (MCP)

This actor works as a tool for AI agents through Apify's MCP server, so an assistant can look up
Korean businesses or Korean-language coverage on demand.

#### Agent-ready: autonomous discovery and payment

This Actor is **pay-per-event** with **limited permissions**, which makes it eligible for Apify's
**agentic payments**. AI agents can discover, run, and **pay for** this Actor autonomously - with no
Apify account - using **USDC on Base via [x402](https://docs.apify.com/platform/integrations/x402)**
or **[Skyfire](https://docs.apify.com/platform/integrations/skyfire)**.

- **MCP-native**: callable as a tool from any MCP-compatible assistant.
- **Deterministic pricing**: you are charged per result, so an agent can budget a task precisely.
- **No empty-result charges**: a run that returns nothing costs nothing.

### Legal

Collects **publicly available** information only. No login, no paywall bypass, no personal accounts.
Business contact details are published by the businesses themselves on their public Naver listings.
You are responsible for using the data in line with Naver's terms and applicable law, including
PIPA/GDPR where relevant.

# Actor input Schema

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

places = Korean local businesses with phone + address (lead generation). blogs / news / cafes = Naver search results, optionally enriched with the full post or article body.

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

One or more search terms. For places, combine a district with a business type for the best coverage, e.g. "강남 카페", "홍대 미용실".

## `placeType` (type: `string`):

"general" covers every business type - the query itself decides the category (e.g. "강남 카페", "부산 치과"). "beauty" uses Naver's hair & beauty lane, which adds booking scores and price info. Only these two lanes server-render results; the others Naver exposes are client-side only, so they are not offered rather than shipped returning zero.

## `regions` (type: `array`):

Naver Place anchors results to a map position, so depth comes from sweeping regions rather than paging. Leave empty to use the query as-is.

## `includeDetails` (type: `boolean`):

places: adds business hours, description, homepage, amenities and keywords. blogs/news: adds the full post/article text.

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

Stop after this many records. Set 0 for no limit (the run still stops safely before its timeout).

## `sortBy` (type: `string`):

Order search results by Naver relevance or newest first. Ignored in places mode.

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

Korean residential proxy is strongly recommended - Naver rate-limits by IP.

## Actor input object example

```json
{
  "mode": "places",
  "queries": [
    "강남 카페"
  ],
  "placeType": "general",
  "regions": [
    "서울",
    "부산",
    "인천"
  ],
  "includeDetails": true,
  "maxItems": 50,
  "sortBy": "relevance",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "KR"
  }
}
```

# Actor output Schema

## `leads` (type: `string`):

No description

# API

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

## JavaScript example

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

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

// Prepare Actor input
const input = {
    "mode": "places",
    "queries": [
        "강남 카페"
    ],
    "placeType": "general",
    "regions": [
        "서울",
        "부산",
        "인천"
    ],
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/naver-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": "places",
    "queries": ["강남 카페"],
    "placeType": "general",
    "regions": [
        "서울",
        "부산",
        "인천",
    ],
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/naver-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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": "places",
  "queries": [
    "강남 카페"
  ],
  "placeType": "general",
  "regions": [
    "서울",
    "부산",
    "인천"
  ],
  "maxItems": 50
}' |
apify call scrapesage/naver-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=scrapesage/naver-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/k9km7jIqhu5r5X76u/builds/7KKg9nUzGRAdvhszq/openapi.json