Naver Shopping Insight Keyword Rankings avatar

Naver Shopping Insight Keyword Rankings

Pricing

from $1.99 / 1,000 search results

Go to Apify Store
Naver Shopping Insight Keyword Rankings

Naver Shopping Insight Keyword Rankings

Collects public popular-keyword rankings from Naver Shopping Insight by category, period, device, gender, and age.

Pricing

from $1.99 / 1,000 search results

Rating

0.0

(0)

Developer

Search API

Search API

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

2 days ago

Last modified

Categories

Share

CSV rank: 833. Original Store listing: billygogo/naver-keyword-scraper.

This Actor collects the public TOP 500 popular search-keyword ranking from Naver Shopping Insight. It uses the same category, date, device, gender, and age values as the website and maps Naver's response into a strict, stable dataset contract.

Input

  • categoryPath: exact Korean category labels separated by >, such as 패션의류 > 여성의류.
  • categoryId: optional advanced eight-digit category ID; overrides categoryPath and is validated against Naver.
  • startDate and endDate: optional YYYY-MM-DD dates. The period may not exceed one year.
  • timeUnit: date, week, or month.
  • devices: any of pc, mo; empty means all.
  • genders: any of f, m; empty means all.
  • ages: any of 10, 20, 30, 40, 50, 60; empty means all.
  • maxItems, maxPages, concurrency, retry, timeout, and optional proxy controls.

The Actor first opens and validates the public Shopping Insight page. It resolves human-readable category paths through Naver's category endpoint, submits the normalized filter payload to Naver's ranking endpoint, validates page order and response shape, deduplicates by category and normalized keyword, and writes records only after the complete bounded extraction succeeds.

Output

Each record contains the category ID/name/path, rank, keyword, applied filter values, result page, public source URL, and ISO-8601 collection time. Raw responses, cookies, headers, proxy URLs, and internal transport fields are never stored.

If Naver returns a CAPTCHA or access-control response, the Actor fails closed with TARGET_BLOCKED in OUTPUT_SUMMARY and writes no dataset placeholders.

Local verification

npm install
apify validate-schema
apify run --purge