Naver Blog & Cafe Scraper — Korean Word-of-Mouth Search avatar

Naver Blog & Cafe Scraper — Korean Word-of-Mouth Search

Pricing

from $4.00 / 1,000 posts

Go to Apify Store
Naver Blog & Cafe Scraper — Korean Word-of-Mouth Search

Naver Blog & Cafe Scraper — Korean Word-of-Mouth Search

Search Naver Blog (네이버 블로그) and Naver Cafe (네이버 카페) by keyword and get posts as clean JSON: title, snippet, author, blog/cafe name, post URL, publish date and thumbnail. Korea's word-of-mouth layer, for brand monitoring and PR tracking.

Pricing

from $4.00 / 1,000 posts

Rating

0.0

(0)

Developer

Seok June Park

Seok June Park

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

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:

FieldMeaning
sourcenaver_blog or naver_cafe
keyword, rankThe search term, and the post's position in those results
title, snippetPost title and the matched excerpt (search highlight markup stripped)
authorBlogger pen name (blog only — the cafe tab shows the cafe, not the member)
channel_name, channel_idBlog or cafe name, and its Naver ID
posted_atPublish date (YYYY-MM-DD)
is_sponsoredtrue when Naver flags the post as a paid/sponsored placement
url, thumbnail_url, post_id, scraped_atCanonical post link, thumbnail, id, KST timestamp

Input example

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

Output example (real row)

{
"source": "naver_blog",
"keyword": "성수동 카페",
"rank": 1,
"title": "[성수동 카페거리] 주말 웨이팅 필수 핫플레이스 동선과 주차 팁",
"snippet": "주말마다 힙한 에너지와 세련된 팝업스토어로 발 디딜 틈이 없는 곳…",
"author": "아파트럼프",
"channel_name": "아파트과 부도",
"channel_id": "10231sy",
"posted_at": "2026-07-02",
"url": "https://blog.naver.com/10231sy/224333861881"
}

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.