# Google Trends Scraper and API (50 Terms) (`locaihost/google-trends`) Actor Export Google Trends to JSON or CSV: interest over time, interest by country, region or metro, top and rising related queries, and Trending Now searches with volume and growth. Up to 50 terms on one 0-100 scale, chained through an anchor term. No API key, no login. $1 per 1,000 rows. - **URL**: https://apify.com/locaihost/google-trends.md - **Developed by:** [locaihost data](https://apify.com/locaihost) (community) - **Categories:** SEO tools, Automation, News - **Features:** Limited permissions - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.55 / 1,000 rows This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. 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 Scraper and API (50 Terms) Get Google Trends data as JSON or CSV rows: interest over time, interest by region, top and rising related queries, and the full Trending Now list for any country. Up to 50 search terms go on one 0-100 scale. No login, no API key. What people use it for: - Ranking many keywords at once: up to 50 terms on one scale, where trends.google.com allows 5. - Content and SEO planning: seasonal peaks and the rising queries around a topic. - Daily trend alerts: schedule Trending Now with `onlyNew` to get only searches that started trending since the last run. - Sizing markets: where a product or brand is searched most, by country, region, US metro or city. - Dashboards and models: the tidy format gives one row per date, region or query, which loads straight into a BI tool or spreadsheet. ### Quick start Paste this into the **JSON** tab of the input and click **Start**: ```json {"searchTerms": ["coffee", "tea", "matcha"], "geo": "US", "trendingCountries": ["US"], "maxTrendsPerCountry": 10} ``` You get one row per term (12 months of weekly interest with average, peak and latest value) and today's 10 top trending searches in the US: 13 rows in about 10 to 30 seconds. Trending-only runs skip Google's cookie step and start at once (since 18 Oct 2026). More examples: ```json {"searchTerms": ["coffee", "tea", "matcha"], "geo": "US", "includeRegions": true, "includeRelatedQueries": true} ``` ```json {"trendingCountries": ["US", "GB", "IN"], "trendingWindow": "past-24-hours", "onlyNew": true} ``` Already have a comparison open on trends.google.com? Paste its link. The terms, location, time range, category and search type are read from it: ```json {"startUrls": [{"url": "https://trends.google.com/trends/explore?q=coffee,tea&geo=US&date=today%205-y"}]} ``` ### What you get | Group | Fields | |---|---| | Term (`type: "term"`, series format) | `term`, `averageValue`, `peakValue`, `peakDate`, `latestValue`, `latestDate`, `timeline` (`date`, `value`, `isPartial`), `regions`, `relatedQueries`, `relatedTopics`, `resolution` | | Request | `geo`, `geoName`, `timeRange`, `category`, `categoryId`, `searchType`, `comparedWith`, `anchorTerm`, `scaleNote`, `notes`, `trendsUrl` | | Interest over time (tidy) | `term`, `date`, `value`, `rawValue`, `isPartial` | | Interest by region (tidy) | `regionLevel`, `regionCode`, `regionName`, `value` | | Related queries and topics (tidy) | `list` (top or rising), `rank`, `query`, `topic`, `topicType`, `topicId`, `value`, `risePercent`, `breakout` | | Trending Now | `country`, `countryName`, `title`, `searchVolume`, `searchVolumeText`, `increasePercent`, `startedAt`, `endedAt`, `active`, `categories`, `relatedQueries`, `news`, `window`, `source` | - Interest over time: ISO dates, values 0-100, the step Google used (hour, day, week, month) and a flag on the current unfinished period. - More than 5 terms on one scale. Google compares at most 5 terms at a time and scales each comparison on its own. Give this Actor up to 50 terms and it chains the comparisons through a shared anchor term and rescales them, so every term is on the same 0-100 scale. - Trending Now: every trending search Google lists for a country in the past 4 hours, 24 hours, 48 hours or 7 days, with search volume, growth, start time, whether it is still rising, category and the searches behind it. The RSS feed only gives the newest 10. - Inputs: "United States" or "US", "past-90-days" or your own start and end dates, a category from a list or any of Google's ~1,400 category ids, and web, image, news, shopping or YouTube search. - Every row links to the same view on trends.google.com (`trendsUrl`), so you can check the numbers. One real term row and one Trending Now row (run on 2026-10-18, shortened): ```json [ { "type": "term", "term": "coffee", "geo": "US", "geoName": "United States", "timeRange": "past-12-months", "category": "All categories", "searchType": "web", "comparedWith": ["coffee", "tea", "matcha"], "resolution": "WEEK", "averageValue": 76.91, "peakValue": 100, "peakDate": "2026-04-12", "latestValue": 68, "latestDate": "2026-10-11", "timeline": [{"date": "2025-10-12", "value": 62, "isPartial": false}, {"date": "2026-10-18", "value": 54, "isPartial": true}], "trendsUrl": "https://trends.google.com/trends/explore?q=coffee%2Ctea%2Cmatcha&geo=US&date=today%2012-m" }, { "type": "trending-now", "country": "US", "countryName": "United States", "title": "notre dame vs byu", "searchVolume": 1000000, "searchVolumeText": "1,000,000+", "increasePercent": 1000, "startedAt": "2026-10-17T11:30:00Z", "active": true, "categories": ["Sports"], "relatedQueries": ["notre dame football", "byu", "byu notre dame"], "window": "past-24-hours", "source": "trending-now" } ] ``` The dataset has five views (**Terms**, **Interest over time**, **Interest by region**, **Related queries and topics**, **Trending Now**) and exports to JSON, CSV, Excel or HTML. The run's `SUMMARY` record lists the comparisons made, the anchor, any filler removed and anything that failed. ### Pricing You pay per row returned. There is no charge for Apify platform usage on top. | Row | Free and Starter | Scale | Business | |---|---|---|---| | Trends row | $1 per 1,000 | $0.75 per 1,000 | $0.55 per 1,000 | Plus $0.00005 per run start. **Apify's free $5 monthly credit covers about 5,000 rows.** Free-plan runs stop at 500 rows each; any paid Apify plan removes the cap. What a row is depends on the output format: | Output format | One row is | Example | |---|---|---| | `series` (default) | one search term, with its whole timeline, regions and related queries inside | 10 terms = 10 rows = $0.01 | | `tidy` | one date, one region or one related query | 10 terms × 53 weeks = 530 rows = $0.53 | | Trending Now (either format) | one trending search | 100 trends = $0.10 | **What's free:** trends skipped by `onlyNew`, runs that return nothing because of the input or because nothing is new, and runs where Google Trends can't be read (the run says nothing was charged). A search term Google has no data for at all returns no row, so it costs nothing. To cap a run's spend, set **Maximum cost per run** in the run options, or `maxRows` in the input. ### Limits - Google never publishes search counts. Each value is search interest relative to the highest point in what you asked for: 100 is the peak, 50 is half as popular, 0 means too little data. Region maps are on each term's own scale. Values from different runs are on different scales; compare terms inside one run. - More than 5 terms: the anchor term appears in every comparison, and the ratio of its totals converts one scale into the other; `rawValue` keeps Google's own number. Google rounds each comparison to whole numbers relative to its biggest term, so a giant anchor flattens small terms: pick a term of middling popularity as `anchorTerm`. If the anchor reads 0 to 9 in a comparison, that row's `scaleNote` says its conversion is approximate. - Google rate-limits Trends hard. The Actor spaces requests, backs off on "too many requests", rotates IPs and moves to residential proxies only when it must. A very large request can still run out of time; it then stops with what it has and a message saying what to narrow, instead of failing. - Filler in related queries. For some terms Google pads related lists with stock phrases when it sees an automated client. By default clusters of those are removed and listed in the run's `SUMMARY` record. Turn off `filterNoise` to get Google's lists exactly as returned; a real but generic query can occasionally be removed with them. - Related topics currently come back empty from Google for most terms. The option is there, and the run tells you when Google returned nothing. - Trending Now search volumes are Google's own lower bounds ("20K+" becomes 20000). If the full list is unavailable, the Actor falls back to the public RSS feed (newest 10 per country, with news headlines) and says so. - Up to 50 search terms (100 characters each) and 50 Trending Now countries per run. ### Only new since last run, and schedules Set `trendingCountries`, turn on **Only new trends since the last run** and schedule the Actor, for example every few hours. Each run returns, and charges for, only trends earlier runs of the same setup haven't returned. `onlyNew` applies to Trending Now; term comparisons always return fresh numbers. Set up a schedule under **Schedules** in Apify Console. ### Integrations: API, n8n, Make and AI agents **API.** Run it and get the rows back in one call: ```bash curl -X POST "https://api.apify.com/v2/acts/locaihost~google-trends/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \ -H "Content-Type: application/json" \ -d '{"searchTerms": ["coffee", "tea", "matcha"], "geo": "US", "includeRelatedQueries": true}' ``` Apify's API clients for Python and JavaScript work the same way. **n8n, Make, Zapier, Google Sheets, Slack, webhooks.** Apify's built-in integrations send each run's dataset wherever you need it, for example new trending searches into a Slack channel. **AI agents (MCP).** Add this Actor to Claude, Cursor or any MCP client with `https://mcp.apify.com/?tools=locaihost/google-trends`, then ask something like *"Which of these 12 drinks gained the most US search interest over the past year?"* ### FAQ #### How much does it cost to scrape Google Trends? $1 per 1,000 rows on the Free and Starter plans, less on Scale and Business. In the default series format one row is one term with its whole timeline, so 10 terms cost $0.01. Apify's free $5 monthly credit covers about 5,000 rows. #### Can I use it through the API or from Python? Yes. Use the `run-sync-get-dataset-items` call above, or Apify's Python and JavaScript clients. Every run's data is also available as JSON, CSV or Excel from its dataset. #### Can I use it from an AI agent? Yes. Through the Apify MCP server (`https://mcp.apify.com/?tools=locaihost/google-trends`) any MCP client can call it with a list of terms and read the rows back. #### Is it legal to scrape Google Trends? The Actor reads Google Trends' public data paths, the ones its robots.txt allows, without logging in, and collects no personal data. You are responsible for how you use the results, including Google's terms. When you publish the numbers, cite them as `Data source: Google Trends (https://www.google.com/trends)`, as Google asks. #### Can I compare more than 5 terms? Yes, up to 50 in one run, on one scale, chained through an anchor term (see Limits). #### Why do my numbers differ slightly from trends.google.com? Google samples searches, so the same query can return slightly different values from one request to the next. Use the `trendsUrl` on each row to compare. #### Why are some fields empty? `regions`, `relatedQueries` and `relatedTopics` are filled only when you turn them on (only the timeline is on by default). When Google has no data for one part of a term (for example no region map for a small term), that part is `null` and the row's `notes` say why. ### More from locaihost data - [People Also Ask questions](https://apify.com/locaihost/people-also-ask): the questions Google shows for the terms that are trending. - [YouTube transcripts](https://apify.com/locaihost/youtube-transcripts): what videos on a rising topic actually say. - [TikTok trends](https://apify.com/locaihost/tiktok-trends): trending hashtags, videos and top ads on TikTok, by country. - [App Store and Google Play reviews](https://apify.com/locaihost/app-stores): ratings and reviews for the apps behind a trend. ### Did it help? If this saved you time, a quick rating on the Store helps other people find it. ### Support Something not working, or a field you need? Open an issue on the **Issues** tab: we answer issues within 24 hours. # Changelog This Actor's version history is a separate document: https://apify.com/locaihost/google-trends/changelog.md # Actor input Schema ## `startUrls` (type: `array`): Paste links copied from trends.google.com, e.g. https://trends.google.com/trends/explore?q=coffee,tea\&geo=US. The terms, location, time range, category and search type are read from the link. Trending Now links (trends.google.com/trending?geo=GB) add that country's trending searches. Settings in the link win over the fields below; the fields fill in anything the link leaves out. One run uses the first link's location and time range. ## `searchTerms` (type: `array`): Words or phrases to look up, e.g. "coffee", "iphone 17". Up to 5 are compared directly, like on trends.google.com. Add more (up to 50) and they are put on one shared 0–100 scale through an anchor term, so you can rank them all against each other. ## `geo` (type: `string`): Leave empty for worldwide. A country name or code ("United States", "US", "Germany", "DE"), a region code ("US-CA", "GB-SCT") or a US metro ("US-NY-501"). ## `timeRange` (type: `string`): Google picks the step from the range: minutes or hours up to a week, days up to 9 months, weeks up to 5 years, months beyond. Set a start and end date below for any other window. ## `startDate` (type: `string`): YYYY-MM-DD, from 2004-01-01. With an end date, it replaces the time range. ## `endDate` (type: `string`): YYYY-MM-DD. Empty means today. ## `category` (type: `string`): Narrows an ambiguous term, e.g. "jaguar" in Autos & Vehicles. For any of Google's ~1,400 subcategories, put its id in Category id. ## `categoryId` (type: `integer`): Any Google Trends category id, e.g. 916 for Coffee & Tea. Overrides Category. ## `searchType` (type: `string`): Which Google search the interest is measured on. ## `includeTimeline` (type: `boolean`): The 0–100 timeline for each term. ## `includeRegions` (type: `boolean`): Where each term is searched most: countries (worldwide), regions or states (inside a country). Each term's map is on its own 0–100 scale. ## `regionLevel` (type: `string`): Automatic means countries for a worldwide search and regions inside a country. ## `includeLowVolumeRegions` (type: `boolean`): Also list regions where Google has too little data to give a value (they come back as 0). ## `includeRelatedQueries` (type: `boolean`): Top and rising searches people make with each term (up to 25 of each). ## `includeRelatedTopics` (type: `boolean`): Top and rising topics. Google currently returns these lists empty to automated tools for most terms; the run says so when that happens. ## `filterNoise` (type: `boolean`): Google sometimes pads related lists with stock phrases unrelated to the term ("gardening" and "hospitals" for "tea"). On: clusters of those are removed and listed in the run's SUMMARY. Off: Google's lists exactly as returned. ## `anchorTerm` (type: `string`): With more than 5 search terms, every comparison includes this term so they can be put on one scale. Empty = your first term. Pick one of medium popularity: one far smaller than the rest gives rougher numbers. ## `outputFormat` (type: `string`): Each dataset row is one charged result. One row per term is cheapest. One row per data point loads straight into a spreadsheet or database, but a 12-month weekly timeline is 53 rows per term. ## `maxRows` (type: `integer`): Stop after this many rows. 0 = no limit. ## `trendingCountries` (type: `array`): Today's trending searches for each country ("US", "United Kingdom", "IN"): every trend Google lists, with search volume, growth, start time, category and the queries behind it. ## `trendingWindow` (type: `string`): How far back the Trending Now list goes. ## `trendingCategory` (type: `string`): Only trends in this category. ## `onlyActiveTrends` (type: `boolean`): Skip trends Google marks as ended. ## `maxTrendsPerCountry` (type: `integer`): 0 = every trend Google lists (often several hundred a day in big countries). ## `onlyNew` (type: `boolean`): For daily alerts: return only trends this setup has not returned before, so a schedule never pays twice for the same trend. Remembered per set of countries and window. ## Actor input object example ```json { "searchTerms": [ "coffee", "tea", "matcha", "energy drink", "kombucha", "yerba mate" ], "geo": "US", "timeRange": "past-12-months", "category": "all", "searchType": "web", "includeTimeline": true, "includeRegions": false, "regionLevel": "auto", "includeLowVolumeRegions": false, "includeRelatedQueries": false, "includeRelatedTopics": false, "filterNoise": true, "outputFormat": "series", "maxRows": 0, "trendingCountries": [ "US", "GB", "IN" ], "trendingWindow": "past-24-hours", "trendingCategory": "all", "onlyActiveTrends": false, "maxTrendsPerCountry": 10, "onlyNew": false } ``` # Actor output Schema ## `terms` (type: `string`): One row per search term with its timeline, regions and related queries (series format). ## `timeline` (type: `string`): One row per term and date (tidy format). ## `trending` (type: `string`): One row per trending search. ## `summary` (type: `string`): Comparisons made, anchor used, filler removed, failures and cost. # 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": [ "coffee", "tea", "matcha" ], "geo": "US", "trendingCountries": [ "US" ], "maxTrendsPerCountry": 10 }; // Run the Actor and wait for it to finish const run = await client.actor("locaihost/google-trends").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": [ "coffee", "tea", "matcha", ], "geo": "US", "trendingCountries": ["US"], "maxTrendsPerCountry": 10, } # Run the Actor and wait for it to finish run = client.actor("locaihost/google-trends").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": [ "coffee", "tea", "matcha" ], "geo": "US", "trendingCountries": [ "US" ], "maxTrendsPerCountry": 10 }' | apify call locaihost/google-trends --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,locaihost/google-trends" } } } ``` 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/TNA6SaBPSd9Pm4NgH/builds/0wJkOqdQbRGTM1dwR/openapi.json