Naver News Scraper avatar

Naver News Scraper

Pricing

from $1.99 / 1,000 search results

Go to Apify Store
Naver News Scraper

Naver News Scraper

Scrape news search results from Naver (South Korea's #1 search engine). Extracts article titles, snippets, sources, publication dates, and image galleries. Supports pagination, source filters, and Korean date parsing — ideal for news aggregation and brand monitoring in the Korean market.

Pricing

from $1.99 / 1,000 search results

Rating

0.0

(0)

Developer

Search API

Search API

Maintained by Community

Actor stats

0

Bookmarked

5

Total users

2

Monthly active users

a month ago

Last modified

Features

Limited permissions

Share

Fast, structured extraction of public Naver News search results. Version 3 uses direct HTML requests and Cheerio instead of launching a browser, so normal searches complete in seconds while preserving Naver pagination, proxy support, sessions, retries, sorting, date controls, and safe failure handling.

Input modes

  • query: one Naver News search.
  • queries: multiple searches. Records are selected round-robin so one query cannot consume the full global limit.
  • startUrls: public https://search.naver.com/search.naver URLs containing where=news and a non-empty query.

These modes may be combined. Duplicate article IDs are removed; an article found by multiple searches receives matchedQueries and queryPositions.

Useful controls include sortBy (relevance, newest, or oldest), startDate, endDate, categories, publisher include/exclude lists, titleContains, pagination limits, concurrency, retries, timeouts, and Apify/custom proxy configuration.

{
"queries": ["인공지능", "로봇"],
"sortBy": "newest",
"maxItems": 20,
"maxPages": 2,
"proxyConfiguration": { "useApifyProxy": true }
}

GOOGLE_SERP is intentionally rejected because that proxy group supports Google HTTP requests, not Naver.

The complete input contract, including defaults, limits, and filter options, is in .actor/input_schema.json.

Output

Records contain only observed or deterministic fields. Core fields include:

  • stable id, articleId, and pressId;
  • publisher article url and naverUrl;
  • title, snippet, publisher, publisher profile/domain;
  • ISO publishedAt, original publishedAtRaw, and date precision;
  • Naver section/category when present;
  • direct publisher image and publisher logo URLs when present;
  • highlighted search terms;
  • query, per-query and global positions, page, search URL, sort order, locale, and scrape timestamp.

Optional values are omitted when unavailable—no fabricated favicon, zero-count, false-status, placeholder, null, empty string, array, or object fields are emitted. Relative publication labels such as 2일 전 are converted to ISO timestamps and marked approximate.

The complete dataset field schema is in .actor/dataset_schema.json.

How to use

Enter one or more News queries in the Apify Input tab, choose filters and limits, and start the Actor. Review normalized articles in the Output dataset.

Blocking and safety

The Actor uses a consistent desktop HTTP profile, cookie-persistent sessions, bounded retries, and optional Apify/custom proxies. HTTP status and content type are validated before parsing. Recognized no-result pages produce an empty dataset. Access-denied, challenge, or unexpected markup fails closed and is never stored as data. The Actor does not solve or bypass CAPTCHAs, authentication, paywalls, or access controls.