# Naver SERP Search Scraper — Web News Image Video Shopping (`khadinakbar/naver-serp-search-scraper`) Actor

Scrape Naver search results across web, news, image, video, and shopping as structured JSON. HTTP-first Korean SERP scraper with residential KR proxy. MCP-ready. Distinct from official Open API wrapper.

- **URL**: https://apify.com/khadinakbar/naver-serp-search-scraper.md
- **Developed by:** [Khadin Akbar](https://apify.com/khadinakbar) (community)
- **Categories:** SEO tools, AI, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 naver serp results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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 SERP Search Scraper

Turn Korean search queries into structured Naver SERP dataset rows across web, news, image, video, and shopping. Paste one keyword or a batch, pick a vertical, and the Actor returns ranked titles, links, snippets, press names, image URLs, channel labels, and shopping prices when the public results page exposes them. No NAVER API HUB Client ID or Secret.

This Actor is built for Korea SEO, brand-monitoring, and agent workflows that need SERP coverage including video and shopping cards from public search HTML.

### Best fit for this Actor

- Monitor Korean keywords across news, web, image, video, and shopping in one schema.
- Feed MCP or CRM pipelines with one predictable row per result (`resultType`, `position`, `title`, `link`).
- Sample shopping cards from nexearch product blocks when you need price-aware SERP snapshots.

For official HUB Search API rows with your own Client ID/Secret, continue with [Search Naver Open API](https://apify.com/khadinakbar/search-naver-open-api). For deeper product catalogs after a shopping SERP sample, continue with [Naver Product Shopping Scraper](https://apify.com/khadinakbar/naver-product-shopping-scraper). For place and map enrichment, use [Naver Map Scraper](https://apify.com/khadinakbar/naver-map-scraper).

### Practical scenario

A Korea SEO analyst tracks `서울 맛집` in the news vertical. They paste the query, set `where` to `news`, keep `maxResultsPerQuery` at `5`, and leave Residential KR proxy on. The run returns five ranked news rows with title, link, press name, and snippet. The same input pattern works for `무선이어폰` with `where=shopping` when they need nexearch product cards before deciding which listings to enrich next.

### Quick start input

```json
{
  "query": "서울 맛집",
  "where": "news",
  "maxResultsPerQuery": 5
}
```

`query` and `queries` can be combined; duplicates are collapsed. `where` accepts `web`, `news`, `image`, `video`, `shopping`, or `nexearch`. Prefer Korean keywords and Apify Residential with country `KR`.

### Input reference

| Field | Type | What it controls |
|---|---|---|
| `query` | string | Single search keyword. Example: `서울 맛집`. |
| `queries` | array | Batch keywords merged with `query`. Max 100 unique values. |
| `where` | enum | Vertical: `web`, `news`, `image`, `video`, `shopping`, `nexearch`. Default `web`. |
| `maxResultsPerQuery` | integer | Rows kept per query after parse. Default 30, max 300. Prefill uses 5. |
| `proxyConfiguration` | object | Prefer Apify Residential + `KR` for stable public SERP HTML. |

### What data you receive

One dataset item is one SERP result row.

```json
{
  "resultType": "news",
  "query": "서울 맛집",
  "where": "news",
  "position": 1,
  "title": "Example headline",
  "link": "https://n.news.naver.com/article/example",
  "snippet": "Short snippet…",
  "pressName": "Example Press",
  "newsDate": "1시간 전",
  "collectedAt": "2026-09-22T12:00:00.000Z"
}
```

| Field | Meaning |
|---|---|
| `resultType` / `where` | Vertical that produced the row |
| `position` | 1-based rank within the query |
| `title` + `link` + `snippet` | Public SERP card text and destination URL |
| `pressName` / `newsDate` | News vertical fields when present |
| `imageUrl` / `channelName` / `price` | Image, video, or shopping fields when present |

`OUTPUT` and `RUN_SUMMARY` in the default key-value store hold `outcome`, `itemsPushed`, and charged event counts. Outcomes include `COMPLETE`, `PARTIAL`, `VALID_EMPTY`, `INVALID_INPUT`, and `UPSTREAM_FAILED`. Download the dataset as JSON, CSV, Excel, or HTML.

### Use through the API

```bash
curl -X POST "https://api.apify.com/v2/acts/khadinakbar~naver-serp-search-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"query":"서울 맛집","where":"news","maxResultsPerQuery":5}'
```

CLI alternative:

```bash
apify call khadinakbar/naver-serp-search-scraper --input='{"query":"서울 맛집","where":"news","maxResultsPerQuery":5}'
```

### Use with AI agents through Apify MCP

> Scrape Naver news SERP for 서울 맛집. Return title, link, pressName, position, and snippet. Read OUTPUT.outcome and itemsPushed after the run. Budget: about $0.005 per accepted search-result plus platform usage. Scope: public Naver search HTML only. Provenance: collectedAt on each row.

Connect via <https://mcp.apify.com>. MCP tool: `apify--naver-serp-search-scraper`. Keep `maxResultsPerQuery` small on the first call while confirming yield.

### Connect the workflow

- After a shopping SERP sample, enrich product pages with [Naver Product Shopping Scraper](https://apify.com/khadinakbar/naver-product-shopping-scraper).
- When you need official HUB Search API quotas with BYOK keys, use [Search Naver Open API](https://apify.com/khadinakbar/search-naver-open-api).
- For place and map context around a keyword, continue with [Naver Map Scraper](https://apify.com/khadinakbar/naver-map-scraper).

### Pricing

This Actor uses Pay per event plus Apify platform usage. The live Pricing tab is the current source of truth for billing details.

- `apify-actor-start`: $0.00005 per run
- `search-result`: **$0.005** per accepted SERP result row

A five-result news prefill is about $0.025 in result events plus platform usage. Empty-match and invalid-input runs have no `search-result` charge.

### How it works

1. Normalize and deduplicate `query` / `queries`, then map `where` to the matching Naver search URL.
2. Fetch public SERP HTML with Cheerio and Apify Residential KR by default.
3. Parse SDS/Fender cards and embedded JSON into one row per result.
4. Charge `search-result` for each accepted row, then write the dataset item plus `OUTPUT` / `RUN_SUMMARY`.

### Best results

- Prefer Korean keywords that match the vertical intent (news, shopping, video).
- Keep Apify Residential with country `KR` enabled for stable public HTML.
- Start with `maxResultsPerQuery` near 5 while confirming yield, then raise the cap.
- An empty or whitespace-only query finishes `SUCCEEDED` with `INVALID_INPUT` and no result charge.
- A nonsense query that returns no cards finishes `SUCCEEDED` with `VALID_EMPTY` and no result charge.

### Builder's note

I found that public Naver SERP HTML on `search.naver.com` already exposes web, news, image, video, and nexearch shopping cards without Open API keys, which is enough for a lean multi-vertical scraper. Dedicated shopping hosts can return access challenges from non-KR routes, so this build keeps shopping on nexearch product cards and couples `Actor.charge('search-result')` to each validated row write so billing stays aligned with useful dataset items.

### Legal and responsible use

Use this Actor on public Naver search pages you are authorized to process, follow applicable law and Naver's terms, and keep the output in your own compliance workflow. Naver is a trademark of Naver Corp. This independent Actor is not affiliated with, associated with, or endorsed by Naver.

Issues and feature requests: use the Actor Issues tab on Apify.

# Actor input Schema

## `query` (type: `string`):

Enter one Korean or multilingual search query, for example 서울 맛집. Provide this, queries, or both.

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

Batch up to 100 queries in one run. Merged with query and de-duplicated.

## `where` (type: `string`):

Choose the Naver vertical. web/news/image/video paginate on dedicated SERPs. shopping extracts product cards from the integrated nexearch page. nexearch returns integrated web organic rows.

## `maxResultsPerQuery` (type: `integer`):

How many result rows to keep per query after pagination. Default 30, maximum 300.

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

Prefer Apify Residential with country KR. Naver may temporarily restrict non-Korean or datacenter exits.

## Actor input object example

```json
{
  "query": "서울 맛집",
  "where": "web",
  "maxResultsPerQuery": 5,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "KR"
  }
}
```

# Actor output Schema

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

Dataset items with resultType, query, where, position, title, link, and vertical-specific fields.

## `summary` (type: `string`):

Compact OUTPUT record with outcome, itemsPushed, charges, and warnings.

## `runSummary` (type: `string`):

Detailed RUN\_SUMMARY including page fetch and restriction counts.

# 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 = {
    "query": "서울 맛집",
    "maxResultsPerQuery": 5
};

// Run the Actor and wait for it to finish
const run = await client.actor("khadinakbar/naver-serp-search-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 = {
    "query": "서울 맛집",
    "maxResultsPerQuery": 5,
}

# Run the Actor and wait for it to finish
run = client.actor("khadinakbar/naver-serp-search-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 '{
  "query": "서울 맛집",
  "maxResultsPerQuery": 5
}' |
apify call khadinakbar/naver-serp-search-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,khadinakbar/naver-serp-search-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/EB9Q3opfySfcUbisQ/builds/l073m4o7H4EAApA51/openapi.json