Naver Blog Scraper — Sponsored Ad Detector + Keyword Volume

Scrape Naver Blog (네이버 블로그) — Korea's dominant blogging platform — by keyword or post URL, and get three things no generic scraper gives you:

1. Full posts — title, body text, hashtags, image count, blogger, date
2. 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
3. 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.

Free plan vs paid plan

	Apify free plan	Any paid Apify plan
Keywords per run	1 (the rest are counted as not searched)	Up to 10
post rows (full body, tags, sponsored/authentic verdict)	10 a run (keyword posts and direct URLs together)	Up to maxPostsPerKeyword per keyword (1,000 max)
keyword-stats rows	1 (your keyword's own volume row)	Your keyword plus up to 29 related keywords
blogger ranking rows	1 (the top blogger)	Up to 20 per keyword
Locked rows	Counted exactly in a final free-plan-preview row and status message (posts, keyword-volume rows and bloggers held back, with their list price)	Nothing locked
Price per event	List price	Bronze 20% off · Silver 35% off · Gold and above 48% off

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 and are not charged — with one exception that is a result you asked for: a target verdict (no-results: the search completed and Naver has no posts for the keyword; post-unavailable: Naver answered that a direct post URL is deleted, private or blocked — 403/404/410/429). Those are charged once as target-verdict only when that event is on the Actor's price list. A fetch that did not finish on our side (timeout, network error, Naver 5xx) is reported as post-fetch-failed and never charged; so are search-failed and keyword-stats-failed.

Input

{
    "keywords": ["제주도 맛집", "강남 피부과"],
    "maxPostsPerKeyword": 100,
    "sort": "sim",
    "fetchContent": true,
    "includeKeywordStats": true,
    "includeBloggerStats": true
}

• keywords — up to 10 per run; each returns up to 1,000 posts
• postUrls — scrape specific posts directly (blog.naver.com/{blogId}/{logNo})
• fetchContent: false — faster metadata-only run (classifier then sees title + snippet only)
• sort — sim (relevance) or date (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). target-verdict ($0.004, the post rate) is billed per completed target verdict row (see above) once that event is on the price list. Other status/notice rows are free. Each billable row is delivered first and charged right after; when your run's maximum cost is reached the run stops before the next billable row and ends SUCCEEDED.

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.

Until target-verdict is on the price list, a keyword where Naver returns nothing is not charged beyond the run start fee. Once it is, that completed empty answer is billed once as target-verdict.

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 post-unavailable status rows (billed as target-verdict only once that event is on the price list)
• 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, not sponsored
• Comment threads are not collected in this version

Works well with

• coupang-review-intelligence — Turn the same keyword into real buyer reviews and a product verdict from Coupang.
• lighthouse-website-audit — Score the landing page you are driving that Naver traffic to.

Every run of this Actor also returns these suggestions in the nextSteps field of its summary row.

Leave a review

A short review on the Reviews tab, good or bad, helps other people find this Actor and tells us what to build next. Found a bug or need a feature? Open an issue on the Issues tab and we'll look into it.