Google Trends Scraper

Google Trends Scraper exports current country-level Trending Now searches with feed ranks, approximate traffic labels and news article context. Save a bounded snapshot to an Apify dataset for editorial planning, market research or a content briefing. This Actor does not provide historical keyword interest or monthly search volumes.

Quick start

1. Choose a primary country and clear Additional country codes for a single-country snapshot.
2. Set a small total row limit and start the Actor.
3. Open the dataset and download JSON, CSV or Excel, or retrieve it through the API.

{
  "mode": "trending_now",
  "geo": "US",
  "geos": [],
  "maxItems": 10,
  "proxyConfiguration": { "useApifyProxy": false }
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Track Google Trends for Japan with localized context
• Compare trending searches across US, UK, and Germany
• Get today's Google Trends for the United States

What you get

One row per current trending search in a selected country, with its title, country feed position, source URL and collection time. Available traffic estimates, original traffic labels and publication times can be null. Nested article entries provide news context rather than full article text or independent related-keyword analysis.

Who is it for?

• News and content editors assembling source-linked topic briefs from current country feeds.
• Market researchers reviewing which topics appear in their selected markets at collection time.
• Regional analysts keeping feed positions and country context with exported observations.
• Data engineers passing snapshots into their own comparison or reporting workflows.

How you can use the data

• Build a small US topic brief. Use the existing primary-US input with additional countries cleared and ten total rows. Retain query, geo, sourceUrl and available article links before deciding what warrants editorial follow-up.
• Review several countries under one shared cap. Use the existing US, GB and DE example and keep country labels with every row. Countries run in input order, so earlier countries can exhaust the total limit before later markets are reached.
• Keep Japanese feed content distinct from a locale label. Use the existing Japan example and retain the requested reporting label alongside the country. Changing hl does not translate the feed or select its language.
• Prepare your own evidence-based comparison. Keep searchVolumeLabel, available numeric traffic, feed rank and collection time. Treat traffic as approximate rather than monthly volume, and recognize that relatedQueries and trendBreakdown repeat up to ten available news headlines rather than search-keyword suggestions. Add any comparison or briefing logic in your own tool.

Input settings

Setting	JSON key	Behavior
Mode	mode	Only trending_now.
Country code	geo	Primary two-letter country. Form default US.
Additional country codes	geos	Added after the primary country. At most 25 distinct countries total.
Locale	hl	Reporting label only. Default en-US. Does not translate the feed.
Maximum trends	maxItems	Total row limit, 1–500. Form/schema default 20.
Maximum run time	maxRunSeconds	Optional 35–270 second budget, including shutdown time.
Proxy configuration	proxyConfiguration	Existing proxy editor. Form defaults to no proxy. See field help for API omission behavior.

The form prefills additional countries with US, GB and DE. Omitted geos adds none. Countries are processed in order, with duplicate country codes removed. If maxItems never reaches the runtime, its fallback is 25. Use explicit values for reproducible API requests. There are no category, date-range or custom sorting controls.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

One row represents one trending search in one country. rank is its original position in that country's feed, not a cross-country ranking or a sort by traffic.

Illustrative shape only, not a current trend observation:

{
  "mode": "trending_now",
  "query": "Example topic",
  "title": "Example topic",
  "rank": 1,
  "geo": "US",
  "hl": "en-US",
  "observedAt": null,
  "traffic": null,
  "searchVolumeLabel": null,
  "trendBreakdown": [],
  "relatedQueries": [],
  "articles": [],
  "sourceUrl": "https://trends.google.com/trending/rss?geo=US",
  "scrapedAt": "2026-10-24T00:00:00.000Z"
}

Field	Meaning
mode	Always trending_now.
query, title	Trend title supplied by the feed.
rank, geo	One-based feed position and requested country.
hl	Input locale label, not a language selection.
observedAt	Feed publication time, or null.
traffic, searchVolumeLabel	Parsed numeric approximation and original traffic label. Either may be null. A label such as 10K+ is not an exact count or monthly volume.
trendBreakdown, relatedQueries	The same first ten available article headlines. These are news context, not related-keyword analysis.
articles	Feed-provided news entries with title, url, source and snippet. Individual values can be null. Full article text is not collected.
sourceUrl, scrapedAt	Country feed URL and row creation time.

The run's key-value store also contains a best-effort RUN_SUMMARY with saved/charged counts, failed countries and warnings. It is separate from the dataset. A storage failure may prevent a summary from being available.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

Pay-per-event pricing charges start once when collection begins and item for each saved trend row. A failed run can still have a start charge and charges for rows already saved. No paid error or status rows are emitted.

Keep the total row cap and country list small for a focused snapshot. See the live Pricing tab for current rates and plan discounts.

Tips for best results

• Clear extra country prefills for a single-market snapshot. Use explicit country lists and total caps in API requests.
• Allow space for later countries in the shared cap. Feed order and input-country order can shape which markets reach the dataset.
• Keep the original traffic label with any numeric approximation. Neither is an exact count or monthly search volume.
• Treat hl as a reporting label. It does not translate or choose feed language.
• Check status and the available summary before comparing markets. Saved rows alone do not establish that every country completed.

Limits and caveats

Feeds can expose fewer rows than requested, and available countries and article context depend on Google. Countries are processed in order, with duplicates removed. Earlier countries can fill the shared cap before later ones are reached. A successful run does not guarantee every requested country completed.

Individual country failures can leave useful rows from other countries. The current implementation fails when no rows are saved or the deadline is reached, while already-saved rows remain available. RUN_SUMMARY is best effort and can be unavailable after a storage failure.

Only current country-level Trending Now feeds are supported. There is no historical keyword interest, monthly search volume, subregion, category, date-range or custom sorting feature. Feed rank is local to each country rather than a cross-country ranking or traffic sort. Related-query and breakdown arrays contain news headlines, not independent keyword analysis, and article bodies are not collected.

Optional fields can be null or empty. Locale is an output reporting label rather than feed translation. No Google login is used, private personalized data is outside scope, and this is not an official Google API. Comparisons and reports require your own downstream workflow.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~google-trends-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "mode": "trending_now",
  "geo": "US",
  "geos": [],
  "maxItems": 10,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/google-trends-scraper').call({
  "mode": "trending_now",
  "geo": "US",
  "geos": [],
  "maxItems": 10,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/google-trends-scraper').call(run_input={'mode': 'trending_now', 'geo': 'US', 'geos': [], 'maxItems': 10, 'proxyConfiguration': {'useApifyProxy': False}})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API and integrations notes

cURL — starts a run asynchronously. Poll the returned run ID until terminal, then read its defaultDatasetId with the dataset items API.

MCP and AI agents

You can ask your AI assistant to collect data with Google Trends Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Google Trends Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/google-trends-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Google Trends Scraper by Fetch Cat, or give it the identifier fetch_cat/google-trends-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Google Trends Scraper to collect up to 5 current Trending Now rows for the US only, clearing additional countries. Show feed ranks, original traffic labels and available article links without claiming monthly search volumes.”
• “Collect up to 9 current Trending Now rows in total for the US, Great Britain and Germany, in that order. Group the saved rows by country and flag any failed or unreached market rather than assuming equal samples.”
• “Retrieve up to 5 current Trending Now rows for Japan only, clearing additional countries and using en-US as the reporting label. Keep source links and available news headlines without translating the feed or calling those headlines related search queries.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Is this a Google Trends API alternative?

It provides programmatic access to country-level Trending Now snapshots through Apify. It does not offer keyword interest over time, historical trends or the full Google Trends product.

Can I export Google Trends data to CSV or JSON?

Yes. Use the dataset export tools or API after the run. Nested article arrays are easiest to retain in JSON.

Does changing hl change the result language?

No. It labels output for your reporting workflow. Content comes from the selected country feed.

Why are article fields or traffic values missing?

Those values are optional in the source. Missing values remain null or empty arrays rather than being inferred. relatedQueries contains news headlines, not independent keyword suggestions.

What if no results are saved?

Check the chosen country, run status and available run summary. The current Actor reports a failed run when it saves no rows. That alone does not establish that the country has no trends. A source response or extraction problem can also cause it.

Which tool should I use for historical keyword research?

This Actor is limited to current country feeds. Compare a dedicated keyword-interest tool's documented scope before choosing it. Do not interpret this Actor's approximate traffic labels as monthly search volume.

Related Actors

• Google News Scraper — Research news beyond the trend's accompanying articles.
• Google Ads Transparency Scraper — Research public advertising alongside market topics.
• Google Autocomplete Scraper — Collect search suggestions rather than trend traffic labels.
• Bing Search Results Scraper — Collect ranked Bing web results with titles and snippets for supporting topic research.
• DuckDuckGo Search Results Scraper — Gather related web search results.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