Naver Blog Search Scraper

What does Naver Blog Search Scraper do?

This Actor searches the public Naver Blog results tab and collects post cards that Naver renders for a keyword. It returns card text, public blog/profile links, displayed date text, available thumbnails, and search provenance; it does not open posts or access private account data.

Why use Naver Blog Search Scraper?

Use it to discover public posts for monitoring topics, content research, and market research. The Actor follows the current Blog tab, deduplicates posts by canonical Naver post URL, and scrolls the rendered results page with a bounded number of attempts until it reaches maxItems or Naver stops adding cards. It records the exact search URL and a collection timestamp with each result. Apify runs, schedules, API access, integrations, and run history are available through the platform.

What data can it extract?

Field group	Fields	Notes
Post identity	title, link, canonicalLink, postId, blogId	IDs are included when they can be parsed from the post URL.
Cloud contract aliases	id, postKey, queryPosition, page, url, blogUrl, authorName, authorUrl, dateRaw, publishedAt, thumbnailUrl	These retain the Cloud field names using the same parsed card values; publishedAt is included only for an absolute date.
Public author links	blogName, blogHomeUrl, bloggerName, bloggerProfileUrl, bloggerId	Each field is omitted when the card does not expose it.
Card content	snippet, description, date, publishedDate, datePrecision	Relative date labels are preserved as text and are not converted into guessed timestamps. description is a compatibility alias for snippet.
Card media	thumbnail, thumbnailUrls, thumbnailCount	Includes unique image URLs linked to the post card.
Search provenance	position, query, searchUrl, pageNumber, source, sourceDomain, recordType, extractionMethod, scrapedAt	Identifies where and when a result was collected.
Promotion marker	isSponsored, sponsorLabel	Reports a sponsored marker only when a distinct 광고 or Sponsored label is present.

The dataset schema declares 40 possible fields. Optional source fields are omitted when the card does not provide them; the Actor does not insert empty text or substitute values.

How to scrape Naver Blog

1. Open the Actor in Apify Console and enter a keyword in Search Query.
2. Choose a Maximum Items value from 1 to 200.
3. Start the run and inspect the dataset. The Actor scrolls the single Blog results page; pageNumber remains 1 for these in-page results.
4. Download the dataset or use the run's API tab, schedule, or integration options.

How much will it cost to scrape Naver Blog?

The Actor's compute use depends on the browser run, the number of cards loaded, and the scrolling needed to reach the requested item limit. It waits briefly after each scroll and stops after two consecutive scrolls add no new post cards; scrolling is capped at 24 attempts. Selecting an Apify proxy can add proxy usage according to your Apify plan. No fixed price is promised here; check the run usage and your account's current pricing.

Input

The input accepts one query, an optional batch in queries, a result cap, paging and retry controls, and optional proxyConfiguration. Duplicate and blank batch queries are removed. When both query inputs are empty, the Actor uses the schema's Korean prefill query.

Input	Type	Default	Range or behavior
query	string	인공지능	Optional query. Combined with queries and deduplicated.
queries	array of strings	Omitted	Optional batch of query strings.
maxItems	integer	50	1–200 unique posts. The scroll loop is bounded and may return fewer results if Naver stops loading cards.
maxPages	integer	3	1–20 result loading pages per query; each extra page is bounded scrolling on the rendered results page.
maxConcurrency	integer	2	1–5 browser result pages processed concurrently.
maxRequestRetries	integer	2	0–5 retries for transient navigation, rate-limit, or proxy failures.
proxyConfiguration	object	Omitted	Optional Apify proxy routing. Standard proxy routing does not bypass Naver access restrictions or challenges.

Example inputs

Default search:

{
  "query": "인공지능"
}

Limit the number of returned cards:

{
  "query": "서울 카페",
  "maxItems": 30
}

Run without proxy routing:

{
  "query": "도시 텃밭",
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

Output

Each dataset row is one Naver Blog search card. Fields unavailable in a particular card are omitted. publishedDate is included only for an absolute calendar date; relative dates remain in date and set datePrecision to relative.

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Tips and advanced options

• maxItems is a result cap; the Actor stops early when the page has no new cards after two scroll attempts.
• Positions are assigned in the order unique post cards are collected. Deduplication uses the canonical Naver post URL.
• A card may expose a blog name, a profile name, both, or neither. These names and URLs are emitted only when shown on the card.
• The Actor reads search cards only. It does not extract full post bodies, comments, follower counts, or details from post pages.
• Proxy routing is optional and does not override access controls. If Naver presents a challenge or access restriction, the Actor fails rather than trying to bypass it.

FAQ, support, and responsible use

Why did a run return fewer posts than maxItems? Naver may stop loading cards, return fewer matching posts, or restrict the browser session. The Actor returns only cards it can read from the public results page.

Why is publishedDate missing? Naver often shows relative text such as 2주 전. That exact text remains available in date; the Actor does not infer a calendar date from it.

Where can I report an issue? Use the Actor's Issues tab and include the run ID, query category (avoid sensitive personal queries), and a short description. The API tab provides dataset access and run links.

This Actor is not affiliated with Naver. It collects public search-card information; results may contain personal data that authors chose to make public. Use it for a legitimate purpose, follow Naver's terms, robots guidance, rate limits, and applicable privacy laws, and seek qualified legal advice when needed. Do not use the Actor to collect private data or evade access restrictions.