Naver Blog & Cafe Scraper
Pricing
from $4.00 / 1,000 results
Go to Apify Store
Naver Blog & Cafe Scraper
Scrapes Naver Blog and Cafe posts with full content, comments, metadata, and engagement metrics. Supports keyword search and direct URL scraping.
Pricing
from $4.00 / 1,000 results
Rating
0.0
(0)
Developer
OrbitData Labs
Maintained by CommunityActor stats
1
Bookmarked
441
Total users
102
Monthly active users
3 hours ago
Last modified
Categories
Share
An Apify actor that scrapes posts, comments, place information, and metadata from Naver Blog and Cafe.
Features
- Keyword Search: Search blog/cafe posts using the Naver Search API
- Direct URL Scraping: Provide specific Naver Blog or Cafe post URLs for detailed scraping
- Blog & Cafe Listing: Provide a blog home URL, or a cafe home or board URL, to collect its most recent posts
- Sponsorship Detection: Flag posts that disclose sponsorship (협찬, 체험단, 원고료) or affiliate commissions, and posts that claim to be self-paid (내돈내산)
- Search Keyword & Rank: Every keyword-search row records which keyword found it and its position in Naver's results
- Date Range: Keep only posts published within a date range (
dateFrom/dateTo, e.g.2026-09-01or7 days) - Full Content Extraction: Extract complete text and HTML content from posts
- Image Collection: Collect all image URLs embedded in posts
- Place/Map Data: Extract place names, addresses, phone numbers, and GPS coordinates from posts
- External Link Extraction: Collect external link card data (OG links) embedded in posts
- Comment Scraping: Collect full comment data (author, content, date, replies) from both blog and cafe posts
- Engagement Metrics: Collect like/sympathy counts
- Video Detection: Detect whether a post contains video content
- Metadata: Author, date, category, tags, and more
Output Data
| Field | Type | Description |
|---|---|---|
type | string | blog or cafe |
title | string | Post title |
url | string | Post URL |
author | string | Author name |
date | string | Published date |
content | string | Full text content |
contentHtml | string | Raw HTML content |
images | string[] | List of image URLs |
tags | string[] | Hashtags/tags |
category | string | Blog category, or the cafe board the post was written in |
likeCount | number | Number of likes/sympathies |
commentCount | number | Number of comments |
viewCount | number | Number of views (cafe posts only; Naver does not publish blog view counts) |
comments | object[] | Comment data (author, content, date, isReply, profileImage). Cafe comments also carry id, parentId (the comment a reply answers), isArticleWriter and isCleanBotFiltered |
places | object[] | Place info from map embeds (name, address, phone, category, latitude, longitude) — blog and cafe posts |
externalLinks | object[] | External links (title, description, URL) |
hasVideo | boolean | Whether the post contains video |
cafeName | string | Cafe name (cafe posts only) |
cafeUrl | string | Cafe URL (cafe posts only) |
keyword | string | Search keyword that produced the row (keyword search only) |
searchRank | number | Position in Naver's search results for keyword (1 = top) |
sponsored | boolean | The post text discloses a sponsorship (products, services, fees or discounts received) |
affiliate | boolean | The post text discloses an affiliate commission (Coupang Partners, Naver Connect, ...) |
disclosureText | string | The sentence that triggered sponsored/affiliate |
selfPaidClaim | boolean | The post claims to be self-paid (내돈내산) and discloses no sponsorship |
scrapedAt | string | Scrape timestamp (ISO 8601) |
Usage
Enter keywords to search Naver Blog/Cafe, or provide direct URLs to scrape specific posts. No separate API key setup is required — just run the actor.
Input Example
{"searchKeywords": ["best restaurants", "Seoul cafe"],"directUrls": ["https://blog.naver.com/example/123456"],"searchType": "both","maxResults": 30,"sortBy": "sim","scrapeContent": true,"scrapeComments": true,"maxConcurrency": 5}
Input Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
searchKeywords | string[] | [] | List of search keywords |
directUrls | string[] | [] | Post URLs to scrape, or blog/cafe home URLs to list (e.g. https://blog.naver.com/<blogId>, https://cafe.naver.com/<cafe>, https://cafe.naver.com/f-e/cafes/<id>/menus/<boardId>) |
searchType | string | both | Search target: blog, cafe, or both |
maxResults | number | 30 | Max search results per keyword, and max posts per listed blog/cafe/board (up to 1000) |
sortBy | string | sim | Sort order: sim (relevance) or date (newest first) |
dateFrom | string | — | Keep posts published on or after this day (KST): YYYY-MM-DD or a period back from today such as 7 days |
dateTo | string | — | Keep posts published on or before this day (KST), same formats |
scrapeContent | boolean | true | Whether to scrape full post content |
scrapeComments | boolean | true | Whether to collect comment data |
skipMembersOnlyPosts | boolean | false | Leave out members-only cafe posts (no body) and fill maxResults with readable posts instead. Applies to keyword searches and cafe home/board URLs |
maxConcurrency | number | 5 | Max concurrent scraping requests |
Output Example
{"type": "blog","title": "Top 10 Restaurants in Gangnam, Seoul","url": "https://blog.naver.com/foodie123/223456789","author": "FoodExplorer","authorLink": "https://blog.naver.com/foodie123","date": "2025-01-15","content": "Hello! Today I'm introducing must-visit restaurants in Gangnam...","images": ["https://blogfiles.pstatic.net/..."],"tags": ["GangnamFood", "SeoulRestaurant", "FoodRecommendation"],"category": "Food/Travel","likeCount": 142,"commentCount": 23,"places": [{"name": "Restaurant ABC","address": "123 Yeoksam-dong, Gangnam-gu, Seoul","tel": "02-1234-5678","category": "Restaurant","latitude": "37.5012","longitude": "127.0396"}],"externalLinks": [{"title": "Reservation Page","description": "Book online","url": "https://example.com/reservation"}],"hasVideo": false,"comments": [{"author": "user123","content": "Great post! Very helpful.","date": "2025-01-16","isReply": false,"profileImage": "https://..."}],"scrapedAt": "2025-01-20T10:30:00.000Z"}
Use Cases
- Market Research: Analyze consumer reviews and place data for specific keywords or products
- Trend Analysis: Track popular topics and keywords over time
- Restaurant/Place Collection: Automatically extract place names, addresses, phone numbers, and GPS coordinates from blog reviews
- Competitor Analysis: Monitor online sentiment about competing brands
- Influencer Discovery: Find influential bloggers in specific niches
- Content Analysis: Analyze patterns of images, videos, and external links in posts
Limitations
- Naver Search API daily limit: 25,000 calls
- Max search results per keyword: 1,000. Naver's search API counts other blog platforms (tistory, etc.) toward its 1,000 results, which this actor filters out; when that leaves fewer Naver blog posts than
maxResults, the rest are taken from Naver's blog search (Naver posts only) and ranked after the API's results - Private cafe posts cannot be scraped. Members-only posts (listed from a cafe, or given as direct URLs) come back with title, author, date and counts only (no body); the run log and
SUMMARY.restrictedCafePostsreport how many. SetskipMembersOnlyPoststo get readable posts instead - The date range applies to keyword searches and blog/cafe listings, not to individual post URLs. Cafe search results carry no date, so they are filtered after scraping and can number fewer than
maxResults - Sponsorship detection reads the post text only: a disclosure posted only as an image banner is not detected, so
sponsored: falsemeans no disclosure was found in the text, not that the post is organic - Blog comments may not be available for some posts due to Naver's access restrictions
- Some content may be restricted due to Naver's access control policies
License
ISC S