# Naver Blog Search Scraper: Blog, Cafe & News Posts (`accountable_eel/naver-search-lookup`) Actor

Naver blog search by keyword: Naver blog, cafe and news posts for any Korean or English search, with title, snippet, date and link. Watch a brand and get only new posts, with alerts to Discord, Slack or Telegram. No author names or profile links. Searches that find nothing are free.

- **URL**: https://apify.com/accountable_eel/naver-search-lookup.md
- **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Social media, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.50 / 1,000 search result returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Search Lookup

Search Naver for any keyword or brand and get the **blog, cafe and news posts** that come back: one row per post with title, snippet, date and link. Run it once for research, or schedule it as a **monitor** that returns only the posts it has not shown you before and sends each one to Discord, Slack or Telegram. It reads Naver's public search result lists, needs no Naver account and no API key, and **never collects an author name, nickname or profile link**.

### What it does

- **Three sources, one run.** Naver Blog, Naver Cafe and Naver News, each read as its own result list. A row's `source` says which one it came from.
- **Korean or English keywords.** Naver returns the same Korean-language results for both, so a brand name written in Latin letters works too.
- **Up to 90 blog posts or 60 cafe posts per search** (pages of 30; Naver ends its cafe list after 2 pages). News is the first page, 10 articles.
- **Newest first, or only recent.** Ask Naver for its date order, or keep only posts on or after a date.
- **Monitoring.** Turn on *Track new posts across runs* and each run marks every post `new` or `seen`; add *Only return new posts* and a quiet day returns nothing and costs only the run start.
- **Alerts.** Paste a Discord or Slack webhook (or a Telegram bot link, or any URL for n8n and Make) and each new post arrives as one message.
- **Free misses.** A search Naver has no results for, or that Naver blocks, writes one row with `found: false` and a plain-English `status`, and is never charged.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `queries` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~naver-search-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"queries":["아이폰 케이스","다이소 후기"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "queries": [
    "아이폰 케이스",
    "다이소 후기"
  ]
}
```

One search per line: a keyword, a brand or a phrase, in Korean or English. Each line is searched on Naver, in the sources you pick below. Accepted formats: 아이폰 케이스, 다이소 후기, apple vision pro.

#### Fields you can set

| Field | What it does |
| --- | --- |
| `queries` | One search per line, Korean or English. |
| `sources` | `blog`, `cafe`, `news`, `blog+cafe` or `blog+cafe+news`. |
| `maxItemsPerQuery` | Posts to read per search **and per source**, 1 to 90 (default 10). News is capped at its first page. |
| `sortBy` | `relevance` (Naver's order) or `newest`. Blog and Cafe only; with monitoring on they are always read newest first. |
| `sinceDate` | `YYYY-MM-DD`: keep only posts on or after that date. Applied on our side after the fetch (and also asked of Naver for Blog). |
| `includeKeywords` / `excludeKeywords` | Keep or drop posts whose title or snippet contains any of these words. Applied before anything is counted or billed. |
| `deltaMode`, `deltaName`, `skipFirstRun`, `alertOnChangeOnly` | Monitoring: see *Watch a brand and send new posts to Discord* below. |
| `notifyUrl`, `notifyFormat`, `maxNotificationsPerRun` | Where new posts are sent. The link is a secret input: it is never logged and never written to the results. |

### Output

One row per **post**, for example (a Naver Blog result for `아이폰 케이스`, shortened):

```json
{
  "query": "아이폰 케이스",
  "found": true,
  "status": "OK",
  "source": "blog",
  "rank": 4,
  "title": "케이스티파이 아이폰 17Pro 리플케이스 스카이블루 & 큐빅 카메라 렌즈",
  "snippet": "리플 케이스 아이폰 17Pro 스카이블루 컬러 리플 케이스는 컬러가 다양…",
  "url": "https://blog.naver.com/gksmf889/224440704714",
  "publishedDate": "2026-10-13",
  "publishedDateApprox": true,
  "publishedText": "2주 전",
  "sourceName": null,
  "checkedAt": "2026-10-27T09:41:07.000Z",
  "isNew": null,
  "changeType": null
}
```

The table below lists every column.

| query | found | status | source | rank | title | snippet | url | publishedDate | publishedDateApprox | publishedText | sourceName | checkedAt | isNew | changeType | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 아이폰 케이스 | true | OK | <source> | <rank> | <title> | <snippet> | <post link> | \<published (date)> | <date is approximate> | <date as naver printed it> | <cafe or publisher name> | <checked at> | \<is this post new?> | <change type> | 1970-01-01T00:00:00.000Z |

A miss comes back as a row with `"found": false` and is never charged: `NOT_FOUND` (Naver has no results, or none inside your date or keyword filter), `BLOCKED` (Naver answered 403/429 or sent something that is not a search page, such as a captcha), `PARSE_CHANGED` (Naver sent a results page but no posts could be read from it) or `BAD_FORMAT` (an empty or over-long search).

#### About the dates

Naver prints an exact date (`2026.09.23.`) for older posts but only an age (`9시간 전`, `2주 전`) for recent ones. Ages are turned into a calendar date in Korean time and flagged `publishedDateApprox: true`; the unit is the error (up to a week for weeks). `publishedText` always keeps what Naver printed. With `sinceDate`, a post aged `2주 전` counts as exactly 14 days old, the newest it can be, so the filter never hides a post that might be inside the window.

### Watch a brand and send new posts to Discord

1. **Make a webhook.** In Discord open the channel's *Settings → Integrations → Webhooks → New Webhook* and copy the webhook URL. (Slack: an incoming-webhook URL. Telegram: `https://api.telegram.org/bot<token>/sendMessage?chat_id=<chat id>`.)
2. **Fill in the actor once.** Put your brand or product names in *Search keywords*, one per line, set *Where to search* to *Blog, Cafe and News*, tick *Track new posts across runs*, give the watchlist a name, tick *Seed silently* and *Only return new posts*, and paste the webhook into *Send alerts to*. Run it: this first run only remembers what Naver shows today. It returns no rows, sends no messages and bills nothing.
3. **Save it as a Task and schedule it** (daily is usual). From the second run on, every post that was not there last time arrives as one Discord message with its title, snippet, date and link, and as one row in the dataset. A day with nothing new costs only the run start. Messages are free; you pay per post row delivered.

