Naver Blog Scraper — Sponsored Ad Detector + Keyword Volume
Pricing
Pay per event
Naver Blog Scraper — Sponsored Ad Detector + Keyword Volume
Scrape Naver Blog posts by keyword: full content, tags, sponsored-vs-내돈내산 ad detection, monthly keyword search volume and blogger rankings. Korean-native classifier. Unofficial tool, not affiliated with Naver.
Pricing
Pay per event
Rating
0.0
(0)
Developer
daehwan kim
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Scrape Naver Blog (네이버 블로그) — Korea's dominant blogging platform — by keyword or post URL, and get three things no generic scraper gives you:
- Full posts — title, body text, hashtags, image count, blogger, date
- Sponsored-ad detection (협찬/내돈내산 분류) — a Korean-native classifier flags whether each post is a paid/sponsored review or an authentic "bought it with my own money" (내돈내산) post
- Keyword search volume — monthly PC/mobile search counts, average clicks and competition level for your keyword and its related keywords, plus a blogger ranking for each keyword
Built by a Korean team. Korean marketing content lives and dies by the sponsored/authentic distinction — this Actor reads the actual Korean disclosure phrasing (소정의 원고료, 업체로부터 제공, 체험단, 내돈내산 …), not just metadata.
Unofficial tool. This Actor is not affiliated with, endorsed by, or sponsored by Naver Corporation. It collects only publicly accessible posts — no login, no private data.
What you get (row types)
Every run returns one flat dataset. Filter by rowType:
post — one row per blog post
| Field | Description |
|---|---|
keyword | The search keyword that found this post (null for direct URLs) |
postTitle | Post title |
url | Post URL |
blogId / logNo | Naver identifiers |
bloggerName / blogUrl | Author |
postDate | Publication date (YYYY-MM-DD) |
snippet | Search-result summary |
sponsoredVerdict | sponsored | authentic | unknown |
sponsoredSignals | Which disclosure phrases matched (e.g. ["협찬", "체험단"]) |
authenticSignals | Which authenticity phrases matched (e.g. ["내돈내산"]) |
contentStatus | ok | skipped | unavailable | http_403 … — how the content fetch went |
content | Full body text (up to 20,000 chars) |
contentLength | Full body length in characters |
tags | Hashtags found in the post |
imageCount / videoCount | Media counts |
keyword-stats — monthly search volume (per keyword, incl. related keywords)
| Field | Description |
|---|---|
inputKeyword | Your keyword |
keyword | This row's keyword (your keyword or a related one) |
isInputKeyword | true on the row for your exact keyword |
monthlySearchesPc / monthlySearchesMobile / monthlySearchesTotal | Monthly Naver search counts |
under10Flag | true when Naver reports "fewer than 10" (value shown as 5) |
monthlyAvgClicksPc / monthlyAvgClicksMobile | Average monthly ad clicks |
competition | Naver's competition level: 낮음 / 중간 / 높음 |
blogger — who owns this keyword (per keyword, top 20)
| Field | Description |
|---|---|
keyword / rank | Keyword and rank by post count |
blogId / bloggerName / blogUrl | The blogger |
postCount | Posts by this blogger in the collected set |
sponsoredCount / authenticCount / sponsoredRatio | How much of their output is sponsored |
latestPostDate | Most recent post in the set |
Status rows (noticeCode + message) explain anything that could not be collected — a deleted post, an unavailable keyword — and are never charged.
Input
{"keywords": ["제주도 맛집", "강남 피부과"],"maxPostsPerKeyword": 100,"sort": "sim","fetchContent": true,"includeKeywordStats": true,"includeBloggerStats": true}
keywords— up to 10 per run; each returns up to 1,000 postspostUrls— scrape specific posts directly (blog.naver.com/{blogId}/{logNo})fetchContent: false— faster metadata-only run (classifier then sees title + snippet only)sort—sim(relevance) ordate(newest first)
Use cases
- Sponsored-review auditing — separate paid placements from authentic reviews for any brand, product or place keyword
- Influencer discovery — the blogger ranking shows who dominates a keyword and how sponsored their output is
- Korean SEO & content planning — real monthly search volume and competition per keyword, straight from Naver's data
- Brand monitoring — track what Korean consumers write about you, with full text for sentiment analysis
- Market research — Naver Blog is where Korean purchase research happens; this is that data, structured
Pricing
Pay per event: a small per-run start fee, then per delivered row — post, keyword-stats and blogger rows are billed at their own rates (see the Pricing tab). Status/notice rows are free. Free-plan runs return up to 25 rows, prioritising the highest-value rows (keyword volume → blogger ranking → posts).
What a run actually costs. One keyword on default settings returned 25 billable rows — 10 keyword-stats, 10 post, 5 blogger — for $0.151. Ten keywords in one run land near $1.50. Rows scale with what you ask for: raise maxPostsPerKeyword and you pay for the extra posts, nothing else. Exact per-row rates are on the Pricing tab.
Status/notice rows are never billed. That includes runs where Naver returns nothing for a keyword — you are not charged for an empty answer.
Fair collection
- Only publicly accessible posts — no login, no captcha bypass, no private cafes
- Post pages are fetched with an honest bot User-Agent and polite concurrency
- Deleted/private posts are reported as status rows and not charged
- Personal data: rows contain only what the blogger publicly displays (public nickname, public blog URL). Use downstream in compliance with applicable law (e.g. PIPA, GDPR); you are the controller of what you do with the data.
Limitations
- Naver search pagination tops out at 1,000 posts per keyword
- The sponsored classifier reads visible text; a sponsored post with no disclosure text anywhere is classified
unknown, notsponsored - Comment threads are not collected in this version