# Naver Place Scraper - Korea Local Business & Map Data (`haketa/naver-place-scraper`) Actor

Naver Place & Naver Map scraper (Korea): search local businesses by area + keyword and export name, category, address, phone, rating, visitor & blog review counts, hours and GPS coordinates. Korea local-business lead generation and market data — fast, no login.

- **URL**: https://apify.com/haketa/naver-place-scraper.md
- **Developed by:** [Haketa](https://apify.com/haketa) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 19 total users, 4 monthly users, 98.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.70 / 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?

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 Place Scraper 🇰🇷 — Korea Local Business & Map Data

Extract **local business data from Naver Place / Naver Map** — Korea's #1 local directory — as clean, structured JSON. Search by **area + keyword** (e.g. `강남 맛집`) and get **name, category, road & lot address, phone, rating, visitor & blog review counts, business hours, coordinates, booking links** and more.

> 💡 **Why Naver, not Google Maps?** In Korea, **Google Maps is structurally weak** (Korean law restricts exporting map data), so Naver dominates local search. Naver Place is *the* source for Korean restaurants, cafes, shops and services — data the global Google Maps scrapers simply can't deliver.

***

### 📋 Table of contents

- [What does it do?](#what-does-it-do)
- [Use cases](#use-cases)
- [How to use it](#how-to-use-it-step-by-step)
- [Input parameters](#input-parameters)
- [Input examples](#input-examples)
- [Output — data fields](#output--data-fields)
- [Sample output record](#sample-output-record)
- [Tips & best practices](#tips--best-practices)
- [Frequently asked questions](#frequently-asked-questions)
- [Changelog](#changelog)

***

### What does it do?

Give it Korean **search queries** (area + keyword) and it returns every matching place with a rich profile:

- 🏪 **Identity:** name, category, business category, description.
- 📍 **Location:** road address, lot (jibun) address, full address, and **GPS coordinates**.
- 📞 **Contact:** phone and Naver virtual phone number.
- ⭐ **Reputation:** visitor review score (rating), visitor review count, **blog/cafe review count**, total review count.
- 🕒 **Details:** business hours, amenities/options, booking link, Naver Pay, Michelin guide flag, images.

Export to **JSON, CSV, Excel, XML or HTML**, or pull from the **Apify API**.

***

### Use cases

**📇 Korea lead generation & local marketing**

- Build lists of Korean businesses by area + category with **phone + address** for outreach.
- Target restaurants, cafes, salons, clinics by neighborhood.

**📊 Market & competitive research**

- Map business density, ratings and review volume across Korean districts.
- Benchmark competitors by reviews and rating.

**🍽️ Food / travel / review platforms**

- Aggregate Korean restaurant/cafe data with ratings and coordinates.

**🤖 Data & AI teams**

- Build Korean local-business datasets with reputation signals.

***

### How to use it (step by step)

No coding required.

1. Click **Try for free / Start**.
2. Add **Search queries** in Korean — area + keyword, e.g. `강남 맛집`, `홍대 카페`, `제주 호텔`.
3. Pick a **Place type** (restaurants, all places, hair/beauty, hospitals, attractions).
4. Set **Max places**.
5. Keep the proxy on its default — **KR Residential** (required).
6. Click **Save & Start**, then export the results.

***

### Input parameters

| Field | Type | Description |
|------|------|-------------|
| `queries` | array | Korean search queries (area + keyword), e.g. `강남 맛집`. |
| `searchType` | string | Place vertical: `restaurant`, `place`, `hairshop`, `hospital`, `attraction`. |
| `maxItems` | integer | Max places. `0` = no limit. Default `200`. |
| `maxPagesPerQuery` | integer | Pagination cap per query (~50 places/page). Default `10`. |
| `proxyConfiguration` | object | **KR Residential required** (Naver needs a Korean IP and rate-limits hard). Default. |
| `maxConcurrency` | integer | Keep low — per-IP rate limits. Default `2`. |

***

### Input examples

**1) Restaurants in Gangnam**

```json
{
  "queries": ["강남 맛집"],
  "searchType": "restaurant",
  "maxItems": 200
}
```

**2) Cafes across several areas**

```json
{
  "queries": ["홍대 카페", "성수 카페", "연남동 카페"],
  "searchType": "restaurant",
  "maxItems": 1000
}
```

**3) Hair salons in Seoul**

```json
{
  "queries": ["서울 미용실"],
  "searchType": "hairshop"
}
```

***

### Output — data fields

One record per place:

| Field | Description |
|------|-------------|
| `placeId` | Naver place ID |
| `name` | Business name |
| `category` / `businessCategory` | Category |
| `description` | Short description |
| `roadAddress` | Road-name address |
| `address` | Lot (jibun) address |
| `fullAddress` / `commonAddress` | Full / common address |
| `phone` / `virtualPhone` | Phone numbers |
| `latitude` / `longitude` | GPS coordinates |
| `visitorReviewScore` | Visitor rating |
| `visitorReviewCount` | Visitor review count |
| `blogCafeReviewCount` | Blog/cafe review count |
| `bookingReviewCount` / `totalReviewCount` | Booking / total review counts |
| `businessHours` / `newBusinessHours` | Hours |
| `options` | Amenities / options |
| `hasBooking` / `bookingUrl` | Naver booking |
| `hasNPay` | Naver Pay accepted |
| `michelinGuide` | Michelin guide info |
| `imageUrl` / `imageCount` / `imageUrls` | Images |
| `placeUrl` / `mobileUrl` | Naver Place URLs |
| `searchQuery` | The query that produced this record |
| `scrapedAt` | ISO timestamp |

***

### Sample output record

```json
{
  "placeId": "1046192699",
  "name": "봉계타 현대백화점 무역센터점",
  "category": "칼국수,만두",
  "roadAddress": "테헤란로 517 현대백화점 무역센터점 10층",
  "address": "삼성동 159-7",
  "phone": "02-3467-6698",
  "latitude": 37.5085258,
  "longitude": 127.059807,
  "visitorReviewScore": 4.5,
  "visitorReviewCount": 2076,
  "blogCafeReviewCount": 512,
  "totalReviewCount": 2588,
  "hasBooking": true,
  "placeUrl": "https://map.naver.com/p/entry/place/1046192699",
  "searchQuery": "강남 맛집",
  "scrapedAt": "2026-06-05T17:00:00.000Z"
}
```

***

### Tips & best practices

- 🇰🇷 **Keep the default KR Residential proxy** — Naver requires a Korean IP and blocks others.
- 🗺️ **Use area + keyword queries** (`강남 맛집`, `부산 카페`) — combine many to cover a region.
- 🧪 **Start with one query** and a small `maxItems` to confirm the output.
- 🐢 **Keep concurrency low** — Naver rate-limits per IP.
- 💾 **Use the Apify API / integrations** to push results into Google Sheets, a CRM, or a webhook, and **schedule** runs to track new openings and ratings.

***

### Frequently asked questions

**Do I need a Korean proxy?**
Yes — Naver only serves a Korean IP reliably and rate-limits others. The actor defaults to KR Residential; keep it.

**Does it include ratings and review counts?**
Yes — visitor rating, visitor review count, and blog/cafe review counts.

**Does it return phone numbers and addresses?**
Yes — phone, virtual phone, road and lot addresses, plus GPS coordinates.

**Can I scrape cafes / salons / clinics, not just restaurants?**
Yes — set the **Place type** (restaurants/cafes, all places, hair & beauty, hospitals, attractions).

**What export formats are supported?**
JSON, CSV, Excel, XML, HTML table, RSS — plus the Apify API and integrations.

***

### Changelog

**Last updated:** 2026-07-02 — Actor verified and maintained. Data pipeline tested for quality, structure and freshness; selectors/endpoints confirmed against the live site.

**0.1.0**

- Initial release: search Naver Place by area + keyword with automatic pagination.
- Rich place records: category, road & lot address, phone & virtual phone, rating, visitor & blog review counts, hours, coordinates, booking and images.
- KR residential proxy handling; fast API-first parsing (no browser).

# Actor input Schema

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

What to look for on Naver Place. Combine an area with a keyword, e.g. '강남 맛집' (Gangnam restaurants), '홍대 카페' (Hongdae cafes) or '제주 호텔' (Jeju hotels). Each line is searched separately. Leave empty to run a ready-made sample of popular Korean searches.

## `searchType` (type: `string`):

Which Naver Place section to search in. Pick 'Restaurants & cafes' for food, 'All places' for any business, or a specific category.

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

Stop after collecting this many places across all searches. Use 0 for no limit.

## `maxPagesPerQuery` (type: `integer`):

How deep to page through each search (about 50 places per page). Raise it to go deeper, lower it to finish faster.

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

Naver serves Korea-specific results and works best from a Korean IP. Korean residential proxies are the reliable default — keep this on for complete, accurate data.

## `maxConcurrency` (type: `integer`):

How many searches to process in parallel. The default keeps results reliable and complete.

## Actor input object example

```json
{
  "queries": [
    "강남 맛집",
    "홍대 카페",
    "제주 호텔"
  ],
  "searchType": "restaurant",
  "maxItems": 100,
  "maxPagesPerQuery": 10,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "KR"
  },
  "maxConcurrency": 2
}
```

# Actor output Schema

## `places` (type: `string`):

All place records collected during the run.

## `runUrl` (type: `string`):

Open this run in the Apify Console.

# 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": [
        "강남 맛집",
        "홍대 카페",
        "제주 호텔"
    ],
    "maxItems": 100,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "KR"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("haketa/naver-place-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": [
        "강남 맛집",
        "홍대 카페",
        "제주 호텔",
    ],
    "maxItems": 100,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "KR",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("haketa/naver-place-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": [
    "강남 맛집",
    "홍대 카페",
    "제주 호텔"
  ],
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "KR"
  }
}' |
apify call haketa/naver-place-scraper --silent --output-dataset

```

## MCP server setup

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