Naver Search Scraper

Returns: one row per Naver web search result with query, position, title, url, domain, siteName, snippet, sourceUrl. Input: {"queries": ["서울 맛집"], "maxResults": 15} Best for: Korean SEO rank tracking, competitor and market research in South Korea, source discovery for Korean-language content.

{
  "query": "서울 맛집",
  "position": 1,
  "title": "맛집 - 라이브서울",
  "url": "https://tv.seoul.go.kr/video/c/2659?curationType=user",
  "domain": "tv.seoul.go.kr",
  "siteName": "라이브서울",
  "sourceUrl": "https://m.search.naver.com/search.naver?query=%EC%84%9C%EC%9A%B8+%EB%A7%9B%EC%A7%91&where=m_web&start=1"
}

What does Naver Search Scraper do?

Naver Search Scraper extracts organic web search results from Naver (네이버 검색), South Korea's largest search engine. You give it one or more search queries, in Korean or any other language, and it returns a clean dataset with the title, target URL, display URL, site name, snippet and ranking position of each result. No Naver login and no API key are needed.

It is useful for Korean SEO and rank tracking, market and competitor research in South Korea, source and lead discovery, and building datasets of Korean-language web content. The details that matter, all true to how the Actor works:

Only organic web results are collected. Ads, Naver-internal cards and Naver-owned pages are skipped. Multiple queries per run, and one failing query does not stop the others. Up to 130 results per query. Naver itself serves roughly 130 results per query in total. Every result carries its 1-based position within the query and the Naver result page it was found on. It uses Naver's mobile web search, which is server-rendered, so no browser is needed and runs stay fast and light.

What data can you get?

Each dataset item is one Naver search result.

Field	Description	Example
id	Stable SHA-1 hash of the query and result URL	8fd3f911f0389529f0e92a60409b21390e54dc1b
sourceUrl	Naver search results page the result was read from	https://m.search.naver.com/search.naver?query=...&where=m_web&start=1
query	The search query the result belongs to	서울 맛집
position	1-based rank of the result within its query	3
page	1-based Naver result page the result was found on (15 results per page)	1
title	Title of the result, truncated to 300 characters	서울맛집 맛집 인기검색 순위
url	Destination URL of the result	https://www.siksinhot.com/search?keywords=...
domain	Hostname of the result URL without www.	siksinhot.com
displayUrl	URL as displayed by Naver under the site name (null if not shown)	www.siksinhot.com › search › 서울맛집
siteName	Site name as displayed by Naver (null if not shown)	식신
snippet	Result description, truncated to 600 characters (null if none)	2주 전 식신이 추천하는 서울맛집...
date	Date shown before the snippet, ISO YYYY-MM-DD (null if Naver shows none)	2026-05-01
dateText	Verbatim date prefix from the snippet; preserves relative Korean wording	3일 전
scrapedAt	ISO 8601 UTC timestamp of the scrape	2026-09-29T18:51:20.864995+00:00

How to use Naver Search Scraper

1. Open Naver Search Scraper in Apify Console and go to the Input tab.
2. Add one or more search queries under Search queries, for example 서울 맛집 or python tutorial.
3. Set Max results per query, from 1 to 130.
4. Leave the proxy setting as it is. Enable Apify Proxy only if Naver blocks your runs.
5. Click Start and wait for the run to finish.
6. Open the Output tab and export the dataset as JSON, CSV, Excel or HTML.

Input

Field	Type	Default / prefill	Description
queries	array of strings	prefill ["서울 맛집"]	Search terms to look up on Naver web search. Korean or any language. Each query is scraped separately.
maxResults	integer 1 to 130	default and prefill 15	Maximum results to extract per query. Naver returns 15 results per page.
maxItems	integer	optional	Hard cap on total results across all queries.
includeDomains	array of strings	[]	Keep matching hostnames and their subdomains.
excludeDomains	array of strings	[]	Remove matching hostnames and their subdomains; exclusion wins.
proxyConfiguration	object	default {}, prefill {"useApifyProxy": false}	Optional. Runs work without a proxy in most cases. If Naver blocks your runs, enable Apify Proxy, residential recommended.

queries is required and must contain at least one non-empty term; otherwise the Actor stops immediately with an example of valid input. You can also pass a Naver search URL such as https://search.naver.com/search.naver?query=python; its query parameter becomes the search term. For a small agent call, use {"queries":["서울 맛집"],"maxItems":1}. A failed query is logged and the remaining queries continue. An empty run tells you to broaden the search term, or to retry later and enable Apify Proxy when requests failed. An empty dataset never contains error records.

