🗺️ Naver Map Scraper: Places, Reviews & Blog Posts (No Login)

Scrape Naver Map (네이버 지도) and Naver Place (네이버 플레이스), Korea's main local search: search places the way a Korean user does, get name, category, phone, address, coordinates, rating and review counts, then add every visitor review of each place and the Naver Blog reviews Naver links to it. A second mode searches Naver Blog posts by keyword. No login, no cookies, no browser. Export to JSON/CSV/Excel, run on a schedule, call via API, or connect to Make, Zapier or n8n.

What a run costs: one price per saved row (a place, a review or a blog post). From 8 November 2026: $0.001 on the Free plan, $0.0009 on Bronze, $0.00085 on Silver, $0.0008 on Gold and above, so 1,000 reviews cost $1 or less. Until then the Actor's earlier price of $0.0025 a row still applies (Apify needs 14 days for a price change). Plus $0.00005 per run; a search without results costs nothing beyond the start.

🔎 What is the Naver Map Scraper?

Google Maps barely covers Korea; Koreans look up restaurants, clinics, salons and hotels on Naver. This Actor reads Naver Place's own data calls, so it returns what the Naver Map app shows, in Korean (or Naver's English where it exists).

What data does it extract?

• Places: place id, name, category, business type, phone (incl. Naver's 0507 virtual numbers), road and lot address, area, latitude/longitude, visitor rating, visitor and blog review counts, saves, open now status, amenities (예약, 주차, 포장…), one-line summary, booking and Naver Pay flags, image, Naver Map link, search rank.
• Visitor reviews (방문자 리뷰): review id, stars, full text, visit date, receipt/payment verification, visit count, ordered menu item, voted keywords (음식이 맛있어요…), owner reply, photo links, reviewer nickname.
• Blog reviews of a place (블로그 리뷰): blog or cafe post title, text preview, link, blog name, date, thumbnail.
• Naver Blog search: title, snippet, post link, blog id, post number, blog name, author nickname, publish time, thumbnails, rank.

What users of other Naver Actors report, and what this one does

Reported elsewhere	Here
Review pagination returns the same reviews again	Reviews are paged with Naver's own cursor: 1,656 of 1,656 reviews of one restaurant in 35 calls, none twice
Request failures and skipped keywords	Failed calls are asked again and move to another proxy route; a keyword is only reported empty when Naver says so
Places, reviews and blog posts need three Actors	One run does all three, and each row says its type
4 GB browser runs	Plain HTTP at 256 MB

⬇️ Input

Field	What it does
searchQueries	Searches as typed into Naver Map, e.g. 강남역 맛집, 부산 호텔. Up to 300 places each.
placeUrls	Naver Map / Place links or bare ids, for places you already know.
maxPlacesPerQuery	Places per search (1 to 300, default 20).
latitude, longitude	Optional search center; places are ranked from there.
visitorReviewsPerPlace	Visitor reviews per place, newest first (0 = none).
blogReviewsPerPlace	Blog/cafe reviews per place (0 = none, Naver links about 110 at most).
reviewsSince	Skip reviews older than this day (YYYY-MM-DD).
blogKeywords	Naver Blog keyword searches, up to 1,000 posts each.
maxPostsPerKeyword, blogSort, blogStartDate, blogEndDate	Depth, order (relevance or newest) and date range of the blog search.
language	ko (default) or en.

Example input

{
  "searchQueries": ["강남역 맛집", "성수동 카페"],
  "maxPlacesPerQuery": 50,
  "visitorReviewsPerPlace": 100,
  "blogReviewsPerPlace": 10,
  "reviewsSince": "2026-01-01",
  "blogKeywords": ["성수동 카페"],
  "maxPostsPerKeyword": 100
}

⬆️ Output

{
  "type": "place",
  "placeId": "31110991",
  "name": "닭갈비전 강남점",
  "category": "닭갈비",
  "businessType": "restaurant",
  "phone": "0507-1402-1568",
  "roadAddress": "서초대로73길 54 강남디오빌 2층 닭갈비전",
  "fullAddress": "서울특별시 서초구 서초동 1309-1 강남디오빌 2층 닭갈비전",
  "latitude": 37.5020765,
  "longitude": 127.023964,
  "visitorReviewCount": 1806,
  "visitorReviewScore": 4.88,
  "blogReviewCount": 1457,
  "openStatus": "영업 전",
  "options": ["예약", "포장", "주차"],
  "placeUrl": "https://map.naver.com/p/entry/place/31110991",
  "searchQuery": "강남역 맛집",
  "rank": 1
}

{
  "type": "visitorReview",
  "placeId": "1000404935",
  "placeName": "도래집 강남점",
  "reviewId": "6addec72d23dab7ffba3e7d2",
  "rating": 5,
  "text": "양도 푸짐하고 도래창 처음 먹어보는데 … 정말 맛있었습니다",
  "visitedAt": "2026-10-25T11:13:09.000Z",
  "verifiedBy": "영수증",
  "menuItem": "도래창+소금막창se",
  "keywords": ["음식이 맛있어요", "친절해요"],
  "ownerReply": null,
  "imageUrls": ["https://pup-review-phinf.pstatic.net/…"],
  "authorNickname": "…"
}

blogReview rows carry title, text, url, blogName, publishedAt; blogPost rows carry keyword, rank, title, snippet, url, blogId, logNo, blogName, publishedAt, thumbnailUrls. Every row has scrapedAt.

🤖 For AI agents

Copy this input; every field is optional and no credential is needed:

{"searchQueries": ["홍대 카페"], "maxPlacesPerQuery": 10, "visitorReviewsPerPlace": 20}

Filter rows by type (place, visitorReview, blogReview, blogPost).

💡 Use cases

• 📍 Korean local lead lists: clinics, salons, academies or restaurants of a district with phone and address.
• ⭐ Review monitoring: a weekly run with reviewsSince returns only new reviews and owner replies of your or your competitors' places.
• 📊 Market research: ratings, review counts and voted keywords across a category and area.
• 📝 Influencer and content research: which bloggers write about a place or a keyword, and when.

⚠️ Limits

• Naver shows at most 300 places per search and 1,000 blog posts per keyword. Split a city into districts (강남구 치과, 서초구 치과) for more.
• Naver links about 110 blog reviews to a place, whatever its blog review count says.
• reviewsSince uses the visit date, which Naver sorts nearly but not exactly in order; the list ends after two pages with no newer review.
• Visitor review dates are visit dates; Naver gives visitors no exact posting time.
• Reviewer nicknames are the public names Naver shows; no profile or contact data of reviewers is collected.

❓ FAQ

Do I need a Naver account or API key? No. The Actor reads what any logged-out visitor sees.

Why Korean search words? Naver ranks places by Korean text. English words work for some places; Korean gives full results.

Can I get all reviews of one place? Yes: put its link into placeUrls and set visitorReviewsPerPlace to its review count.

How fast is it? On our test server 61 places with 1,209 reviews, 105 blog reviews and 40 blog posts took 25 seconds.

Does a place found by two searches cost twice? No, each place, review and post is saved once per run.

What happens on a timeout or a spending limit? The run stops in time, keeps its rows and says so; run it again with the same input to continue without paying twice.

Can I get menus with prices or opening hours per day? Not in this version; the place row has the open-now status and description.

Is it legal? It collects public business listings and public reviews. You are responsible for how you use them: follow Korea's PIPA, GDPR where it applies, and Naver's terms, and do not use reviewer nicknames for contact or profiling.

🔗 You might also like

• Google Maps Business Scraper
• Google Maps Email Scraper
• Bilibili Scraper

Keywords: naver map scraper, naver place scraper, 네이버 지도 크롤링, 네이버 플레이스 리뷰, naver place reviews, naver blog scraper, 네이버 블로그 크롤러, korean business data, korea local leads, naver visitor reviews, naver map api, korean restaurant data, naver blog search api, south korea places, naver review monitoring