Naver Blog Search Scraper

What does Naver Blog Search Scraper do?

Naver Blog Search Scraper is a Naver Blog search API alternative that collects public post cards from the current Naver Blog search. Enter one Korean or international keyword, or submit a small batch of queries, and the Actor returns structured posts with stable blog/post identifiers, ranking, title, snippet, blog attribution, publication label, thumbnail, and provenance. It does not open private posts, bypass login, or extract hidden account data.

Why scrape Naver Blog search?

• Monitor Korean consumer conversations and creator coverage.
• Research brand, product, destination, and technology mentions.
• Build public-content discovery, SEO, and trend-monitoring workflows.
• Schedule recurring runs and export results through Apify datasets, webhooks, integrations, or API calls.

The Actor uses Naver's current Blog-tab route, stops on repeated pages, enforces item and page limits, deduplicates stable post IDs, and detects access challenges instead of storing them as results.

What data can it extract?

Field	Type	Description
id	string	Stable query-ranking ID; postKey remains stable across queries
postId, blogId	string	Public identifiers from the canonical post URL
title, snippet	string	Public search-card title and summary
url, blogUrl	string	Canonical post and blog URLs
blogName	string	Public blog display name when shown
authorName	string	Public author or creator display name shown by Naver
authorUrl	string	Public author profile URL shown by Naver
dateRaw, publishedAt	string	Source label and normalized Korean date when parseable
thumbnailUrl	string	Search-card thumbnail when available
queryPosition, page	integer	Query-relative rank and result page
query, searchUrl, scrapedAt	string	Search and scrape provenance

Unavailable optional values are omitted rather than replaced with N/A, zeroes, or fabricated placeholders.

How to scrape Naver Blog

1. Open the Actor input tab.
2. Enter query, or provide several values in queries.
3. Set maxItems and maxPages to bound the run.
4. Leave concurrency low for reliable Naver access.
5. Enable an authorized Apify Proxy only when direct access is blocked.
6. Run the Actor and inspect the dataset Output tab.

{
  "query": "인공지능",
  "maxItems": 10,
  "maxPages": 2,
  "maxConcurrency": 1,
  "proxyConfiguration": { "useApifyProxy": false }
}

Output

The default dataset contains one item per query-specific post ranking. You can download it as JSON, CSV, Excel, HTML, XML, or RSS, or access it through the Apify API.

{
  "id": "naver-blog:example:12345:q:%EC%9D%B8%EA%B3%B5%EC%A7%80%EB%8A%A5",
  "postKey": "example:12345",
  "postId": "12345",
  "blogId": "example",
  "queryPosition": 1,
  "page": 1,
  "title": "Public Naver Blog post title",
  "url": "https://blog.naver.com/example/12345",
  "blogName": "Example blog",
  "authorName": "Example author",
  "authorUrl": "https://in.naver.com/example",
  "query": "인공지능",
  "sourceDomain": "search.naver.com"
}

Cost and performance tips

Cost depends on browser runtime, selected memory, and proxy traffic. Start with 5–10 items and one page. Increase limits only after verifying the query. The Actor blocks media/font downloads, uses bounded retries, and stops pagination when pages repeat or the requested quota is reached.

Legal, privacy, and support

Use the Actor only for public information and comply with Naver's terms, robots directives, and applicable privacy law. Public posts can still contain personal data; process it only with a legitimate basis. Challenge or CAPTCHA pages are never saved as records. For help, use the Actor's Issues tab; for programmatic runs, use its API tab.