Search interest over time
dataforseo/keywords_google_trends_explore_liveCompare relative search interest for up to five terms.
- call
- Price: —
- DataForSEO
- 3 min
Overview
Reports how search interest in a set of terms has moved over time, as a relative popularity index rather than absolute counts. Up to five terms can be compared in one call, returning a value at each interval in the chosen range with explicit markers where data is missing, plus averages across the period. A geographic breakdown shows which regions searched most for each term, and related topic and query lists reveal what people search alongside them. The trend can be drawn from web, news, video, image, or shopping search, which gives materially different pictures for the same term.
A time series of relative interest per term, with averages, and any regional, topic, or query blocks requested.
Input
These go in the input object of the run request.
| Field | Type | Required | Description |
|---|---|---|---|
| keywords | array | No | Keywords. Required if you don't specify category_code the maximum number of keywords. |
| location_code | integer | No | Search engine location code. Optional. if you don't use this field, you will recieve global results. |
| language_code | string | No | Search engine language code. Optional. default value: en. |
| category_code | integer | No | Google trends search category. Required if you don't specify keywords if you don't specify keywords, the value of this field must be greater than 0 if you specify keywords and don't specify this field, the 0 value will be applied by default and the search will be carried out across all available categories. |
| location_name | string | No | Which market to report on; omit for worldwide interest. |
| type | string | No | Which search property to draw the trend from. Allowed: web, news, youtube, images, froogle Default: "web" |
| time_range | string | No | A preset window, ignored when explicit dates are given. |
| date_from | string | No | Start of the range, as `YYYY-MM-DD`. |
| date_to | string | No | End of the range, as `YYYY-MM-DD`. |
| item_types | array | No | Which blocks to return: the graph, the map, topics, or queries. |
Requests up to 1 MB.
Example
Use your own API key and a saved idempotency key for each new job. Replace image or media placeholders with your own publicly reachable HTTPS URLs. Keep the same key and request body when recovering a timeout.
# Set once per job; reuse this key and the identical body after a timeout.
: "${AGENTSKY_IDEMPOTENCY_KEY:?Set a unique, saved key for this job}"
curl --fail-with-body https://gateway.agentsky.dev/v1/run \
-H "authorization: Bearer $AGENTSKY_API_KEY" \
-H "content-type: application/json" \
-H "Idempotency-Key: $AGENTSKY_IDEMPOTENCY_KEY" \
-d '{"provider":"dataforseo","endpoint":"keywords_google_trends_explore_live","input":{"category_code":3,"keywords":["rugby","cricket"]}}'
# If status is READY/RUNNING, poll GET /v1/runs/{runId} with the same API key.Pricing
— per call using your plan when signed in. Reported usage is billed under your account plan. Read the final customer charge from price.amount.value after the run finishes. A RUNNING response is not the final bill.
