# Naver Map Scraper $1💰 Places, Menus, Reviews (`abotapi/naver-map-scraper`) Actor

From $1/1K. Scrape Naver Map places by keyword or URL: names, categories, ratings, phones, addresses, GPS, menus, opening hours, facilities, subway and bus transit, photos, plus visitor and blog reviews. 70+ fields, full pagination, three sort orders, fast and low cost.

- **URL**: https://apify.com/abotapi/naver-map-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Categories:** Travel, Lead generation, E-commerce
- **Stats:** 8 total users, 2 monthly users, 99.3% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 place 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/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 Map Scraper

Extract structured place data from Naver Map (map.naver.com), Korea's most-used maps and local search service. Search by keyword or paste place URLs, and get names, categories, ratings, phone numbers, addresses, GPS coordinates, menus, opening hours, facilities, nearby subway and bus stops, photos, and both visitor and blog reviews. Paginates each keyword to its full result count.

### Why this scraper

- 70+ fields per place, far more than list-only alternatives: GPS, place id, road and lot addresses, virtual phone, facilities, payment options, transit, photos, and reviews.
- Three input shapes: keyword search, a pasted place URL (including short naver.me links), and a pasted search URL.
- Full pagination: every keyword walks to its complete result set (often thousands of places), not just the first page.
- Three sort orders: relevance, distance (nearest first), and popularity.
- Menus, opening hours, and facilities extracted from the full place page.
- Visitor reviews (star rating, text, author, visit date, photos, keyword tags) and blog reviews (title, body, link, author, thumbnail).
- Fast and cheap: the default connection works on every Apify plan, so a trial run costs almost nothing.

### Data you get

> Sample shape, values are illustrative placeholders, not from a live listing.

| Field | Example |
| --- | --- |
| name | "Sample Dumpling House" |
| category | "Korean restaurant" |
| businessCategory | "restaurant" |
| placeId | "00000001" |
| placeUrl | "https://map.naver.com/p/entry/place/00000001" |
| latitude | 37.5000 |
| longitude | 127.0000 |
| phone | "+820000000000" |
| virtualPhone | "+820000000000" |
| address | "Sample-dong 000-0" |
| roadAddress | "Sample-ro 000" |
| fullAddress | "Seoul Sample-gu Sample-dong 000-0" |
| visitorReviewScore | 4.4 |
| visitorReviewCount | 0 |
| totalReviewCount | 0 |
| blogCafeReviewCount | 0 |
| distance | "120m" |
| imageUrls | \["https://example.com/photo-000.jpg"] |
| conveniences | \["Parking", "Wi-Fi"] |
| paymentInfo | \["Card", "Mobile pay"] |
| openingHours | { ... structured hours ... } |
| menus | \[ { "name": "Sample Menu", "price": "0", "images": \[] } ] |
| subwayStations | \[ { "displayName": "Sample Station", "nearestExit": "0", "walkTime": 2 } ] |
| busStations | \[ { "name": "Sample Stop", "walkTime": 1 } ] |
| topPhotos | \["https://example.com/photo-000.jpg"] |
| blogReviews | \[ { "title": "Sample blog title", "url": "https://example.com/blog/000" } ] |
| visitorReviews | \[ { "rating": 5, "body": "Sample review text", "authorNickname": "user000" } ] |
| searchKeyword | "dumpling house" |

### How to use

Pick a mode, then fill in the matching section. Examples:

**Basic keyword search (fast, list only)**

```json
{
  "mode": "search",
  "keywords": ["만두집"],
  "includeDetails": false,
  "maxItems": 20
}
```

**Keyword search with full details and reviews**

```json
{
  "mode": "search",
  "keywords": ["강남 카페"],
  "sort": "popular",
  "includeDetails": true,
  "includeReviews": true,
  "maxReviews": 30,
  "maxItems": 50
}
```

**Nearest places to a point**

```json
{
  "mode": "search",
  "keywords": ["카페"],
  "sort": "distance",
  "searchCoordinates": "37.4979,127.0276",
  "maxItems": 30
}
```

**Specific place and search URLs**

```json
{
  "mode": "url",
  "startUrls": [
    "https://m.place.naver.com/restaurant/00000001/home",
    "https://map.naver.com/p/search/서울 호텔"
  ],
  "includeDetails": true,
  "maxItems": 40
}
```

### Input parameters

