Use Naver Web, Blog, Cafe & News Results Scraper with Python

Search Naver's web, blog, cafe, or news results for a Korean or any-language query, and get back title, URL, domain, snippet, and source name for each organic result, filterable by keyword or domain.

1. Choose the data you need

Review the published README for supported collection modes, examples, and limits. The recipe below uses the current published input definition.

2. Prepare a source-based input

This JSON contains published prefills and required-field defaults. Review every value for your task before running it; it is not a promise of successful collection.

{
  "dateRange": "any",
  "includeAds": false,
  "includeContent": false,
  "includeSerpFeatures": false,
  "maxItems": 3,
  "maxItemsPerQuery": 3,
  "maxPagesPerQuery": 1,
  "mode": "webSearch",
  "searchQueries": [
    "비비바"
  ],
  "sortBy": "relevance"
}

Download input.example.json and save your reviewed copy as input.json.

Field	Type	Required	Description
`mode`	string	required	Which Naver result surface to collect.
`searchQueries`	array	optional	One or more Korean or any-language queries, e.g. `비비바` or `서울 맛집`. Duplicates and blank entries are removed. (Legacy `searchQuery` and `query` keys are still accepted.)
`maxItems`	integer	optional	Hard cap on all normal result records across every query (error records are extra).
`maxItemsPerQuery`	integer	optional	Hard cap on normal result records produced by each query.
`maxPagesPerQuery`	integer	optional	Page ceiling for paginated modes (blog, cafe, news, image, video). Collection also stops when Naver runs out of results.
`sortBy`	string	optional	Relevance or newest first. Applies to blog, cafe, news, image and video modes; web and integrated modes use Naver's default order.
`dateRange`	string	optional	Only return results published inside this window. Applies to blog, cafe, news, image and video modes; web and integrated modes do not support a date filter.
`includeAds`	boolean	optional	Keep paid blog placements and integrated-search ads, marked with `isAd`. (Blog and integrated modes.)
`includeContent`	boolean	optional	Fetch the post or article body, inline images and author for blog and news results. One extra request per result; unavailable bodies are omitted. (Blog and news modes.)
`includeSerpFeatures`	boolean	optional	Include place cards and AI briefing blocks from the integrated results page, when Naver shows them. (Integrated mode.)
`containsKeyword`	string	optional	Only keep results whose title, snippet, domain, source name, cafe name or suggestion contains this text (case-insensitive).
`domain`	string	optional	Only keep results from this domain (exact host or suffix, e.g. `naver.com` or `blog.naver.com`).

3. Start an Actor run

Set APIFY_TOKEN in your environment. Python 3.10 or newer is sufficient; this recipe uses no third-party packages.

Execution may incur charges. Review current pricing on Apify. The request asks for a 120-second timeout and a charge limit; these settings are subject to Apify’s pricing and do not guarantee an all-inclusive spending cap.

import json
import os
import urllib.request

# Save the schema-derived example as input.json; review and edit it first.
with open("input.json", encoding="utf-8") as stream:
    actor_input = json.load(stream)

token = os.environ["APIFY_TOKEN"]
request = urllib.request.Request(
    "https://api.apify.com/v2/acts/fXexRpaALarFERLPr/runs?timeout=120&maxTotalChargeUsd=0.50",
    data=json.dumps(actor_input).encode("utf-8"),
    headers={"Authorization": "Bearer " + token, "Content-Type": "application/json"},
    method="POST",
)
# This starts a potentially billable run. Do not automatically retry this POST.
with urllib.request.urlopen(request, timeout=40) as response:
    run = json.load(response)["data"]
print("Run ID:", run["id"])
print("Status:", run["status"])
# Inspect and download results in Apify Console once the run succeeds.

4. Inspect the actual results

Open the run in Apify Console and wait for a successful completion. Use the published output schema to locate results and the dataset schema to understand declared views. Missing or optional record fields must not be treated as guaranteed values.

Naver results across web, blog, cafe, news, image, video, integrated blocks and autocomplete — exact URLs, titles, snippets, dates, thumbnails, ranks and vertical-specific fields.

Questions before you run

Which inputs are required?

The published required fields are mode

What does this guide verify?

The fields, prefills, and schema links are rendered from the published build. This is a usage recipe, not a paid live extraction test. Source availability and collection results can vary.

What if the run request times out?

Check Apify Console before retrying. The first request may already have created a run. Do not automatically repeat a run-creation POST.

Open on Apify Full Actor reference

Generated from source build Rd3z6T4JbPlEIBdK3 and its README and schemas. Source changes regenerate this guide; no third-party editorial claims are inferred.