Naver Blog Search Scraper 🔍

Search Naver Blog (네이버 블로그) by keyword and extract full post content, metadata, thumbnails, hashtags, and engagement metrics.

🚀 Quick Start (3 minutes)

1. Click "Try for free" on the Actor page
2. Enter your search keyword:

   {
     "queries": ["강남 맛집"],
     "maxResults": 20,
     "includeFullContent": true
   }
   

3. Click Start — blog posts with full text appear in the Dataset tab
4. Export as JSON, CSV, or Excel

Tip: Set sortBy: "date" to get the most recent posts first, or "relevance" for Naver's best matches.

✨ Features

• 🔍 Keyword Search — Search across all of Naver's blog ecosystem by any keyword
• 📄 Full Content — Extract complete blog post text (not just snippets)
• 📊 Rich Metadata — Publish date, author, thumbnails, hashtags, likes, comments
• ⚡ No Browser Needed — Direct HTTP + API calls, 10x faster and cheaper
• 🔄 Sort Options — Sort by relevance (관련도순) or date (최신순)
• 📦 Batch Queries — Process multiple search keywords in a single run
• 🛡️ Proxy Support — Built-in Apify Proxy integration for reliable scraping

🎯 Use Cases

• Content Marketing — Monitor blog coverage of your brand, products, or services over time
• SEO Research — Analyze top-ranking blog posts for target keywords to inform your content strategy
• Competitive Analysis — Track what bloggers write about your competitors and compare coverage volume
• Market Research — Discover consumer sentiment, trends, and preferences from blog posts
• Influencer Discovery — Find popular bloggers in specific niches by engagement metrics
• Academic Research — Collect Korean blog data for NLP, sentiment analysis, or topic modeling
• Trend Analysis — Track emerging topics and hashtag trends across the Naver blog ecosystem
• PR Monitoring — Get notified about new blog posts mentioning your brand by scheduling recurring runs

📊 Output Fields

Each blog post record includes:

Field	Type	Description	Example
rank	integer	Position in search results	1
title	string	Blog post title	"강남 맛집 추천 베스트 10"
blogId	string	Naver blog ID (part of URL)	"foodie_kim"
logNo	integer	Naver's internal post number	224133165158
url	string	Direct link to the full blog post	"https://blog.naver.com/..."
authorName	string	Blog author's display name	"김맛집의 블로그"
publishDate	string	Date and time the post was published	"2026. 1. 3. 22:09"
fullContent	string	Complete post text (when enabled)	"친구들과 오랜만에..."
contentLength	integer	Character count of the full post text	35290
thumbnailUrl	string	Main thumbnail image URL	"https://blogthumb..."
hashtags	array	Hashtags attached to the post	["강남맛집", "서울맛집"]
ogDescription	string	Open Graph / meta description of the post	"친구들과 오랜만에..."
sympathyCount	integer	Number of likes ("공감") on the post*	42
commentCount	integer	Number of comments*	15
shareCount	integer	Number of shares*	3
categoryName	string	Blog category assigned by the author*	"맛집 리뷰"
searchQuery	string	The keyword that found this post	"강남 맛집"

*Engagement and category fields are available when includeMetadata is enabled.

⚙️ Input Parameters

Parameter	Type	Default	Description
queries	string[]	—	Search keywords (e.g., ["강남 맛집", "제주 여행"])
query	string	—	Single search keyword (alternative)
maxResults	integer	30	Max posts per query (1–200)
sortBy	string	"relevance"	Sort: "relevance" (관련도순) or "date" (최신순)
includeFullContent	boolean	true	Extract complete blog post text (adds one request per post)
includeMetadata	boolean	true	Fetch likes, comments, shares, category via Naver Blog API
proxyConfiguration	object	—	Apify Proxy settings

Example Input

{
    "queries": ["강남 맛집", "서울 카페 추천"],
    "maxResults": 50,
    "sortBy": "date",
    "includeFullContent": true,
    "includeMetadata": true
}

⚠️ Limitations & Notes

• Max 200 posts per query — Naver's search pagination limits accessible results
• Full content extraction — Adds one HTTP request per post; disable includeFullContent for faster runs when only titles/metadata are needed
• Metadata enrichment — Adds one API call per post for engagement metrics; disable includeMetadata for speed
• Rate limiting — Automatic retry with exponential backoff on 429/5xx errors
• Some posts restricted — Private or member-only blog posts may not return full content
• No login required — All data comes from publicly accessible pages and APIs
• Content length — Full post text can be very long (30K+ characters); plan storage accordingly

⚡ How It Works

1. Search — Parses Naver blog search results (server-rendered HTML)
2. Extract — Fetches each blog post's full content via PostView API
3. Enrich — Gets engagement metrics (likes, comments, shares) from Naver Blog mobile API

No browser, no Selenium, no Playwright — just fast HTTP requests.

💰 Pricing

$0.50 per 1,000 blog posts — pay only for what you scrape. Platform usage costs are included at minimal cost.

🔗 Part of the Naver Place Suite

Combine with our other Korean data scrapers:

• Naver Place Search — Search places by keyword
• Naver Place Reviews — Visitor reviews with ratings
• Naver Place Blog Reviews — Place-specific blog reviews
• Naver Place Photos — Business & visitor photos

⚠️ Disclaimer

This Actor is provided for educational and research purposes. Please respect Naver's Terms of Service and use responsibly. The author is not responsible for any misuse of this tool.