Naver Map Places Scraper
Pricing
from $0.47 / 1,000 place saveds
Naver Map Places Scraper
Extract public Naver Map business listings with addresses, phones, websites, coordinates, categories, review counts, and place URLs.
Pricing
from $0.47 / 1,000 place saveds
Rating
0.0
(0)
Developer
Fetch Cat
Maintained by CommunityActor stats
0
Bookmarked
6
Total users
1
Monthly active users
9 days ago
Last modified
Categories
Features
Share
Extract public Naver Map places for Korean local-business research, local SEO and lead lists. Search by Korean keywords or look up a place by its numeric ID or full Naver place URL, then export names, available contact details, addresses, coordinates and review counts.
This is a listing scraper, not a review-text exporter. Search results are limited to the places Naver returns, with a maximum of 70 per query. Optional fields can be empty.
Quick start
- Open the Actor input and enter a focused search in
queries. - Add an optional
locationhint and start with a small result limit. - Run the Actor and download the dataset as JSON, CSV or Excel.
{"queries": ["카페"],"location": "서울","maxResultsPerQuery": 10,"proxyConfiguration": { "useApifyProxy": false }}
Korean terms generally work best for local searches. A location hint adds text to the search. It is not a geographic boundary or distance filter.
Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.
Ready-to-run examples
Choose a public example to see its settings before starting a run:
What you get
- Local SEO research: compare public listing names, categories and review counts by search term.
- Business prospecting: export available phones, websites and Naver place links for review in a CRM.
- Market research: compare business categories across focused city or district searches.
- Directory enrichment: use place IDs and links to connect results with your own business records.
Who is it for?
- Korean local-market researchers examining focused place-search samples.
- Local SEO analysts retaining listing categories and source review counts.
- Business-research teams checking publicly exposed contact and website information.
- Directory and data teams joining place IDs to their own business records.
How you can use the data
- Review the existing Seoul cafe sample. Use 카페 with the 서울 location hint, ten places per query and explicit direct access. Keep placeId, naverUrl and available addresses for manual checking: the location text is not a geographic boundary.
- Keep public contact details in source context. Retain available phone and website fields with source links when preparing a research or CRM shortlist. A phone can be a forwarding number, while a null value does not prove the business has no phone or site.
- Reconcile a known numeric place identity. Supply your own numeric ID or full Naver place URL for a smaller direct record of identity and available address, phone and website. Location hints are ignored and most search-only fields remain empty. Shortened naver.me links are not direct lookups.
- Compare focused query samples in your own dataset. Keep query and rank with review counts and collection time, joining placeId yourself across queries. Duplicate removal is per query, not across the whole export. Review counts are not review text or guaranteed totals, and source rank is not a custom market ranking.
Input settings
| Setting | API key | Behavior |
|---|---|---|
| Search terms or places | queries | Required array, up to 100 entries. Search terms, numeric place IDs and full Naver URLs containing /place/ID are accepted. |
| Location hint | location | Optional text appended to keyword searches. Ignored for direct place lookups. |
| Maximum places per query | maxResultsPerQuery | Integer from 1 to 70. Defaults to 10. A ceiling, not a guaranteed result count. |
| Include detail fields | includeDetails | Reserved setting, default true. Changing it currently has no effect on extraction or output. |
| Proxy configuration | proxyConfiguration | Explicit connection settings. See the input-field help. No automatic retry through a proxy is provided. |
For a direct lookup, put a numeric place ID or a full URL such as https://map.naver.com/p/entry/place/PLACE_ID in queries, replacing PLACE_ID with the actual numeric ID. Short naver.me links are not resolved as direct lookups. Direct lookups return a smaller record: ID, name and available address, phone and website. Most search-only fields remain empty.
Example inputs
Use the Quick start input as a small first run. Adjust the fields described above for your own data.
Output data
Each row represents a place. The following is an illustrative shape, not an observed listing:
{"query": "카페 서울","rank": 1,"placeId": "PLACE_ID","name": "Example business","category": null,"categories": [],"address": null,"roadAddress": null,"phone": null,"website": null,"naverUrl": "https://map.naver.com/p/entry/place/PLACE_ID","latitude": null,"longitude": null,"rating": null,"reviewCount": null,"visitorReviewCount": null,"blogReviewCount": null,"openingHours": null,"businessStatus": null,"tags": [],"placeDescription": null,"imageUrl": null,"menuInfo": null,"distanceMeters": null,"scrapedAt": "2026-10-25T00:00:00.000Z"}
| Fields | Meaning |
|---|---|
query, rank | Source query and source-provided rank, or position within that query's returned results. No custom sorting is applied. |
placeId, name, naverUrl | Place identifier, business name and Naver listing URL. |
category, categories | First category and category array when available. |
address, roadAddress | Address text and road-name address. |
phone, website | Available public contact number, which may be a forwarding number, and website. |
latitude, longitude, distanceMeters | Available numeric coordinates and source distance. Distance is not a user-selected radius. |
rating, reviewCount, visitorReviewCount, blogReviewCount | Available numeric rating and separate source counts. Not individual reviews or guaranteed totals. |
openingHours, businessStatus | Available source text, not a complete weekly opening schedule. |
tags, placeDescription, imageUrl, menuInfo | Available result labels/snippets, description, thumbnail URL and menu text. |
scrapedAt | ISO timestamp associated with the extraction. |
Empty fields mean the value was not available or usable for that result. They do not establish that a business lacks it. Duplicate place IDs are removed within each query, not across different queries. The same business can appear in several queries.
Download your results
Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.
See Apify's download and export guide for the available formats and field options.
Pricing
The start event is charged once after the first successful retrieval, including a valid empty search response. The item event applies to each saved place. Failed validation does not trigger start, unsaved places are not paid items, and later failures can leave previously saved, charged results.
Use a small per-query cap and few focused queries. See the live Pricing tab for current rates and plan-specific pricing. Connection settings can also affect Apify platform usage.
Tips for best results
- Use focused Korean terms and a city or district hint. The hint adds search text rather than enforcing an area.
- Set the per-query cap explicitly. Up to seventy places may be requested, without guaranteeing that many.
- Keep original place IDs and query attribution. The same business can appear under several queries.
- Check direct-lookup coverage separately. It returns fewer fields than search results.
- Read completed and pending query counts. A useful partial dataset does not prove every query finished.
Limits and caveats
Only public Naver Map place listings are supported without a Naver login. This is not an official Naver API, exhaustive Korea-wide directory, area sweep or review-text exporter. Full reviews and detailed menu enrichment are outside scope.
Up to one hundred query entries and seventy places per query are supported. Location appends search text rather than a strict area or radius filter and is ignored for direct lookups. Shortened naver.me links are not resolved as direct place inputs. Direct numeric-ID or full-place-URL records are smaller, leaving most search fields empty. IncludeDetails is reserved and does not change collection or output.
Search order follows Naver's returned position or source rank without custom sorting. Duplicate IDs are removed within each query rather than across queries. Public contact numbers can forward calls, distance is source-provided rather than a selected radius, and opening-hour text is not a complete weekly schedule. Ratings and separate visitor/blog counts can be absent and are not individual reviews or guaranteed totals. Null fields mean unavailable or unusable data rather than proof the business lacks it.
Challenges, temporary limits, changed pages and unavailable places can prevent collection. No automatic retry through a proxy is provided. The form disables proxy by default, while raw API input omitting the setting may use managed proxy defaults. Select the intended connection settings explicitly and do not assume proxy access guarantees.
An isolated query failure preserves useful results from completed queries but makes the run fail, with unfinished queries listed in RUN_SUMMARY. A valid no-match response completes successfully with no rows. An access failure is not privacy or deletion proof. RUN_SUMMARY reports saved counts, completed and pending queries, warnings and finish time. Longer runs may stop early, and saved progress supports platform migration rather than automatic recovery in a newly started run.
Automation and integrations
Save your settings for next time
Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.
Run on a schedule
Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.
Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.
Send results to your other tools
Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.
For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.
API usage
Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.
The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.
For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.
cURL
curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~naver-map-places-scraper/runs' \-H "Authorization: Bearer $APIFY_TOKEN" \-H 'Content-Type: application/json' \--data @- <<'JSON'{"queries": ["카페"],"location": "서울","maxResultsPerQuery": 10,"proxyConfiguration": {"useApifyProxy": false}}JSON
Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('fetch_cat/naver-map-places-scraper').call({"queries": ["카페"],"location": "서울","maxResultsPerQuery": 10,"proxyConfiguration": {"useApifyProxy": false}});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
Python
import osfrom apify_client import ApifyClientclient = ApifyClient(os.environ['APIFY_TOKEN'])run = client.actor('fetch_cat/naver-map-places-scraper').call(run_input={'queries': ['카페'], 'location': '서울', 'maxResultsPerQuery': 10, 'proxyConfiguration': {'useApifyProxy': False}})print(client.dataset(run['defaultDatasetId']).list_items().items)
API and AI-agent use notes
The cURL request starts a run asynchronously. Check the returned run ID until it completes, then fetch items from its defaultDatasetId using the Apify API.
MCP and AI agents
You can ask your AI assistant to collect data with Naver Map Places Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.
Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.
Easier setup with an Apify plugin
If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.
Use Apify AI in Console
Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Naver Map Places Scraper. You can describe the data you want and ask questions about the results.
Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.
Choose your assistant
- Claude and Claude Code (Anthropic): Apify setup guide.
- ChatGPT and Codex (OpenAI): Apify setup guides.
- Grok Bot (xAI): Apify plugin guide.
- Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.
Connect just this scraper
To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:
{"mcpServers": {"apify": {"url": "https://mcp.apify.com?tools=fetch_cat/naver-map-places-scraper"}}}
Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.
Use Apify's general server
Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Naver Map Places Scraper by Fetch Cat, or give it the identifier fetch_cat/naver-map-places-scraper.
Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.
Example requests
- “Use Fetch Cat’s Naver Map Places Scraper to collect up to 5 places for 카페 with location hint 서울 and explicit direct access. Keep IDs, place links and available addresses without treating the hint as a strict city boundary.”
- “Collect up to 5 카페 results with 서울 as a location hint and explicit direct access. Retain public phone and website fields for review, flagging missing values and possible forwarding numbers rather than claiming verified contacts.”
- “Retrieve up to 5 카페 places with 서울 as a location hint and explicit direct access. Keep source rank and separate visitor and blog review counts where available, and inspect completed or pending queries without collecting review text or starting automatic recovery.”
Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.
Pay with x402
If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.
Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.
Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.
Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.
Other ways for agents to pay
Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.
FAQ
Can I export Naver Map places as CSV or use an API?
Yes. Download the dataset as CSV, JSON or Excel, or use the Apify API and client libraries above. This Actor is not an official Naver API.
Can it extract full reviews or detailed menus?
No. It returns available review counts and search-result metadata. includeDetails does not add deeper enrichment, and direct place lookups return only a small set of fields.
How can I improve relevance or handle empty output?
Use a focused Korean search and a city or district hint. Check the run status and RUN_SUMMARY: a successful no-match search differs from a failed or unfinished query. The location hint is search text, not a strict area filter.
Why are phone numbers, ratings or coordinates missing?
Naver may not expose them in the returned result, or the value may not be usable as the expected type. Null fields do not establish that the listing has no such information.
What if Naver challenges the run?
Try a smaller focused input and review the connection-field help. The form defaults to proxy disabled. Raw API input that omits proxyConfiguration may use managed proxy defaults. Proxy use does not guarantee access.
Related Actors
- Google Maps Places Scraper — Research listings on another local-search source.
- Google Maps Lead Finder — Collect Google Maps business listings and optionally published contacts from business websites.
- Website Contact Finder — Inspect public business websites for contact information.
- Bing Maps Places Scraper — Compare listings from Bing Maps where available.
- 2GIS Places Scraper — Research businesses in supported 2GIS markets.
Support and feedback
For custom additions or integrations, email hello@fetchcat.dev.
Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.
Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.
Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.
Made with care for curious people, AI agents and the possibilities in data. ♥