Example input:

{
  "queries": ["서울 맛집", "python tutorial"],
  "maxResults": 30,
  "proxyConfiguration": { "useApifyProxy": false }
}

Focus a ranking report on particular domains

Use includeDomains to keep a brand's websites or a research source, or excludeDomains to remove sources you already know. Both take hostnames rather than URLs. A value of openai.com matches that hostname and its subdomains; it does not match notopenai.com. A leading www. is normalized. Defaults are empty arrays, so existing inputs produce the same results as before. If both lists match a result, exclusion wins.

{"queries":["OpenAI"],"includeDomains":["openai.com"],"maxItems":1}

Filtering is applied to the returned organic web results, without changing the query sent to Naver. position retains the original position among the Actor's eligible organic results, rather than becoming a new rank within the filtered subset. maxResults and maxItems count saved rows. Filtering can require more result pages, and restrictive filters may leave the dataset empty. The Actor examines at most nine pages per query and stops when no further results are available. Broaden your query or loosen the filters if the status reports no results. These filters never visit the destination websites.

Read dates with their original wording

dateText keeps the date prefix as Naver displayed it, for example 3일 전 or a dotted calendar date. date retains the existing normalized date for convenient sorting. Relative dates depend on the scrape date, and phrases expressed in months or years use the existing approximate day conversion. A relative phrase is evidence of what the search page showed, rather than proof of an article's exact publication timestamp. Use dateText, date, and scrapedAt together when preparing a report. Both date fields are null when Naver supplies no recognizable date prefix.

Requests use a bounded retry budget with backoff. Proxy retries obtain a fresh session URL, and visible CAPTCHA or access-denied messages cause retries. Merely loading a script that mentions CAPTCHA does not make an otherwise readable results page a block. If every attempt fails, the query is logged and later queries continue; no error row is stored. When the user's spending limit is reached, the final status says the run stopped at that limit.

Output

Below are real items from a local run with the query 서울 맛집. Search rankings, titles and snippets can change between runs.

[
  {
    "title": "맛집 - 라이브서울",
    "url": "https://tv.seoul.go.kr/video/c/2659?curationType=user",
    "domain": "tv.seoul.go.kr",
    "displayUrl": "tv.seoul.go.kr›video",
    "siteName": "라이브서울",
    "snippet": "서울에는 110년의 역사를 자랑하는 광장시장이 있습니다. 먹거리가 풍부한 광장시장에서 꼭 먹어봐야 할 음식들을 영상으로 만나보세요.",
    "date": null,
    "id": "9e4905738de55c3061e67ad7ab5fd8c6961e3d22",
    "sourceUrl": "https://m.search.naver.com/search.naver?query=%EC%84%9C%EC%9A%B8+%EB%A7%9B%EC%A7%91&where=m_web&start=1",
    "query": "서울 맛집",
    "position": 1,
    "page": 1,
    "scrapedAt": "2026-10-11T09:24:40.892526+00:00"
  },
  {
    "title": "서울 맛집 모아보기",
    "url": "https://korean.visitseoul.net/restaurants",
    "domain": "korean.visitseoul.net",
    "displayUrl": "korean.visitseoul.net›restaurants",
    "siteName": "Visit Seoul",
    "snippet": "서울 맛집 탐방하기. 서울에서 꼭 먹어봐야 할 음식 리스트! 서울의 감성 카페부터 한식, 중식, 일식, 양식, 아시아식, 채식, 할랄까지 서울 맛집 총정리. 다양한 메뉴, 지역별로 검색하여 맛있는 서울을 느껴보세요. 서울관광재단 Visit Seoul이 소개하는 서울 맛집.",
    "date": null,
    "id": "be1d6ea01e001d30e51cdd0056e730511c09c241",
    "sourceUrl": "https://m.search.naver.com/search.naver?query=%EC%84%9C%EC%9A%B8+%EB%A7%9B%EC%A7%91&where=m_web&start=1",
    "query": "서울 맛집",
    "position": 2,
    "page": 1,
    "scrapedAt": "2026-10-11T09:24:40.892526+00:00"
  }
]

How much does it cost?