### Example runs

**Naver blog search by keyword.** `queries`: `아이폰 케이스`, `다이소 후기` · `sources`: `blog` · `maxItemsPerQuery`: `30`. One row per blog post with title, snippet, date and link, in Naver's relevance order.

**New Naver blog posts about a brand, alerted.** `queries`: your brand · `sources`: `blog+cafe+news` · `deltaMode`: on · `deltaName`: `my-brand` · `skipFirstRun`: on · `alertOnChangeOnly`: on · `notifyUrl`: your webhook. Schedule it daily.

**Naver cafe search for a product.** `queries`: `아이폰 케이스` · `sources`: `cafe` · `sortBy`: `newest` · `maxItemsPerQuery`: `30`. Cafe posts (community discussions and reviews) newest first, with the cafe's name in `sourceName`.

### Limits

- **First result pages only.** Blog: up to 90 posts per search (3 pages of 30). Cafe: up to 60 (Naver ends the cafe list after 2 pages). News: the first page, 10 articles, without the related headlines Naver groups under them. There is no way to read deeper.
- **Titles and snippets, not full posts.** The actor never opens a post, so it has no full text, comments, likes or images. `snippet` is the excerpt Naver prints under the title.
- **No author data.** Blog and cafe authors are private individuals, so no blogger name, nickname, profile link or profile picture is read or returned. A Blog row has an empty `sourceName`; a Cafe row carries the cafe's (community's) name and a News row the publisher (the outlet's website domain when Naver prints no name for it). The post link alone identifies the post.
- **Korean-language results.** Naver serves the same Korean results whatever language you search in or send.
- **Recent dates are approximate** (see *About the dates*).
- **Filters.** `sortBy` works for Blog and Cafe, not News. A date range is asked of Naver for Blog only; for Cafe and News `sinceDate` is applied after the fetch.
- **Naver's index.** You see what Naver shows for that search at that moment; a post Naver has not indexed, or has hidden, will not appear.

### FAQ

**Do I need a Naver account or API key?** No. The actor reads Naver's public search pages.

**Is every row billed?** Every post row delivered is billed. A search with no results, a blocked search, and posts hidden by *Only return new posts* or your keyword words are not.

**What does `rank` mean?** The post's position in Naver's own list for that search and source, not counting ads. With `sinceDate` or keyword words, the posts that are dropped leave gaps in the rank numbers.

**Why did monitoring mark old posts as new?** A new watchlist name starts empty. Keep the same `deltaName` (or the same sources) between runs. A watchlist remembers the last 20,000 posts per search.

**Who is responsible for how the results are used?** You are, including compliance with Naver's terms of service and applicable data-protection law.

### Pricing

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed
per item only when data is actually found and returned — see
`.actor/pay_per_event.json` for exact prices. A miss is never charged.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~naver-search-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"queries":["아이폰 케이스","다이소 후기"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~naver-search-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"queries":["아이폰 케이스","다이소 후기"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~naver-search-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"queries":["{{search}}"]}`, mapping the row's search into the `queries` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Naver Blog Search: Posts, Cafe and News Scraper" — the agent will find and run this actor.

# Actor input Schema

## `queries` (type: `array`):

One search per line: a keyword, a brand or a phrase, in Korean or English. Each line is searched on Naver, in the sources you pick below. Accepted formats: 아이폰 케이스, 다이소 후기, apple vision pro. You're only charged for the ones we actually find — a miss costs nothing.

## `sources` (type: `string`):

Which Naver result lists to read for every search. Each source is read separately and every row says which one it came from.

## `maxItemsPerQuery` (type: `integer`):

Blog returns 30 posts a page and is read up to 3 pages, so up to 90. Cafe is read up to 2 pages, so up to 60 (Naver ends its cafe list there). News gives its first page only (10 articles). Default 10. You are billed per post returned.

## `sortBy` (type: `string`):

Blog and Cafe only: Newest first asks Naver for its date order. News always comes in Naver's own order. With monitoring on, Blog and Cafe are always read newest first.

## `sinceDate` (type: `string`):

YYYY-MM-DD. Applied after the fetch on each post's date (Korean time); for Blog it is also asked of Naver. A post whose date cannot be read is dropped. A post dated only as '2 weeks ago' counts as 14 days old, the newest it can be.

## `deltaMode` (type: `boolean`):

Turns the actor into an alert feed. Each run compares every post of a search with the posts that search returned before and marks it new or seen. Schedule it daily and combine with 'Only return new posts' and 'Send alerts to'.

## `deltaName` (type: `string`):

Leave empty and one is derived from the sources you picked. Type your own name to keep one memory across changes, or to run several independent watchlists. With a name set and the checkbox above off, every post is returned and marked new or seen.

## `skipFirstRun` (type: `boolean`):

The first run of a search has nothing to compare with. Turn this on to remember its posts without returning or billing them, so alerts start from the second run.

## `alertOnChangeOnly` (type: `boolean`):

With monitoring on, a run returns only the posts not seen before. Posts seen before write no row and are not billed, so a quiet day costs only the start fee.

## `notifyUrl` (type: `string`):

Optional. After a post is billed, each NEW post is sent here as one message with its title, snippet, date and a link. Discord or Slack: paste the channel's webhook URL. Telegram: https://api.telegram.org/bot<token>/sendMessage?chat_id=<chat id>. Any other URL receives JSON. Messages are free, and a failed message never fails the run (the row's notifyErrors says why). Stored encrypted, never logged or written to the results. Alerts only go out with monitoring on.

## `notifyFormat` (type: `string`):

Leave on 'Detect from the link': discord.com links get Discord messages, hooks.slack.com Slack, api.telegram.org Telegram, anything else JSON. Pick one only to override that.

## `maxNotificationsPerRun` (type: `integer`):

Up to 100. After this, one 'more posts' message says the rest are in the run's dataset. 0 sends only that one message.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

## `maxResults` (type: `integer`):

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

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

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

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

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "queries": [
    "아이폰 케이스",
    "다이소 후기"
  ],
  "sources": "blog",
  "maxItemsPerQuery": 10,
  "sortBy": "relevance",
  "sinceDate": "",
  "deltaMode": false,
  "deltaName": "",
  "skipFirstRun": false,
  "alertOnChangeOnly": false,
  "notifyFormat": "auto",
  "maxNotificationsPerRun": 20,
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "columns": [
    "source",
    "rank",
    "title",
    "snippet",
    "url",
    "publishedDate",
    "publishedDateApprox",
    "publishedText",
    "sourceName",
    "checkedAt",
    "isNew",
    "changeType"
  ],
  "maxConcurrency": 1,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

No description

# 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 = {
    "queries": [
        "아이폰 케이스",
        "다이소 후기"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/naver-search-lookup").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 = {
    "queries": [
        "아이폰 케이스",
        "다이소 후기",
    ],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/naver-search-lookup").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 '{
  "queries": [
    "아이폰 케이스",
    "다이소 후기"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/naver-search-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/naver-search-lookup"
        }
    }
}
```

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/Rf2kGnEAHHlTTjlCI/builds/BgWpcz5OyuwWcqIqE/openapi.json