Google Search keyword popularity trends

Ask your Agent to compare one or two terms in a supported country using DataForSEO’s relative keyword-popularity series. Read the available dated values and any whole-period averages to explore changes in interest.

Up to 0.11 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

DataForSEO

Google Search keyword popularity trends

Ask your Agent to compare one or two terms in a supported country using DataForSEO’s relative keyword-popularity series. Read the available dated values and any whole-period averages to explore changes in interest.

You receive

Get available keyword-popularity values for dated intervals and, when provided, relative averages over the returned period. Your Agent can describe rises and dips and compare two terms within the same response using a shared highest-value reference of 100. The supplier’s documented defaults use Google Search and run from the same calendar date in the preceding year through today; interpret the actual returned intervals.

Start with your task

Compare search interest in [iphone 14] and [samsung s23] in [United States]. Summarize the changes across the dates returned on the same scale, where 100 is the highest point. Explain that these are estimates, not search counts; a zero means there was not enough data.

What to know

These are DataForSEO’s modeled relative indicators, not official Google Trends observations, search counts or audience percentages. A reported 0 means insufficient data; null and missing values remain unavailable. This Tool has no date, source or language selector. Returned intervals may not cover the whole default range, and the response does not establish current collection freshness or predict future demand.

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

The highest value across the submitted terms is the common reference. Each term does not independently get a peak of 100, and the values are not normalized to add up to 100. Compare terms within the same response; the indices do not establish absolute demand across separate requests.