| Parameter | Type | Default | Description |
| --- | --- | --- | --- |
| mode | string | "search" | "search" runs the keywords; "url" scrapes pasted URLs. |
| keywords | array | \["만두집"] | Search terms (search mode). Each is paginated to its full result count. |
| sort | string | "relevance" | "relevance", "distance" (nearest first), or "popular" (search mode). |
| searchCoordinates | string | central Seoul | Map centre "lat,lng" that biases results and powers distance sort. |
| startUrls | array | (none) | Naver Map place or search URLs, including short naver.me links (url mode). |
| includeDetails | boolean | true | Fetch the full place page (menus, hours, facilities, transit, photos, blog reviews). |
| includeReviews | boolean | false | Collect paginated visitor (star) reviews. |
| maxReviews | integer | 20 | Upper bound on visitor reviews collected per place. |
| maxItems | integer | 20 | Stop after this many places. 0 means no limit. |
| proxy | object | Apify datacenter | Connection settings. The default connection is the cheapest reliable option. |
| maxResidentialMB | integer | 0 | Residential traffic budget; after it, the run auto-downgrades to datacenter. 0 = no cap. |
| resumeFromRunId | string | (none) | Continue one interrupted run: paste a previous run/dataset ID to skip places it already collected. |
| incrementalMode | boolean | false | Recurring monitoring: remembers the previous run of the same search itself and returns only NEW/UPDATED/REAPPEARED places (see below). |
| stateKey | string | (auto) | Name an incremental-mode monitoring campaign, or share state across runs. Auto-derived from the search + settings when empty. |
| emitUnchanged | boolean | false | Incremental mode only: also return (and bill) places unchanged since the last run. |
| emitExpired | boolean | false | Incremental mode only: also return (and bill) places no longer found, once a run fully scans the tracked search. |
| mcpConnectors | array | (none) | Optional: pipe results into Notion, Linear, Airtable, or Apify apps. |

### Resume & recurring updates

Two distinct features, both off by default:

- **`resumeFromRunId`** continues ONE interrupted crawl. Paste a previous run ID or dataset ID and this run skips every place id it already collected — no duplicates, no re-charging.
- **`incrementalMode`** is for scheduling this actor daily or weekly against the same search. The actor remembers the previous run itself (no id to paste) and tags every place with `changeType` (`NEW`, `UPDATED`, `UNCHANGED`, `REAPPEARED`, or `EXPIRED`), `changedFields`, `firstSeenAt`, and `lastSeenAt`. By default only NEW/UPDATED/REAPPEARED places are returned; turn on `emitUnchanged`/`emitExpired` to also get (and pay for) the rest. State is tracked per place id (`id`, the same value as `placeId`), scoped to the search (mode, keywords/URLs, sort, search centre, and the detail/review toggles) — different searches never share state unless you set the same `stateKey` explicitly. `EXPIRED` rows are only emitted once a run fully scans its tracked search (not when Max records capped it, Resume was used, or a search could not be reached), so a partial run never wrongly marks a place as gone.

Visitor review counts, ratings, and new reviews are real, live data — incremental mode reports them as UPDATED like any other change, it does not filter them out.

### Send results into your apps (MCP connectors)

Optionally mirror results into the apps you already use through Model Context Protocol (MCP) connectors. Authorize a connector once under Apify, Settings, Integrations, then select it in the `mcpConnectors` input. For Notion, also set `notionParentPageUrl`. The connector receives a condensed, human-readable summary per item (a title plus key fields), while the complete record always stays in the Apify dataset. Leaving `mcpConnectors` empty skips the export entirely and never changes the dataset output.

### Output example

> Sample shape, values are illustrative placeholders, not from a live listing.

```json
{
  "recordType": "place",
  "id": "00000001",
  "placeId": "00000001",
  "name": "Sample Dumpling House",
  "category": "Korean restaurant",
  "businessCategory": "restaurant",
  "placeUrl": "https://map.naver.com/p/entry/place/00000001",
  "latitude": 37.5000,
  "longitude": 127.0000,
  "distance": "120m",
  "phone": "+820000000000",
  "virtualPhone": "+820000000000",
  "address": "Sample-dong 000-0",
  "roadAddress": "Sample-ro 000",
  "fullAddress": "Seoul Sample-gu Sample-dong 000-0",
  "visitorReviewScore": 4.4,
  "visitorReviewCount": 0,
  "totalReviewCount": 0,
  "blogCafeReviewCount": 0,
  "imageUrls": ["https://example.com/photo-000.jpg"],
  "conveniences": ["Parking", "Wi-Fi"],
  "paymentInfo": ["Card"],
  "openingHours": null,
  "menus": [{ "name": "Sample Menu", "price": "0", "recommend": false, "images": [] }],
  "subwayStations": [{ "displayName": "Sample Station", "nearestExit": "0", "walkTime": 2, "walkingDistance": 130 }],
  "busStations": [{ "name": "Sample Stop", "walkTime": 1, "walkingDistance": 20 }],
  "topPhotos": ["https://example.com/photo-000.jpg"],
  "blogReviews": [{ "title": "Sample blog title", "url": "https://example.com/blog/000", "authorName": "blogger000" }],
  "visitorReviews": [{ "rating": 5, "body": "Sample review text", "authorNickname": "user000", "visited": "0.0" }],
  "searchKeyword": "dumpling house"
}
```

### Plan requirement

The default connection works on every Apify plan, including the free tier. Residential connections are optional and only useful if the default is ever blocked; pick a country of `KR` if you enable them. Korean text (keywords, names, addresses, reviews) is fully supported in both input and output.

# Actor input Schema

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

How to choose what to scrape. 'search' runs the keywords you enter; 'url' scrapes specific Naver Map place or search URLs you paste.

