Naver DataLab Trends Scraper avatar

Naver DataLab Trends Scraper

Pricing

from $1.99 / 1,000 search results

Go to Apify Store
Naver DataLab Trends Scraper

Naver DataLab Trends Scraper

Scrapes public keyword trend data from Naver DataLab (datalab.naver.com). Extracts relative search volume indices for up to 5 keyword groups over a specified period, with optional device/gender/age filters.

Pricing

from $1.99 / 1,000 search results

Rating

0.0

(0)

Developer

Search API

Search API

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 days ago

Last modified

Share

Collect relative public search-volume indices from Naver DataLab for up to five keyword groups. Each group may combine related spellings or terms. The output preserves Naver's numeric 0–100 series as typed dataPoints, plus the exact requested range, time unit, device, gender, age buckets, and source provenance.

Use timeUnit values date, week, or month. Device is all, pc, or mo; gender is all, f, or m. Age codes follow the public DataLab form: 1 is under 13, 2 is 13–18, 3 is 19–24, continuing through 11 for 60+. Dates must be between 2016-01-01 and today and must be ordered.

{
"keywords": [{"name":"AI","keywords":["인공지능","AI"]}],
"startDate":"2026-01-01",
"endDate":"2026-03-31",
"timeUnit":"month",
"device":"",
"gender":"",
"ages":[]
}

Each dataset row represents one group. id identifies the group and complete filter request. dataPoints contains {period, value} objects; values are relative indices, not absolute search counts and should not be compared across independently normalized requests. pointCount is validated against the array length. Empty or unstructured chart fallbacks fail closed rather than storing page text as trend data.

The Actor automates the public DataLab form, captures the returned graph_data payload, applies the requested granularity and filters, and performs bounded single-page execution. It does not require Naver credentials or use private APIs. Run npm test, npm run check, apify validate-schema, and node validate-datasets.js for QA. Use modest request volume and comply with Naver's terms and applicable law.