# Naver Blog, Cafe & News Search Scraper 네이버 블로그·카페·뉴스 (`elabstudio/naver-blog-cafe-news-scraper`) Actor

Search Naver Blog, Naver Cafe and Naver News by keyword and get titles, URLs, snippets, authors, ISO dates and thumbnails for trend, brand and market research.

- **URL**: https://apify.com/elabstudio/naver-blog-cafe-news-scraper.md
- **Developed by:** [E:LAB STUDIO](https://apify.com/elabstudio) (community)
- **Categories:** Social media, News
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.40 / 1,000 search results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Naver Blog, Cafe & News Search Scraper (네이버 블로그·카페·뉴스 검색)

Search **Naver Blog, Naver Cafe and Naver News** by keyword and get every result as clean JSON / CSV / Excel: title, URL, snippet, blog or cafe name or news publisher, **publish date as ISO 8601**, and thumbnail. Results link back to the original post or article; the actor does not copy post or article bodies.

Naver is South Korea's #1 search engine. Its blogs and cafes (forums) are where Korean consumers write reviews, ask for recommendations and complain, so this is the place to listen to the Korean market.

- English field names, one schema for all three sources
- Relative dates (`3시간 전`, `1일 전`, `어제`) converted to real timestamps in Korea time
- Ads (파워컨텐츠) removed, ranks kept
- Sort by relevance or newest, filter by period or custom date range
- No login, no API key, no browser: fast and cheap

### What you can use it for

- **Brand and product monitoring**: what Korean bloggers and cafe members say about your product or competitors.
- **Trend and buzz tracking**: count how often a product, brand or topic shows up in Korean blogs, cafes and news over time.
- **Influencer discovery**: find the blogs that rank for your keywords and their posting dates.
- **News tracking**: Korean press coverage of a company, person or topic, with publisher and original link.
- **Market research**: volume of posts over time for a keyword, trending topics, consumer questions in cafes.

### Input

| Field | Example | Notes |
|---|---|---|
| `keywords` | `["무선 이어폰", "갤럭시 버즈"]` | Search terms. Korean works best; English brand names work too. |
| `sources` | `["blog", "cafe", "news"]` | Any combination. |
| `maxItemsPerKeyword` | `100` | Per keyword **and** per source. Naver shows up to ~1,000 results per query. |
| `sort` | `relevance` / `date` | Newest first with `date`. |
| `period` | `all`, `day`, `week`, `month`, `6months`, `year` | Quick time filter. |
| `dateFrom` / `dateTo` | `2026-01-01` / `2026-03-31` | Custom range (overrides `period`). |
| `maxConcurrency` | `4` | Parallel searches. |
| `proxyConfiguration` | `{ "useApifyProxy": false }` | Usually not needed. |

Example: the newest 200 blog posts about a product in the past month

```json
{ "keywords": ["갤럭시 버즈"], "sources": ["blog"], "maxItemsPerKeyword": 200, "sort": "date", "period": "month" }
```

Example: Korean news coverage of a company in Q1

```json
{ "keywords": ["삼성전자 반도체"], "sources": ["news"], "dateFrom": "2026-01-01", "dateTo": "2026-03-31", "maxItemsPerKeyword": 500 }
```

### Output example

Blog post:

```json
{
  "keyword": "무선 이어폰",
  "source": "blog",
  "rank": 1,
  "title": "가성비 무선 이어폰 추천, 앤커 사운드코어 P31i 후기",
  "url": "https://blog.naver.com/mobano/224382485186",
  "snippet": "이 무선 이어폰은 3만 9천9백 원에 판매 중(네이버 스토어 기준)인데요...",
  "authorName": "모바노",
  "authorUrl": "https://in.naver.com/mobano",
  "publishedAt": "2026-08-19T09:00:00+09:00",
  "dateRaw": "2026.08.19.",
  "thumbnailUrl": "http://blogfiles.naver.net/MjAyNjA4MThfMjEx/.../resize_DSC_4111.jpg",
  "scrapedAt": "2026-11-09T04:39:09.478Z"
}
```

News article:

```json
{
  "keyword": "무선 이어폰",
  "source": "news",
  "rank": 1,
  "title": "강아지와 뛰어도 안 빠져…삼성 첫 '귀에 거는 이어폰' 버즈 온 [써보니]",
  "url": "https://n.news.naver.com/mnews/article/031/0001073124?sid=105",
  "snippet": "삼성전자가 지난달 27일 출시한 '갤럭시 버즈 온'은 갤럭시 버즈 최초의 클립형 무선 이어폰이다...",
  "authorName": "아이뉴스24",
  "authorUrl": "https://media.naver.com/press/031",
  "publishedAt": "2026-11-08T09:01:12+09:00",
  "dateRaw": "1일 전",
  "thumbnailUrl": "https://imgnews.pstatic.net/image/origin/031/2026/11/08/1073124.jpg",
  "originalUrl": "http://www.inews24.com/view/2023721",
  "naverNewsUrl": "https://n.news.naver.com/mnews/article/031/0001073124?sid=105",
  "reporter": "권서아 기자"
}
```

Cafe post:

```json
{
  "keyword": "무선 이어폰",
  "source": "cafe",
  "rank": 1,
  "title": "귀통증 없는 무선이어폰 추천 부탁드려요.",
  "url": "https://cafe.naver.com/ranceali/109103",
  "snippet": "현재 에어팟을 쓰고 있는데 수명이 다되어 알리에서 판매하는 이어폰으로 구매하려 합니다...",
  "authorName": "랑스알리",
  "authorUrl": "https://cafe.naver.com/ranceali",
  "publishedAt": "2026-11-03T13:38:00+09:00",
  "dateRaw": "6일 전"
}
```

### Pricing

Pay per result:

- **$0.40 per 1,000 search results** (title, URL, snippet, author, date, thumbnail)

So 1,000 results cost $0.40. You can set a maximum cost per run in Apify and the actor stops when it is reached.

### FAQ

**Do I need a Naver account or API key?** No. The actor reads Naver's public search pages, like a logged-out visitor.

**Does it return the full post text?** No. To respect authors' and publishers' copyright, the actor returns search-listing data only (title, snippet, author, date, link). Open the URL to read the post.

**How accurate are dates?** Naver shows recent posts as "3시간 전" (3 hours ago). The actor converts these to a timestamp at scrape time, so they are accurate to the unit shown (minutes, hours, days).

**How many results can I get?** Naver lists up to roughly 1,000 results per query and source. For more, split the query (add words) or use date ranges.

**Is it legal?** The actor collects publicly visible search results only. You are responsible for how you use the data, including personal data and copyright rules in your country.

**Something broke?** Naver changes its layout from time to time. Open an issue on the actor page and it will be fixed quickly.

# Actor input Schema

## `keywords` (type: `array`):

One or more search terms, as you would type them on naver.com. Korean works best (e.g. 무선 이어폰, 강남 맛집), English brand names also work.

## `sources` (type: `array`):

Which Naver search tabs to scrape.

## `maxItemsPerKeyword` (type: `integer`):

Stop after this many results for each keyword in each source. Naver usually returns up to about 1,000 results per query. 0 = as many as possible (capped at 1,000).

## `sort` (type: `string`):

Relevance (Naver default) or newest first.

## `period` (type: `string`):

Only return posts published in this period. Ignored when a custom date range is set.

## `dateFrom` (type: `string`):

Custom range start, YYYY-MM-DD (Korea time).

## `dateTo` (type: `string`):

Custom range end, YYYY-MM-DD (Korea time). Empty = today.

## `maxConcurrency` (type: `integer`):

How many keyword/source searches run at the same time. Keep it low to stay polite.

## `proxyConfiguration` (type: `object`):

Not needed in most cases. Enable if you run very large jobs and start seeing blocks.

## Actor input object example

```json
{
  "keywords": [
    "무선 이어폰",
    "갤럭시 버즈"
  ],
  "sources": [
    "blog",
    "cafe",
    "news"
  ],
  "maxItemsPerKeyword": 20,
  "sort": "relevance",
  "period": "all",
  "maxConcurrency": 4,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Search results with title, URL, snippet, author, ISO date and thumbnail.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "무선 이어폰"
    ],
    "sources": [
        "blog",
        "cafe",
        "news"
    ],
    "maxItemsPerKeyword": 20,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("elabstudio/naver-blog-cafe-news-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": ["무선 이어폰"],
    "sources": [
        "blog",
        "cafe",
        "news",
    ],
    "maxItemsPerKeyword": 20,
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("elabstudio/naver-blog-cafe-news-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "무선 이어폰"
  ],
  "sources": [
    "blog",
    "cafe",
    "news"
  ],
  "maxItemsPerKeyword": 20,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call elabstudio/naver-blog-cafe-news-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,elabstudio/naver-blog-cafe-news-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/zOnVFoWMBxsA5XgK3/builds/l3egeq6I1mMaCdscV/openapi.json