## `keywords` (type: `array`):

One or more Naver Map search terms, for example 만두집, 강남 카페, or 서울 호텔. Each keyword is paginated to its full result count (capped by Max records). Only applies in 'search' mode.

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

Order of search results. 'relevance' is Naver's default ranking; 'distance' returns the nearest places first (relative to the search centre); 'popular' favours well-reviewed places. Only applies in 'search' mode.

## `searchCoordinates` (type: `string`):

Optional map centre that biases results and powers the 'distance' sort, written as 'latitude,longitude' (for example 37.4979,127.0276 for Gangnam). Defaults to central Seoul. Only applies in 'search' mode.

## `startUrls` (type: `array`):

Naver Map URLs to scrape: a place page (map.naver.com/p/entry/place/1234567, m.place.naver.com/restaurant/1234567/home), a short naver.me link, or a search page (map.naver.com/p/search/만두집). Multiple URLs supported. Only applies in 'url' mode.

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

Fetch the full place page for each result: menus, opening hours, facilities, payment options, exact coordinates, nearby subway and bus stops, photos, and blog reviews. This makes one extra request per place, so it is slower and billed separately. Turn off for a fast, cheap list-only run.

## `includeReviews` (type: `boolean`):

Collect star-rated visitor reviews for each place (rating, text, author, visit date, photos, keyword tags), paginated up to Max reviews per place. Adds extra requests per place.

## `maxReviews` (type: `integer`):

Upper bound on visitor reviews collected per place when Include visitor reviews is on. 0 disables review collection.

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

Stop after this many places across the whole run. The default (20) keeps a trial run small and cheap; set 0 for no limit (full coverage of every keyword, which can be thousands of places per keyword).

## `proxy` (type: `object`):

Connection settings. The default connection works on every Apify plan, including the free tier. A residential connection is optional and only needed if the default is ever blocked.

## `maxResidentialMB` (type: `integer`):

Only applies when the proxy group is RESIDENTIAL. After this many MB of residential traffic, the run auto-downgrades to the cheaper datacenter tier. 0 means no budget cap.

## `resumeFromRunId` (type: `string`):

Paste a previous run ID or dataset ID to continue a large keyword pull without returning or charging for places already collected there. Use this after an interrupted run. For recurring daily/weekly monitoring of the same search, use Incremental mode below instead.

## `incrementalMode` (type: `boolean`):

Turn this on for daily or recurring monitoring. The first run returns all matching places as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED places, tagged with changeType/changedFields/firstSeenAt/lastSeenAt. Turn on "Emit unchanged" or "Emit expired" only when you also want those places returned (and billed). State is kept separately per search + sort + coordinates + detail settings; use State key to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above.

## `stateKey` (type: `string`):

Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the search/sort/coordinates and detail settings — different searches then never mix state with each other.

## `emitUnchanged` (type: `boolean`):

Off by default. Turn on to also return places that have not changed since the last run, marked UNCHANGED. This returns — and bills — extra rows you already have, so leave it off unless you specifically want the full snapshot every run.

## `emitExpired` (type: `boolean`):

Off by default. Turn on to also return places that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search — not when Max records capped it, Resume was used, or a search could not be reached. This returns — and bills — extra synthetic rows, so leave it off unless you need expiry tracking.

## `mcpConnectors` (type: `array`):

Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify → Settings → Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON — the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).

## `notionParentPageUrl` (type: `string`):

URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on items written to each connector per run. Does not affect the dataset.

## Actor input object example

```json
{
  "mode": "search",
  "keywords": [
    "만두집"
  ],
  "sort": "relevance",
  "startUrls": [
    "https://map.naver.com/p/search/강남 카페"
  ],
  "includeDetails": true,
  "includeReviews": false,
  "maxReviews": 20,
  "maxItems": 20,
  "proxy": {
    "useApifyProxy": true
  },
  "maxResidentialMB": 0,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "maxNotifyListings": 50
}
```

# Actor output Schema

## `overview` (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": "search",
    "keywords": [
        "만두집"
    ],
    "startUrls": [
        "https://map.naver.com/p/search/강남 카페"
    ],
    "maxItems": 20,
    "proxy": {
        "useApifyProxy": true
    },
    "incrementalMode": false,
    "emitUnchanged": false,
    "emitExpired": false
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/naver-map-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": "search",
    "keywords": ["만두집"],
    "startUrls": ["https://map.naver.com/p/search/강남 카페"],
    "maxItems": 20,
    "proxy": { "useApifyProxy": True },
    "incrementalMode": False,
    "emitUnchanged": False,
    "emitExpired": False,
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/naver-map-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": "search",
  "keywords": [
    "만두집"
  ],
  "startUrls": [
    "https://map.naver.com/p/search/강남 카페"
  ],
  "maxItems": 20,
  "proxy": {
    "useApifyProxy": true
  },
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false
}' |
apify call abotapi/naver-map-scraper --silent --output-dataset

```

## MCP server setup

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

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/shNWn0aliF3bAl3WJ/builds/fDyuMqddsHftrE1JZ/openapi.json