This tutorial shows how to scrape Naver Map reviews from Naver Place visitor-review URLs into CSV with the Naver Map Review Scraper template for UScraper. You will prepare store URLs, import the workflow, set the export path, run one visible test, and validate Korean review rows.
Before you start
Prerequisites and source checks
You need UScraper as a local desktop app, the Naver Map Review Scraper template, an export folder, and Naver Place visitor-review URLs you are allowed to process. Start with one store URL to prove that the page loads, review cards render, Korean text exports correctly, and the folder is writable.
Open Naver Map or the mobile Naver Place page in your browser, search for the store, and navigate to the visitor reviews tab. Direct mobile review URLs are the most predictable input because the workflow is built around a rendered review page, not a keyword search page.
Technical access is not permission. Naver reviews can include personal data, copyrighted text, photos, and platform-specific visit signals. Review current policies, keep runs modest, and do not bypass CAPTCHA or login walls.
API or scraping
Naver Place reviews API vs scraping
Teams often search for a Naver Place reviews API because they want stable review data without browser automation. Official Naver resources serve different jobs. The Naver local search API is built for local search result data, while NAVER Cloud Maps products cover map display, geocoding, reverse geocoding, directions, and related location services.
Do not assume every visitor-review field shown on Naver Place is available through an official API. If your project requires sanctioned production access, start with the official Naver local search API documentation and NAVER Cloud Maps product page. If the job is a small CSV export from browser-visible pages, a no-code Naver review scraper can be the faster research path.
| Approach | Best fit | Trade-off |
|---|---|---|
| UScraper template | Controlled Naver review CSV exports from selected store URLs | Best for supervised research, not unattended high-volume crawling |
| Official Naver APIs | Approved apps that need documented search or maps capabilities | May not expose the same visitor-review fields visible in Naver Place |
| Hosted scraping actors | Cloud runs, scheduling, managed infrastructure | Store URLs and review data pass through a third-party service |
| Python or Selenium crawler | Engineering teams that need custom parsing and pipelines | More code, selector maintenance, QA, and compliance work |
Workflow
How the Naver Map review scraper works
The JSON export is the authoritative workflow definition. In plain English, the flow is:
Set Window Size -> Navigate -> Wait for Page Load -> Wait for body
-> Sleep -> Inject JavaScript scroll and expand loop
-> Wait for hidden review rows -> Structured Export -> Loop Continue
The sample Navigate block opens a mobile visitor-review URL for one Naver Place. Replace it with more direct review URLs for a multi-store batch. The JavaScript block scrolls, clicks common Korean and English more controls, detects review-like DOM or embedded data, and writes normalized values into hidden rows. Structured Export then appends those rows to CSV.
| Workflow stage | What it does | What to verify |
|---|---|---|
| Set Window Size | Uses a mobile-shaped browser viewport | The review page matches the mobile layout |
| Navigate | Opens each configured Naver Place visitor-review URL | URLs point to review pages, not search pages |
| Scroll and expand | Clicks more, expand, and full-view controls, then scrolls | Reviews visibly load before export |
| Hidden export rows | Normalizes detected review fields into stable attributes | Row count is greater than zero for accessible pages |
| Structured Export | Writes headers and appends to a local CSV | Filename and save folder are correct |
Runbook
How to scrape Naver Place reviews to CSV
Import the template
Open the Naver Map Review Scraper template, download the workflow JSON, and import it into UScraper.
Replace the sample URL
In Navigate, replace the sample m.place.naver.com visitor-review URL with one store page you are allowed to process. Keep the first test to one URL.
Confirm the export path
In Structured Export, set a project folder, keep headers enabled, and confirm the file name naver-map-review-scraper.csv. Append mode is useful for multi-store runs.
Run visibly
Let the browser load, scroll, and expand review content. Stop if you see CAPTCHA, login requirements, abnormal-access text, or a page that clearly does not match the intended store.
Validate the first rows
Open the CSV, compare several rows against the browser, check UTF-8 Korean text, inspect diagnostic values, and only then add more review URLs.
Use a dated filename or clear the previous CSV before reruns. Append mode is practical for store lists, but it can mix test rows with production rows during debugging.
Output
Naver review CSV export fields
The template exports one row per detected review. Store-level fields repeat on each row, which keeps combined multi-store files easy to filter, group, and join with other datasets from the UScraper template library.
| CSV group | Columns |
|---|---|
| Store context | 가게이름, 카테고리, 전체평점, 방문자리뷰, 블로그리뷰 |
| Reviewer signals | 리뷰작성자, 리뷰작성자링크, 리뷰작성수, 팔로워 |
| Review content | 첨부이미지, 리뷰내용, 이런_점이_좋아요, raw_review_text |
| Visit details | 방문시간, 방분횟수, 방문인증 |
| Audit trail | source_url |
Validation
Validate Naver reviews before analysis
Open the CSV beside the browser after the first run. Check rows from the top, middle, and bottom of the file. Sort by source_url, then scan 리뷰내용, 방문시간, and raw_review_text for repeated rows, diagnostic content, or broken Korean encoding.
| Symptom | Likely cause | Fix |
|---|---|---|
| Zero rows | Review page did not render, page was blocked, or selectors missed the layout | Rerun one visible URL, inspect the browser, and update waits or selectors |
| Diagnostic row | CAPTCHA, login wall, abnormal-access page, or no detectable review cards | Stop the batch and reduce scope |
| Garbled Korean text | Spreadsheet opened the CSV with the wrong encoding | Import as UTF-8 instead of double-clicking |
| Duplicate reviews | Same URL was run twice or append mode reused an old CSV | Dedupe by source_url, reviewer, visit date, and review text |
| Blank reviewer or date | Naver did not expose that field on the card | Treat blanks as unknown, not errors |
Keep an audit note with the source URL list, run date, template version, export folder, prompts seen, and selector edits.
Common issues
Troubleshooting Naver Map review exports
Confirm the URL is a visitor-review page, not the main place profile or a search result. Run visibly, wait for review cards, and check whether labels, class names, or lazy loading changed.
Browse more tutorials in the UScraper blog, or go straight to the Naver Map Review Scraper template when you are ready to import the workflow and run the first one-store validation.