# Google Trends Bulk Scraper (`cornflower_vision/google-trends-scraper`) Actor Google Trends for hundreds of keywords in one run, all on one 0-100 scale (no 5-term limit). Interest over time, by region, related queries, comparisons and Trending Now. You only pay for queries that succeed. - **URL**: https://apify.com/cornflower_vision/google-trends-scraper.md - **Developed by:** [Jason Todd](https://apify.com/cornflower_vision) (community) - **Categories:** SEO tools, Marketing - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.00 / 1,000 query processeds This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Google Trends Bulk Scraper Get Google Trends data for **hundreds of keywords in one run**: interest over time, interest by region, related queries, keyword comparisons and Trending Now searches. Export to JSON, CSV or Excel, or call it from your code. **You only pay for queries that succeed.** If Google blocks a query and every retry fails, it is reported in the results and not charged. ### Why use this Actor? - πŸ“¦ **Bulk by default.** Paste a list of keywords and get them all back in one dataset. - βš–οΈ **Comparisons.** Compare up to 5 terms on the same 0-100 scale, like the *Compare* button on Google Trends. - πŸ† **Rank hundreds of keywords on one scale.** Google Trends stops at 5 terms per comparison. Turn on *Compare all search terms on one scale* and the Actor links many comparisons through an anchor term, so all your keywords share one 0-100 scale and get a rank. - πŸ—ΊοΈ **All the data on the Explore page.** Interest over time, by country, subregion, city or US metro area, plus related queries and topics. - πŸ”₯ **Trending Now.** Today's trending searches for any country, with approximate search volume and news links. - πŸ“Š **Spreadsheet-ready output.** Choose the *Flat* format to get one row per data point with the same columns everywhere. - πŸ›‘οΈ **Built for reliability.** Each parallel session uses its own proxy IP and cookies. When Google blocks a query on a datacenter IP, the Actor retries it through **residential proxies** automatically, at no extra cost to you. - ⚑ **Fast.** In our tests on 20 October 2026, 101 queries with 3 data types each finished in 1-3 minutes with 100% success. - πŸ” **Blocked queries get a second chance.** Queries that Google blocks during the run are tried again at the end, so a short blocking wave does not cost you results. ### What data can you get? | Data | What it is | |---|---| | Interest over time | Search interest (0-100) per hour, day, week or month in the chosen time range | | Interest by region | Search interest per country, subregion, city or US metro area (DMA) | | Related queries | Top and rising searches related to each term, including *Breakout* terms | | Related topics | Top and rising topics related to each term (see limitations) | | Comparison averages | Average interest of each term in a comparison group | | Trending Now | Trending searches in a country, with approximate traffic, picture and news articles | ### How to use it 1. Enter your **search terms**, one per line. Each term is one query. 2. Optionally add **comparison groups**, for example `bitcoin, ethereum, solana`. Each group is one query. 3. Pick a **location** code such as `US` or `VN` (leave empty for worldwide), a **time range** and the **data types** you want. 4. Click **Start**. When the run finishes, download the results or connect them to your tools. For daily trending searches, switch **Mode** to *Trending Now* and enter country codes. ### Compare hundreds of keywords on one scale Google Trends compares at most 5 terms at a time, and gives every comparison its own 0-100 scale. A 40 in one comparison and a 40 in another do not mean the same popularity. Turn on **Compare all search terms on one scale** to fix that: 1. The Actor splits your search terms into groups of 4 and adds the same **anchor term** to every group. 2. The anchor's real popularity is the same everywhere, so the Actor uses it to bring all groups to one scale. 3. Every term gets values on a common 0-100 scale (100 = the highest point of all terms), an `averageInterest` and a `rank`. ```json { "searchTerms": ["netflix", "disney plus", "hulu", "hbo max", "peacock", "paramount plus", "youtube tv", "sling", "fubo"], "compareAllTerms": true, "anchorTerm": "hulu", "geo": "US", "timeRange": "today 12-m" } ``` Each result item includes `rank`, `averageInterest`, `interestOverTime` on the common scale, `anchorTerm`, `groupTerms` (the terms Google compared together) and `precisionWarning`. The *All terms on one scale* view of the dataset (also the *Ranking* link in the run's Output tab) shows the ranking as a table. **Choosing the anchor term.** Pick a term of medium popularity compared with your other terms. Leave it empty to use the first search term. - If the anchor is tiny next to a group's terms, Google rounds it to almost 0 and that group loses precision. - Terms that are much less popular than their group get rounded heavily, too. In both cases the item has a `precisionWarning` that explains why, so you know which numbers to treat with care. **Use specific search terms.** Google counts every search that contains the words, so `max` also counts searches like "iphone pro max" and "air max". Use `hbo max` instead. **Checked against Google itself.** On 21 October 2026 we ran the 9 US streaming services above and compared terms from different groups directly in Google Trends: the Actor's values were within 1 point of Google's own comparison. **Cost.** Each group of 4 terms counts as one query, so 100 terms cost 25 queries. ### Input example ```json { "searchTerms": ["bitcoin", "ethereum", "solana"], "comparisonGroups": ["iphone, samsung galaxy, google pixel"], "geo": "US", "timeRange": "today 12-m", "includeInterestOverTime": true, "includeInterestByRegion": true, "includeRelatedQueries": true, "outputFormat": "nested", "proxyConfiguration": { "useApifyProxy": true } } ``` ### Output example **Nested format** (one item per query, shortened): ```json { "searchTerm": "bitcoin", "comparisonGroup": null, "geo": "US", "timeRange": "today 12-m", "category": 0, "searchType": "web", "interestOverTime": [ { "date": "2025-10-19", "timestamp": 1760832000, "formattedTime": "Oct 19 – 25, 2025", "isPartial": false, "value": 32, "hasData": true } ], "averages": null, "interestByRegion": [ { "geoName": "Wyoming", "geoCode": "US-WY", "value": 100 } ], "relatedQueries": { "top": [{ "query": "bitcoin price", "value": 100, "formattedValue": "100", "isBreakout": false, "link": "https://trends.google.com/trends/explore?q=bitcoin+price&date=today+12-m&geo=US" }], "rising": [{ "query": "how to buy bitcoin safely", "value": 9450, "formattedValue": "Breakout", "isBreakout": true, "link": "https://trends.google.com/trends/explore?q=how+to+buy+bitcoin+safely&date=today+12-m&geo=US" }] }, "relatedTopics": null, "trendsUrl": "https://trends.google.com/trends/explore?q=bitcoin&date=today%2012-m&geo=US", "warnings": [], "scrapedAt": "2026-10-19T14:00:00Z", "status": "success", "error": null } ``` In a comparison group, `interestOverTime[].values` and `interestByRegion[].values` hold one number per term, for example `{"bitcoin": 32, "ethereum": 6, "solana": 4}`. **Flat format** (one row per data point, same columns in every row): | rowType | searchTerm | geo | date | regionName | rankType | query | value | |---|---|---|---|---|---|---|---| | interestOverTime | bitcoin | US | 2025-10-19 | | | | 32 | | interestByRegion | bitcoin | US | | Wyoming | | | 100 | | relatedQuery | bitcoin | US | | | rising | how to buy bitcoin safely | 9450 | **Trending Now** items: ```json { "geo": "US", "rank": 1, "title": "example trend", "approxTraffic": "20000+", "approxTrafficMin": 20000, "publishedAt": "2026-10-19T14:20:00Z", "picture": "https://...", "pictureSource": "Example News", "newsItems": [{ "title": "...", "url": "https://...", "source": "Example News", "picture": "https://...", "snippet": null }] } ``` ### Pricing This Actor uses pay-per-event pricing. See the **Pricing** tab for current prices. - **Query processed:** charged once for each search term or comparison group that succeeds, no matter how many data types you selected. With *Compare all search terms on one scale*, each group of 4 terms counts as one query. - **Trending search:** charged once for each Trending Now item. Failed queries are never charged. Set a maximum cost per run, and the Actor stops cleanly when it is reached. ### Tips - **Values are relative, not search volumes.** 100 is the peak for that query; 50 means half as popular. Google calculates the scale for each query separately, so to compare terms on one scale put them in the same **comparison group**. - **Google samples its data,** so numbers can differ slightly between runs and from the website. - **Proxies matter.** Google rate-limits by IP address. Keep the proxy and **Switch to residential proxies when blocked** enabled. If queries still fail, lower **Parallel sessions**. - **Partial periods.** The last point is often `isPartial: true` because the period is not over yet. ### Limitations - This is an unofficial tool. It is not affiliated with or endorsed by Google, and Google can change its website at any time. - **Related topics** are often returned empty by Google, and Google does not provide them for comparison groups. The Actor adds a warning when that happens. - **Trending Now** returns the list Google publishes in its RSS feed, usually about 10 searches per country. - A comparison group can contain at most 5 terms, and its terms cannot contain commas: the comma separates the terms, as on Google Trends. - *Compare all search terms on one scale* supports interest over time only. Its values are as precise as Google's rounding allows. Google also samples its data, so single points can move by a few points between runs; averages and ranks are more stable. - City and metro-area breakdowns need a location; metro areas (DMA) exist only for the United States. ### FAQ **Why are some values 0?** Google shows 0 when there is not enough search volume for that term, place or time. **What does "Breakout" mean?** A rising query grew by more than 5,000%. The exact number is in `value`. **Is it legal to scrape Google Trends?** This Actor only collects public, aggregated statistics shown on the Google Trends website and no personal data. You are responsible for how you use the data; check the terms that apply to you, and consult a lawyer if you are unsure. **Can I call it from my code?** Yes. Replace `` with your Apify API token. Python: ```python from apify_client import ApifyClient client = ApifyClient("") run = client.actor("cornflower_vision/google-trends-scraper").call(run_input={"searchTerms": ["bitcoin"], "geo": "US"}) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item["searchTerm"], item["interestOverTime"][-1]) ``` JavaScript: ```javascript import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: '' }); const run = await client.actor('cornflower_vision/google-trends-scraper').call({ searchTerms: ['bitcoin'], geo: 'US' }); const { items } = await client.dataset(run.defaultDatasetId).listItems(); console.log(items); ``` cURL (waits for the run and returns the items): ```bash curl -X POST "https://api.apify.com/v2/acts/cornflower_vision~google-trends-scraper/run-sync-get-dataset-items" \ -H "Authorization: Bearer " -H "Content-Type: application/json" \ -d '{"searchTerms": ["bitcoin"], "geo": "US"}' ``` **Something does not work.** Open an issue on the **Issues** tab with the run link. Run statistics (requests, rate-limit hits, retries) are saved in the `RUN_STATS` record of each run, which helps us find the problem quickly. # Actor input Schema ## `mode` (type: `string`): Explore keywords: interest over time, by region and related searches for your search terms.
Trending Now: the searches trending right now in one or more countries. ## `searchTerms` (type: `array`): One search term per line. Each term is processed separately and counts as one query. ## `comparisonGroups` (type: `array`): Compare 2 to 5 terms on the same scale, like the Compare button on Google Trends. One group per line, terms separated by commas, for example bitcoin, ethereum, solana. Each group counts as one query. A term cannot contain a comma, because the comma separates the terms (the same rule as on Google Trends). ## `compareAllTerms` (type: `boolean`): Google Trends compares at most 5 terms at a time, and every request has its own 0-100 scale. Turn this on to put all your search terms on one scale, so you can rank hundreds of them. The Actor adds an anchor term to every group of 4 terms and rescales the groups through it. Only interest over time is supported in this mode. Each group of 4 terms counts as one query. ## `anchorTerm` (type: `string`): Used with Compare all search terms on one scale. Pick a term of medium popularity compared with your other terms: if the anchor is tiny next to them, the results lose precision (the output then shows a precision warning). Leave empty to use the first search term. ## `geo` (type: `string`): Country or region code, for example US, VN, GB or US-CA. Use the code, not the name: VN, not Vietnam. Leave empty for worldwide. ## `timeRange` (type: `string`): Google decides the data granularity: hourly for short ranges, daily, weekly or monthly for longer ones. ## `customTimeRange` (type: `string`): Only used when Time range is Custom range. Format: YYYY-MM-DD YYYY-MM-DD, for example 2024-01-01 2024-12-31. ## `category` (type: `integer`): Google Trends category ID. 0 means all categories. You can find the ID in the cat= part of a Google Trends URL. ## `searchType` (type: `string`): Which Google property the searches come from. ## `includeInterestOverTime` (type: `boolean`): Search interest (0-100) for each day, week or month in the time range. ## `includeInterestByRegion` (type: `boolean`): Search interest per country, region, city or metro area. ## `includeRelatedQueries` (type: `boolean`): Top and rising searches related to each term. ## `includeRelatedTopics` (type: `boolean`): Top and rising topics related to each term. Google often returns this list empty; not available for comparison groups. ## `regionResolution` (type: `string`): How to split Interest by region. Automatic uses countries for worldwide and subregions for a country. Cities and Metro areas need a location; metro areas exist only for the US. ## `includeLowVolumeRegions` (type: `boolean`): Also return regions where Google has too little data (value 0). ## `outputFormat` (type: `string`): Nested: one item per query with all data inside, best for JSON and APIs.
Flat: one row per data point with the same columns everywhere, best for Excel and CSV. ## `trendingGeos` (type: `array`): Two-letter country codes, one per line, for example US or VN. ## `language` (type: `string`): Language for Google's labels, for example en-US or vi. It does not change the numbers. ## `maxConcurrency` (type: `integer`): How many queries run at the same time, each from its own proxy IP and cookies. The default of 5 is the fastest in our tests: with 10, Google blocked so many more requests that the run got slower and more expensive. ## `maxAttemptsPerQuery` (type: `integer`): How many times a query is tried (with a fresh IP when Google blocks) before it is reported as failed. Failed queries are not charged. ## `proxyConfiguration` (type: `object`): Google rate-limits by IP address, so a proxy is strongly recommended. ## `residentialFallback` (type: `boolean`): Google blocks many datacenter IPs. When a query is blocked, it is retried through Apify residential proxies, which Google blocks far less. This keeps the success rate high and costs you nothing extra: you still pay per successful query. ## Actor input object example ```json { "mode": "explore", "searchTerms": [ "bitcoin", "ethereum" ], "compareAllTerms": false, "anchorTerm": "", "geo": "", "timeRange": "today 12-m", "category": 0, "searchType": "web", "includeInterestOverTime": true, "includeInterestByRegion": false, "includeRelatedQueries": false, "includeRelatedTopics": false, "regionResolution": "AUTO", "includeLowVolumeRegions": false, "outputFormat": "nested", "trendingGeos": [ "US" ], "language": "en-US", "maxConcurrency": 5, "maxAttemptsPerQuery": 5, "proxyConfiguration": { "useApifyProxy": true }, "residentialFallback": true } ``` # Actor output Schema ## `results` (type: `string`): No description ## `ranking` (type: `string`): No description ## `runStats` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "searchTerms": [ "bitcoin", "ethereum" ], "trendingGeos": [ "US" ], "proxyConfiguration": { "useApifyProxy": true } }; // Run the Actor and wait for it to finish const run = await client.actor("cornflower_vision/google-trends-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`πŸ’Ύ Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // πŸ“š Want to learn more πŸ“–? Go to β†’ https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "searchTerms": [ "bitcoin", "ethereum", ], "trendingGeos": ["US"], "proxyConfiguration": { "useApifyProxy": True }, } # Run the Actor and wait for it to finish run = client.actor("cornflower_vision/google-trends-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"πŸ’Ύ Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # πŸ“š Want to learn more πŸ“–? Go to β†’ https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "searchTerms": [ "bitcoin", "ethereum" ], "trendingGeos": [ "US" ], "proxyConfiguration": { "useApifyProxy": true } }' | apify call cornflower_vision/google-trends-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,cornflower_vision/google-trends-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/gipxaG7qz0CNMzroK/builds/ATbOASr0Z2hU3GIk1/openapi.json