Naver Place Visitor & Blog Review Finder

What it returns

75 fields from the published dataset schema. Export as JSON, CSV or Excel, or read the dataset through the Apify API.

• reviewTypeRecord type: visitor, blog, or stats
• placeIdNaver Place ID
• placeNamePlace name
• placeCategoryPlace category (Korean)
• placeBusinessCategoryNaver business category, e.g. restaurant or cafe
• placeAddressPlace street address
• placeRoadAddressPlace road address
• placeRatingPlace-level average visitor review score
• placeTotalReviewsTotal visitor review count on the place
• placeBlogReviewCountTotal linked blog/cafe review count on the place
• placeUrlCanonical place URL
• searchKeywordKeyword that discovered this place (keyword-search mode only)
• searchRank1-based rank of the place in the keyword search result
• reviewIdVisitor review ID
• reviewTextFull review body (Korean), omitted for rating-only reviews
• reviewHasTextFalse when the review is rating-only
• reviewRatingReview star rating from 1 to 5, in 0.5 increments, when Naver exposes it; older anonymous reviews often omit it
• reviewerNameReviewer nickname (masked by Naver)
• reviewerProfileUrlReviewer profile URL
• reviewerImageUrlReviewer profile image URL
• reviewerFollowerCountReviewer follower count
• reviewerReviewCountTotal reviews authored by the reviewer
• reviewerAverageRatingReviewer's average rating across their reviews
• reviewDateReview creation date (YYYY-MM-DD, KST)
• reviewCreatedAtReview creation timestamp in ISO 8601 (KST)
• visitDateActual visit date (YYYY-MM-DD)
• visitCountNumber of visits reported by the reviewer
• visitCountLabelKorean visit label, e.g. 2번째 방문
• votedKeywordsNaver voted keyword tags, e.g. 음식이 맛있어요
• visitTagsVisit-context tags, e.g. 예약 없이 이용 or 혼자

Not in the schema among the core Naver fields: snippet, price. The field matrix shows which other tools return them.

How it differs from the other Naver Actors

Among the 5 catalogue Actors for Naver with a published schema, only this one returns reviewType, placeId, placeAddress, placeRating, placeTotalReviews, reviewId, reviewText, reviewHasText.

Pick another Actor if you need

Input

Example input

Built from the input form's published example values and defaults.

{
  "placeUrls": [
    "https://map.naver.com/p/entry/place/38239053"
  ],
  "maxPlacesPerKeyword": 3,
  "maxReviews": 3,
  "includeVisitorReviews": true,
  "includeRatingOnlyReviews": false,
  "includeBlogReviews": false,
  "maxBlogReviews": 10,
  "includeReviewPhotos": false,
  "includeReviewStats": false,
  "maxConcurrency": 3,
  "maxItems": 3
}

Run it from code or an AI agent

The same run through the Apify API, with the example input. You need an Apify API token; the run is billed to your account at the Store price.

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run_input = {
    "placeUrls": [
        "https://map.naver.com/p/entry/place/38239053"
    ],
    "maxPlacesPerKeyword": 3,
    "maxReviews": 3,
    "includeVisitorReviews": True,
    "includeRatingOnlyReviews": False,
    "includeBlogReviews": False,
    "maxBlogReviews": 10,
    "includeReviewPhotos": False,
    "includeReviewStats": False,
    "maxConcurrency": 3,
    "maxItems": 3
}

run = client.actor("dataspryva/naver-place-visitor-and-blog-review-finder").call(run_input=run_input)
if run is None:
    raise RuntimeError("The Actor run was not found.")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

import { ApifyClient } from "apify-client";

const client = new ApifyClient({ token: "<YOUR_APIFY_TOKEN>" });
const input = {
    "placeUrls": [
        "https://map.naver.com/p/entry/place/38239053"
    ],
    "maxPlacesPerKeyword": 3,
    "maxReviews": 3,
    "includeVisitorReviews": true,
    "includeRatingOnlyReviews": false,
    "includeBlogReviews": false,
    "maxBlogReviews": 10,
    "includeReviewPhotos": false,
    "includeReviewStats": false,
    "maxConcurrency": 3,
    "maxItems": 3
};

const run = await client.actor("dataspryva/naver-place-visitor-and-blog-review-finder").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

curl -X POST "https://api.apify.com/v2/actors/dataspryva~naver-place-visitor-and-blog-review-finder/run-sync-get-dataset-items"   -H "Authorization: Bearer $APIFY_TOKEN"   -H "Content-Type: application/json"   -d '{"placeUrls":["https://map.naver.com/p/entry/place/38239053"],"maxPlacesPerKeyword":3,"maxReviews":3,"includeVisitorReviews":true,"includeRatingOnlyReviews":false,"includeBlogReviews":false,"maxBlogReviews":10,"includeReviewPhotos":false,"includeReviewStats":false,"maxConcurrency":3,"maxItems":3}'

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=dataspryva/naver-place-visitor-and-blog-review-finder",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

What a run costs

The result rate falls on higher Apify plans. Each figure is the published per-result rate times the number of results.

• Every run also has a start event, charged per GB of memory (minimum one): $0.10 on Free, $0.03 on Business. At its default memory of 4 GB a run starts at $0.40 on Free. Fewer, larger runs keep this small.
• The Free plan includes $5 of monthly usage (Apify pricing, checked 2026-11-11); at the Free rate that covers at most about 5,050 results, less start events and platform usage.
• Worked example: 10,000 results in one run on the Free plan cost $10.30 ($9.90 for results + $0.40 start), plus Apify platform usage (compute), billed separately by Apify.
• Pay per event. Platform usage (compute) is billed by Apify on top of the event prices. Compare other tools in the cost estimator.

Where it fits among Naver routes

It ranks 3 of 5 catalogue Actors for Naver on the published formula (fields, price, reliability, freshness). Its line is highlighted on the map.

What people use it for

• Analyze visitor feedback
• Collect blog reviews
• Track place ratings

Other catalogue Actors for Naver

Similar Actors

Questions people ask

Sources

• Naver Place Visitor & Blog Review Finder on Apify Store
• Published build with input and output schema (JSON)
• Naver Open API and Maps API documentation