Naver Search Scraper uses pay-per-event pricing, charged per result saved to the dataset. You are never charged for a result you did not get. Apify's free plan credit covers small runs, so you can test a few queries at no cost. See the Pricing tab of this Actor for the exact price per result on each plan.

Cost scales with the number of queries and the results per query, so a run with 3 queries and 30 results each produces at most 90 results. You can also set a maximum cost per run in the run options, and the Actor stops when that limit is reached.

Use with AI agents (MCP)

Naver Search Scraper can be called by AI assistants such as Claude, ChatGPT and Cursor through the Apify MCP server at https://mcp.apify.com. The server exposes the tools search-actors and call-actor, and this Actor's typed input and output schemas let an agent set the queries and read the results without guessing.

To load this Actor directly, add it to your MCP client configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=axiomworks/naver-search-scraper"
    }
  }
}

Example prompts you can type into your agent:

"Search Naver for 서울 맛집 and list the top 10 sites with their URLs." "Use Naver Search Scraper to check which sites rank for 'python tutorial' on Naver and summarize the top 20 results." "Get the first 30 Naver web results for three Korean product keywords and give me a table of site name and position."

Integrations and API

Python:

import os

from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("axiomworks/naver-search-scraper").call(run_input={
    "queries": ["서울 맛집", "python tutorial"],
    "maxResults": 30,
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["query"], item["position"], item["title"], item["url"])

JavaScript:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('axiomworks/naver-search-scraper').call({
    queries: ['서울 맛집', 'python tutorial'],
    maxResults: 30,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
process.stdout.write(JSON.stringify(items, null, 2));

cURL:

curl -X POST "https://api.apify.com/v2/acts/axiomworks~naver-search-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries": ["서울 맛집"], "maxResults": 15}'

Connect Naver Search Scraper to Zapier, Make, n8n, Google Sheets, Slack and other tools through Apify integrations, or use webhooks to trigger your own workflow when a run finishes. Schedule it in Apify Console, for example daily, to track Naver rankings over time.

FAQ

How many results can I get per query? Up to 130 per query, which is roughly all Naver serves, 15 per page. Queries with few matches return fewer.

Is this the same as what I see on naver.com? It uses Naver's mobile web search, which lists organic web results. Positions can differ slightly from the desktop page and from personalized results. Blog, cafe, news, shopping and place tabs are not included.

Do I need a proxy to scrape Naver? Usually not. Runs work without a proxy in most cases. If you see blocked or empty runs, for example an HTTP 403, HTTP 429 or a CAPTCHA page, enable Apify Proxy in the proxy field, with the residential group if possible.

A query returned nothing. Why? The run logs the reason for each failed query. If every query returns nothing, the run succeeds with an empty dataset and a status message saying what to change. If only some do, the others are still saved. Check spelling and try a broader query; for request failures, retry later or enable Apify Proxy.

How fast is it? It fetches 15 results per page and retries transient failures up to 3 times, so a query of 100 results takes a handful of page requests. Several queries in one run are processed one after another.

How often does the data change? Every run fetches live results, so rankings reflect the moment of the run. Schedule the Actor daily or weekly to track changes in Naver rankings over time.

Can I scrape Naver blogs, cafes or shopping? No. This Actor covers organic web search results only.

Is it legal to scrape Naver?

This Actor collects only publicly visible search results. It does not log in and does not access private content. You are responsible for how you use the data. Follow privacy law such as GDPR and CCPA when you store or process any personal data that appears in results, respect Naver's terms of service, keep request volume reasonable, and use the output lawfully. This is general information, not legal advice. This Actor is an independent tool and is not affiliated with, endorsed by or sponsored by Naver Corporation.

Feedback

Found a bug or want a new field? Open an issue in the Issues tab of this Actor. Feature requests and examples of queries that behaved unexpectedly are welcome.

한국어 안내

네이버 웹 검색 결과를 검색어별로 수집합니다. 각 결과에는 검색어(query), 순위(position), 페이지(page), 제목(title), 링크(url), 표시 주소(displayUrl), 사이트 이름(siteName), 요약(snippet)이 들어 있습니다.

주요 입력은 queries(검색어 목록)이며, maxResults로 검색어당 최대 결과 수(1~130)를, maxItems로 전체 결과 수 상한을 정할 수 있습니다. 네이버가 접속을 막는 경우 proxyConfiguration에서 Apify Proxy를 켜세요.

예시 입력:

{ "queries": ["서울 맛집"], "maxResults": 15 }