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

{
  "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:

{
  "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:

{
  "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.