# Naver Place (네이버 플레이스) Scraper - Korean Business + Reviews (`lanternlab318/naver-place`) Actor

Search Naver Map by Korean keyword or region, or paste Naver Place links, and get the public listing: place ID, name, category, lot and road address, business phone, coordinates, rating and review counts, plus public visitor reviews on request. Cut-short collection is marked partial, not zero.

- **URL**: https://apify.com/lanternlab318/naver-place.md
- **Developed by:** [Lantern Lab](https://apify.com/lanternlab318) (community)
- **Categories:** Lead generation, Travel, Business
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 90.9% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.19 / 1,000 places

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/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 Place (네이버 플레이스) Scraper - Korean Business + Reviews

Search Naver Map the way Korean customers do - a keyword plus a region, in Korean - or
paste Naver Place links, and get the public listing of every matching business back:
Naver's own place ID, name, category, lot address and road address, the phone the
business publishes, latitude and longitude, the star rating and the review counts. Turn
reviews on and every place also returns its public visitor reviews: star rating, review
text, the visit date and the publish date, and the reviewer's public display nickname.

**Price:** USD 3.19 per 1,000 places and USD 0.79 per 1,000 reviews. Rows that only
report a status - a search term that found nothing, a dead link, a list that was cut
short - are never charged.

No Naver account, cookie or login is used, and nothing behind a login is collected.

### What you get

| | |
| --- | --- |
| **Places** | `placeId`, `name`, `category`, `roadAddress`, `address`, `commonAddress`, `fullAddress`, `phone`, `virtualPhone`, `lat`, `lng`, `rating`, `reviewCount`, `blogReviewCount`, `url` |
| **Reviews** (optional) | `reviewId`, `placeId`, `rating`, `text`, `visitedAt`, `publishedAt`, `originType`, `language`, `nickname` |
| **Every row** | `recordType`, `collectedAt`, `partial`, `partialReason` |
| **Last row** | `RUN_SUMMARY`: what was collected, what was skipped as a duplicate, what is incomplete and why |

Every place and every review is written once per run, even when several of your search
terms return the same business. A search term that genuinely matched nothing is reported
as an empty result; a term or review list that was cut short by a limit or refused by
Naver is marked `partial` with a `partialReason`, so incomplete collection is never
served to you as "zero results".

### Input

```json
{
  "searchQueries": ["강남 카페", "부산 해운대 호텔"],
  "placeUrls": ["https://map.naver.com/p/entry/place/1498100901"],
  "maxPlacesPerQuery": 20,
  "includeReviews": true,
  "maxReviewsPerPlace": 50
}
```

Give `searchQueries`, `placeUrls`, or both. A place link may also be a bare numeric place
ID. `maxUpstreamRequests` is optional and caps the requests a run may send; left empty,
the Actor derives a ceiling from your input so a run is never unbounded.

### Output

One place row:

```json
{
  "recordType": "place",
  "placeId": "1498100901",
  "name": "그라운드8",
  "category": "카페",
  "roadAddress": "도산대로49길 41 2층",
  "address": "신사동 646-20",
  "commonAddress": "서울 강남구 신사동",
  "fullAddress": "서울특별시 강남구 신사동 646-20 2층",
  "phone": null,
  "virtualPhone": "0507-1302-6392",
  "lat": 37.5257026,
  "lng": 127.0369307,
  "rating": 4.97,
  "reviewCount": 423,
  "blogReviewCount": 250,
  "url": "https://map.naver.com/p/entry/place/1498100901",
  "source": "search",
  "sourceQuery": "강남 카페",
  "rank": 1,
  "partial": false,
  "partialReason": null,
  "collectedAt": "2026-10-24T09:12:31.004Z"
}
```

One review row:

```json
{
  "recordType": "review",
  "reviewId": "6adb5a64dfa2e4fc595b75e9",
  "placeId": "2025884279",
  "placeName": "대물섬 강남점",
  "rating": 5,
  "text": "쥐치부터 구이까지 최고!",
  "visitedAt": "2026-10-23",
  "visitedAtText": "10.23.금",
  "publishedAt": "2026-10-23",
  "publishedAtText": "10.23.금",
  "originType": "영수증",
  "language": "ko",
  "nickname": "mdl****",
  "rank": 1,
  "partial": false,
  "partialReason": null,
  "collectedAt": "2026-10-24T09:12:33.551Z"
}
```

### Limits

- **Korean terms work, English ones mostly do not.** This is Naver's Korean index:
  `강남 카페` returns thousands of matches, `gangnam cafe` returns almost none.
- **Dates have no year on Naver's page.** A review date is shown as `10.23.금` for the
  year in progress, so `publishedAt` and `visitedAt` are derived: the year in progress,
  or the year before when that date has not happened yet. The exact string Naver showed
  is always kept in `publishedAtText` and `visitedAtText`.
- **Addresses come in three widths.** A place found by search carries Naver's short road
  address (`도산대로49길 41 2층`), the city and district next to it in `commonAddress`, and
  the full lot address in `fullAddress`. A place fetched from a link carries the full road
  address in `roadAddress` and nothing in `commonAddress`, because that is how Naver's two
  endpoints answer.
- **`rating` is null when Naver publishes no star average**, which happens in some
  categories even for a place with hundreds of reviews. Null means "no rating published",
  not "rated zero".
- **`reviewCount` and the collected review total differ.** `reviewCount` is the number on
  the place's card; the review coverage row's `reviewsAvailable` is what the review
  endpoint reports for the same place, and it is usually a little lower. Both are Naver's
  own numbers from different places on its own site.
- **`phone` is often null and `virtualPhone` is filled instead.** Both are business
  contact numbers published on the place's own page; many Korean businesses only publish
  Naver's forwarding number.
- **One search term does not reach every match.** Naver reports a total for a term that
  is far larger than the list it will serve; `placesAvailable` on the search-term row is
  that total, and `placesReturned` is what was actually collected.
- **A review can carry no stars and no text.** Naver lets a visitor post keywords or a
  photo only: measured on 1,000 collected reviews, 799 had a star rating and 975 had
  text. `rating` and `text` are then null rather than 0 or an empty string.
- **Reviews are newest first**, 50 per request, and only visitor reviews. Blog and cafe
  posts about a place are not collected; `blogReviewCount` only tells you how many exist.
- **naver.me short links are not supported.** Open one and paste the address it lands on.
- **Nothing private.** Only what the public place page shows. No account is used, and of
  a reviewer only the public display nickname is kept - no profile ID, link or photo.

# Actor input Schema

## `searchQueries` (type: `array`):

One Naver Map search term per line, the way you would type it on the map: a keyword plus a region works best, for example "강남 카페", "부산 해운대 호텔" or "서울 치과". Korean terms return far more than English ones because this is Naver's Korean index. Every term is searched separately and its places are labelled with it. A place that matches several of your terms is returned once and charged once. Give this, or placeUrls, or both.

## `placeUrls` (type: `array`):

One Naver Place link or numeric place ID per line, for example https://map.naver.com/p/entry/place/1498100901, https://pcmap.place.naver.com/restaurant/1498100901/home or just 1498100901. naver.me short links are not supported: open one and paste the address it lands on. A link whose place no longer exists is reported as not_found, not as a failure.

## `maxPlacesPerQuery` (type: `integer`):

Upper bound on the places one search term may produce. Naver serves 100 places per request and this Actor pages past that, so higher values cost more requests but do reach more places. Naver's own result list for a term runs out well before the total it reports, and the run says per term how many it actually got.

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

With this on, every place collected in the run also returns its public visitor reviews: star rating, review text, the visit date and the publish date as Naver shows them, the receipt/payment origin, and the reviewer's public display nickname. Reviews are charged per review, so leave this off when you only need the business listings.

## `maxReviewsPerPlace` (type: `integer`):

Upper bound on the reviews one place may produce, used only when reviews are on. Naver serves 50 reviews per request and this Actor pages past that with Naver's own cursor, newest first. A place with fewer reviews than this returns all of them and says so.

## `maxUpstreamRequests` (type: `integer`):

Hard ceiling on the HTTP requests this run sends to Naver: search pages, place details and review pages together. At the ceiling collection stops - the inputs not finished are written with partialReason "upstream_request_cap" and the run then ends normally. Leave empty and the Actor works a ceiling out from your inputs and limits, so a run is never unbounded.

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

The proxy the requests to Naver go through. The default (Apify Proxy, datacenter) is the cheapest and is what this Actor is measured on; Naver serves these public place endpoints over it without a captcha, and the run rotates the exit IP per request because one IP that sends about five requests back to back is rate-limited. A Korean exit is not required.

## Actor input object example

```json
{
  "searchQueries": [
    "강남 카페"
  ],
  "maxPlacesPerQuery": 20,
  "includeReviews": false,
  "maxReviewsPerPlace": 50,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

No description

## `runSummary` (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 = {
    "searchQueries": [
        "강남 카페"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("lanternlab318/naver-place").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 = { "searchQueries": ["강남 카페"] }

# Run the Actor and wait for it to finish
run = client.actor("lanternlab318/naver-place").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 '{
  "searchQueries": [
    "강남 카페"
  ]
}' |
apify call lanternlab318/naver-place --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lanternlab318/naver-place"
        }
    }
}
```

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/2NuVWzYPDJzYlulDH/builds/1D7Obd5DE4lPwvRPO/openapi.json