Naver: scrapers and the official API, compared

Route map

Each line is one way to get Naver data; each stop is a field you probably need. Green lines are catalogue Actors, ranked by the published formula.

Which route for which job

The catalogue Actors for Naver return different records. "Only this route" lists the published fields no other Actor in this table returns, which is usually what decides the choice. Cost is the published per-result rate; start events and platform usage are extra.

Field matrix: who returns what

Every tool with a published output schema, against the 7 fields most Naver jobs need. A dot means the field name appears in the schema; rows can still leave it empty.

Field dictionary: the exact keys

The same core field has a different key in each Actor's output. Map these before you merge datasets; a dash means the published schema has no matching key. Need a field that is not listed here, such as email? Search every Naver Actor by field.

Download this comparison: CSV · JSON (every tool with a published schema, matching keys per core field, price and score).

All 13 tools, scored

Catalogue Actors link to their detail pages; the score (0 to 100) is the published formula, identical for every tool. Other Store tools follow in their own table, for reference. Price is the published primary-result rate per 1,000 (the Free-plan rate where the price is tiered; higher Apify plans pay less); start events and platform usage are excluded.

Other Store tools, for reference

Scored with the same published formula and listed for comparison only; this site does not link or recommend them.

What to check before you choose

Teams use Naver data to research Korean search visibility, local businesses, customer feedback and shopping offers. Search results help locate relevant pages, while listing and review records support analysis of specific places.

Choose a search collector for discovery, a blog extractor for post research, or a Place review tool for feedback. Use shopping tools for offers, and assess the official search and Maps products separately because their access conditions differ.

Checklist

• Choose the Naver surface first: web results, blogs, shopping and Place reviews have different records and coverage.
• Keep placeRating separate from reviewRating, and verify whether an address is supplied as placeAddress, placeRoadAddress or roadAddress.
• Inspect the schema for the content you need: the listed blog fields do not identify a full-text field, and the business listing fields do not identify menu items.

Where the data is incomplete

Tool titles and use cases describe broader coverage than some listed schemas establish. A contentLength field does not supply the post text.

The published data's price summary and evidence note disagree about the cheapest route, so confirm billing on the relevant tool page. The leading tool's detailed schema is also absent, leaving its exact output coverage unconfirmed here.

Official API route

Terms and personal data

Keep business-data collection to public listings and follow Naver's terms. Review the conditions for the specific search or Maps product you use. This is general information, not legal advice.

Read Naver's terms. Keep to public data, do not bypass logins or access controls, and check whether personal data is involved before you collect it. The can-I-scrape checklist walks through it.

How to start

1. Open the recommended Naver tool and identify which search or content sources its documented inputs support. Choose a narrow Korean query or public source appropriate to that coverage.
2. Collect a small dataset and inspect whether the rows contain search results, posts, businesses or reviews. Check destination links and any place identifiers before joining records.
3. Save the output with the query or source used. Map the available fields to your required columns and record any missing text, address or rating data.

Call Naver Map Business Listings with Menu & Hours Data from code

The example input uses the Actor's published defaults; set your own Naver query before you run it. You need an Apify API token.

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run_input = {
    "mode": "search",
    "searchKeywords": [
        "강남 맛집"
    ],
    "placeUrls": [],
    "sortBy": "relevance",
    "maxResultsPerKeyword": 20,
    "includeDetails": True,
    "includeReviews": False,
    "maxReviewsPerPlace": 10,
    "openNow": False,
    "hasBooking": False,
    "hasNpay": False,
    "hasCoupon": False,
    "takeout": False,
    "newlyOpened": False,
    "wheelchairAccessible": False,
    "maxItems": 100,
    "monitoringMode": False,
    "emitUnchanged": False
}

run = client.actor("dataspryva/naver-map-business-listings-with-menu-and-hours").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 = {
    "mode": "search",
    "searchKeywords": [
        "강남 맛집"
    ],
    "placeUrls": [],
    "sortBy": "relevance",
    "maxResultsPerKeyword": 20,
    "includeDetails": true,
    "includeReviews": false,
    "maxReviewsPerPlace": 10,
    "openNow": false,
    "hasBooking": false,
    "hasNpay": false,
    "hasCoupon": false,
    "takeout": false,
    "newlyOpened": false,
    "wheelchairAccessible": false,
    "maxItems": 100,
    "monitoringMode": false,
    "emitUnchanged": false
};

const run = await client.actor("dataspryva/naver-map-business-listings-with-menu-and-hours").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

curl -X POST "https://api.apify.com/v2/actors/dataspryva~naver-map-business-listings-with-menu-and-hours/run-sync-get-dataset-items"   -H "Authorization: Bearer $APIFY_TOKEN"   -H "Content-Type: application/json"   -d '{"mode":"search","searchKeywords":["강남 맛집"],"placeUrls":[],"sortBy":"relevance","maxResultsPerKeyword":20,"includeDetails":true,"includeReviews":false,"maxReviewsPerPlace":10,"openNow":false,"hasBooking":false,"hasNpay":false,"hasCoupon":false,"takeout":false,"newlyOpened":false,"wheelchairAccessible":false,"maxItems":100,"monitoringMode":false,"emitUnchanged":false}'

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=dataspryva/naver-map-business-listings-with-menu-and-hours",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

Questions people ask

More on Naver

• Topic groupLocal business data: every website compared
• ToolWhich Naver route fits your job?
• ToolNaver cost by Apify plan, rows and runs

Related websites

• Google Search4 Actors
• Yandex4 Actors

Sources

• Naver Map Business Listings with Menu & Hours Data on Apify Store
• Naver Shopping Price Comparison Scraper on Apify Store
• Naver Place Visitor & Blog Review Finder on Apify Store
• Naver Blog Post Search & Full Content Extractor on Apify Store
• Naver Web, Blog, Cafe & News Results Scraper on Apify Store
• Naver Open API and Maps API documentation
• Official source, checked 2026-11-09
• Naver terms