Naver DataLab Search Trends

📈 Compare Naver search interest over time

For SEO teams, marketers, and researchers, this Actor returns Naver search trends for Korean or English terms. Compare named keyword groups, keep the audience filters with each series, and export the data for reports without copying chart values by hand.

• Compare brand names on one shared search-interest scale.
• Find seasonal peaks for product terms before planning campaigns.
• Combine Korean and English spellings to study one topic.
• Compare mobile and PC search interest in separate runs.
• Study interest among selected age bands for audience research.

📊 Keyword groups with dates and interest ratios

Each row holds one keyword group's series, its terms, and the comparison settings. Compare up to five groups, with up to 20 terms per group. Choose daily, weekly, or monthly periods and filter by device, gender, and age band.

Naver ratios use a shared 0 to 100 scale within the comparison. They are not absolute search counts. Changing the groups, date range, or audience can change that scale. Naver may leave out low-volume points; the Actor does not fill those gaps with zeros.

▶️ Run a keyword comparison

1. Add one to five named keyword groups.
2. Choose dates from January 1, 2016 onward, within Naver's available periods.
3. Choose the period interval and audience filters.
4. Start the Actor, then open the dataset to view or export the series.

Weekly and monthly inputs must cover whole calendar months. Naver can return narrower weekly boundaries within that range. You do not need to supply a Naver account or API key.

⚙️ Input

Input fields

Field	Type	What it does
keywordGroups	array of objects	Required. One to five groups compared together. The form prefills a Coffee group; there is no schema default.
keywordGroups[].name	string	Required nonblank group label. Must not contain __SZLIG__ or __OUML__.
keywordGroups[].terms	array of strings	Required. One to 20 nonblank terms combined for this group. Each term must not contain a comma or __OUML__. Put each full phrase in its own entry.
startDate	string	Required YYYY-MM-DD calendar date, January 1, 2016 or later. Weekly and monthly ranges must start on the first day of a month. Form prefill: 2024-01-01; no schema default.
endDate	string	Required YYYY-MM-DD calendar date on or after the start. Daily ranges can cover one day. Weekly and monthly ranges must end on the last day of a month. Form prefill: 2024-01-31; no schema default. Data depends on Naver's available periods.
maxItems	integer	Maximum saved group series, not period points. Use 0 or omit it for all available series. Minimum 0, with no fixed upper bound. Form prefill: 100; no schema default.
timeUnit	string	date for daily, week for weekly, or month for monthly. Default when omitted: date. Weekly and monthly ranges require whole calendar months.
device	string	all, mo for mobile, or pc. Default when omitted: all.
gender	string	all, f for female, or m for male. Default when omitted: all.
ages	array of strings	Naver age-band codes. Empty or omitted means all ages, the default. Repeated codes are combined.

Age codes are 1: 0-12, 2: 13-18, 3: 19-24, 4: 25-29, 5: 30-34, 6: 35-39, 7: 40-44, 8: 45-49, 9: 50-54, 10: 55-59, and 11: 60+.

Successful default input

This is the public input from the successful current-beta default-input run.

{
  "keywordGroups": [
    {
      "name": "Coffee",
      "terms": [
        "커피",
        "coffee"
      ]
    }
  ],
  "startDate": "2024-01-01",
  "endDate": "2024-01-31",
  "maxItems": 100,
  "timeUnit": "date",
  "device": "all",
  "gender": "all",
  "ages": []
}

🧾 Output

Output fields

Field	Type	What it does
groupName	string	Name of this keyword group.
terms	array of strings	Terms combined in this group.
startDate	string	First date covered by the returned comparison.
endDate	string	Last date covered by the returned comparison.
timeUnit	string	date, week, or month.
device	string	all, mo, or pc.
gender	string	all, f, or m.
ages	array of strings	Selected age codes; empty means all ages.
periods	array of objects	Published period dates and relative search-interest values.
periods[].period	string	Naver's period date in YYYY-MM-DD form.
periods[].ratio	number	Relative interest from 0 to 100 within this comparison.
comparisonUrl	string	Naver result-page link for the comparison. It may expire.

Example series

This complete row comes from a successful current-beta monthly comparison of Naver and YouTube terms.

{
  "groupName": "YouTube",
  "terms": [
    "유튜브",
    "youtube"
  ],
  "startDate": "2024-01-01",
  "endDate": "2024-03-31",
  "timeUnit": "month",
  "device": "pc",
  "gender": "m",
  "ages": [
    "9"
  ],
  "periods": [
    {
      "period": "2024-01-01",
      "ratio": 100
    },
    {
      "period": "2024-02-01",
      "ratio": 87.7661
    },
    {
      "period": "2024-03-01",
      "ratio": 95.78802
    }
  ],
  "comparisonUrl": "https://datalab.naver.com/keyword/trendResult.naver?hashKey=N_7751d278fb4c3350249af2248ffa1233"
}

💳 Pricing

The keyword-group-series event costs $0.135 for each keyword-group series saved to the dataset. The charge covers the group and all its returned period values, rather than each point. There is no separate run-start event in this Actor's pricing. Empty runs and input checks that save no series do not trigger this event.

Set maxItems to limit saved series. Repeated rows with the same group name and ordered term list are saved only once per run.

🔌 Integrations

Export the dataset as JSON, CSV, or Excel. Start runs and read saved rows through the Apify API, or use Apify schedules to repeat the same comparison for reports.

❓ FAQ

Why do weekly dates differ from my input dates?

Weekly input must cover whole months, but the returned dates follow Naver's published weekly boundaries. The row keeps those returned boundaries.

Does a missing period mean zero searches?

No. Naver may omit low-volume points. The Actor keeps the published points and does not fill gaps with zeros.

Can I compare ratios from separate runs?

The scale belongs to each comparison. Keep the groups, date range, and audience settings the same when comparing runs, and keep that context with your reports.

What if my run succeeds but has no rows?

Check the log for an input warning or a message that no trends matched. Invalid dates or unsupported choices can stop the run without saving rows. Try terms and periods with published Naver data.

Is this the official Naver DataLab tool?

This is an Apify Actor that returns public Naver DataLab search trends. You can also use Naver DataLab to view search trends. This Actor's input does not ask for Naver API credentials.

📝 Changelog

v0.0 (29-10-2026)

• Initial release.

🆘 Support

For issues, questions, or feature requests, file a ticket and I'll fix or implement it in less than 24h 🫡

🔗 Related Actors

• Naver Blog Review Scraper: Read public review posts about topics found in your trend research.
• Pinterest Trends Scraper: Rising Search Terms: Study Pinterest search terms alongside Naver interest.
• Naver DataLab Search Trends Scraper: Compare another Actor for Naver keyword trend series.
• Naver DataLab Search Trend (English): Explore another Naver search-trend workflow for Korean or English terms.
• Naver Search Autocomplete Scraper: Find query suggestions before choosing trend terms.

Made with ❤️ by Maxime Dupré