Google Trends Full Scraper — Interest & Related
Interest over time, related queries and topics, and interest by region for up to 5 compared keywords. Handles rate limits with backoff + proxy, and flags every incomplete-period data point instead of returning it silently.
Google Trends Full Scraper — Interest & Related returns 8 documented output fields, including type, keyword, date, value and isPartial. Every field carries a declared type, a written description and an example value. 56 runs are recorded on Apify.
- 8
- Output fields
- 9
- Inputs
- 56
- Runs
- 2026-10-16
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| type | stringnull | Type of this record, as classified by the Actor. | article |
| keyword | stringnull | The keyword this record relates to. | <keyword> |
| date | stringnull | ISO 8601 date associated with this record. | 2026-10-15 |
| value | numbernull | Value as recorded for this row. | 42.5 |
| isPartial | booleannull | Whether the source marks this record as incomplete. | true |
| query | stringnull | The query that produced this row. | shopify scraper |
| rank | integernull | Position in the source's own ordering. 1 is highest. | 1 |
| geoName | stringnull | Geo Name as recorded for this row. | <geoName> |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"type": "article",
"keyword": "<keyword>",
"date": "2026-10-15",
"value": 42.5,
"isPartial": true,
"query": "shopify scraper",
"rank": 1,
"geoName": "<geoName>"
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| keywords | arrayrequired | Search terms to analyze, up to 5 — they are compared on the same scale, exactly like the Google Trends website. For more, run separate jobs. |
| geo | stringoptional | Two-letter country code (US, GB, DE...) or a sub-region (US-CA). Leave empty for worldwide. |
| timeRange | stringoptional | One of: now 1-H, now 4-H, now 1-d, now 7-d, today 1-m, today 3-m, today 12-m, today 5-y, all. |
| datasets | arrayoptional | Which data to return: interestOverTime, relatedQueries, relatedTopics, interestByRegion. |
| category | integeroptional | Google Trends category number to narrow results (0 = all categories). See Google Trends for category IDs. |
| property | stringoptional | Search surface: web (empty), news, images, youtube, or froogle (shopping). |
| language | stringoptional | Result language, e.g. en-US, de-DE. |
| proxyConfiguration | objectrequired | A proxy is required because Google rate-limits by IP. The example uses Apify Proxy; select residential access or provide an external proxy if the shared proxy is blocked for your run. |
| maxItems | integeroptional | Hard limit on output rows. Strictly enforced — you will never be charged for more than this. |
04 — run
Run Google Trends Full Scraper on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
8 of 8 fields described
- What does Google Trends Full Scraper — Interest & Related return?
- It returns 8 documented output fields: type, keyword, date, value, isPartial, query, rank and geoName. Each field declares its type, a description of what it holds, and an example value.
- What input does Google Trends Full Scraper — Interest & Related require?
- keywords and proxyConfiguration are required. A further 7 inputs are optional. The full input schema, with types and defaults, is below.
- Does Google Trends Full Scraper — Interest & Related need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run Google Trends Full Scraper — Interest & Related?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.