Retired 2026-09-15. Unpublished from the Apify Store: the source host disallows automated access (robots.txt) and the output carried identifiers of private bloggers. Kept here for reference only. The example below is fictional.

Naver Blog & Cafe Scraper — Korea's Word-of-Mouth Layer

Search Naver Blog (네이버 블로그) and Naver Cafe (네이버 카페) by keyword and get posts back as clean JSON/CSV: title, snippet, author, blog/cafe name, post URL, publish date and thumbnail.

Why this matters. In Korea, brand conversation does not happen on Twitter or Reddit — it happens on Naver blogs and in Naver cafes (community forums). If you are tracking a brand, a product launch, a restaurant or a neighbourhood in Korea, this is the layer where people actually talk.

What you get

One row per post:

Field	Meaning
source	naver_blog or naver_cafe
keyword, rank	The search term, and the post's position in those results
title, snippet	Post title and the matched excerpt (search highlight markup stripped)
author	Blogger pen name (blog only — the cafe tab shows the cafe, not the member)
channel_name, channel_id	Blog or cafe name, and its Naver ID
posted_at	Publish date (YYYY-MM-DD)
is_sponsored	true when Naver flags the post as a paid/sponsored placement
url, thumbnail_url, post_id, scraped_at	Canonical post link, thumbnail, id, KST timestamp. thumbnail_url is null on text-only posts (common when sorting by newest); snippet, channel_name and channel_id are null when Naver omits them from the result card.

Input example

{
  "keyword": "성수동 카페",
  "source": "both",
  "sort": "sim",
  "maxItems": 60
}

Output example (real row)

{
  "source": "naver_blog",
  "keyword": "성수동 카페",
  "rank": 1,
  "post_id": "000000000001",
  "title": "[예시] 성수동 카페 방문 후기",
  "snippet": "예시 문구입니다. 실제 게시물이 아닌 형식 설명용 데이터입니다.",
  "author": "example_author",
  "channel_name": "example blog",
  "channel_id": "example-blog",
  "posted_at": "2026-08-01",
  "is_sponsored": null,
  "url": "https://blog.naver.com/example-blog/000000000001",
  "thumbnail_url": null,
  "scraped_at": "2026-08-01T10:00:00+09:00"
}

Coverage and honest limits

• Blog reads Naver's own blog-section search API. It reports the match count (commonly ~1,000 for a broad keyword) and paginates cleanly, so maxItems up to 1,000 is real.
• Cafe reads Naver's mobile cafe search tab, which serves about 30 posts per keyword — Naver publishes no deeper public cafe search. Asking for more will not invent results.
• Naver shows a publish date on only some cafe cards, so posted_at is null for the rest. It is left null rather than guessed.
• author is blog-only by design: the cafe result card identifies the cafe, not the individual member.
• If a requested source returns nothing, the run warns and records it in an EMPTY_SOURCES key-value record instead of finishing quietly.

Privacy

Only public search results are collected — no login, no private cafe content, no member profiles. author and channel_name are the public pen name and blog/cafe name Naver itself prints on the result card.