Google Trends [Just 💰$0.49] — Interest & Related

What does Google Trends do?

Google Trends turns trends.google.com into structured data. Pull live trending searches with their search volume and growth, or analyse any keyword — interest over time, interest by region, and related & rising queries. Run the same query consistently over time, or track what is trending right now.

How to use this actor

• 👉 Register for a free Apify account — no credit card required.
• 🎉 Just click Sign up free on Apify → and complete a quick signup.
• 💰 A free Apify account includes $5 in monthly credits — enough to test this actor.
• ⏳ Scrape during the free trial, with no commitment or upfront payment required.

Key features

• 📦 Compact mode — compact mode — core fields only, ideal when you're feeding an LLM or building a comparison sheet across many companies.
• 🧹 Empty-field stripping — drop null, empty-string, and empty-array fields from each record before push. Smaller payloads for AI agents and dashboards that already handle missing fields gracefully.
• 🎯 Batch searches — pass ["term1", "term2"] for query, location, or city to batch multiple searches in one run — shared dedup state, single dataset, one Actor-Start charge instead of N.
• ♻️ Incremental mode — recurring runs emit only listings whose ratings, reviews, or metadata changed — track reputation movement over time without re-processing the universe. Saves 80–95% on monitoring runs.
• 📤 Export anywhere — Download the dataset as JSON, CSV, or Excel from the Apify Console, or stream live via the Apify API and integrations (Make, Zapier, Google Sheets, n8n, …).
• 🔌 MCP connectors — export your results into Notion via Apify's MCP connectors — a clean run-summary page, no glue code. Opt-in via the App connector field; deterministic field-mapping, no AI. Built on Apify's connector framework, so more destinations open up as their catalog grows.

What data can you extract from trends.google.com?

Each result includes Core keyword fields (keyword, timeRange, category, portalUrl, trendsShareUrl, recentTrend, recentChangePercent, and error, and more) and extended fields (detailFetched). In standard mode, all fields are always present — unavailable data points are returned as null, never omitted. In compact mode, only core fields are returned.

Input

The main inputs are a search keyword, an optional location filter, and a result limit. Additional filters and options are available in the input schema.

Key parameters:

• keywords — Search terms to analyze. Each returns interest over time, interest by region, and related + rising queries. Billed per keyword. Leave empty to scrape Trending Now instead.
• geo — Two-letter country code, e.g. US, DK, JP. Applies to both keyword analysis and the Trending Now feed. (default: "US")
• timeframe — Window for keyword analysis (ignored by the Trending Now feed). (default: "today 12-m")
• maxResults — Maximum total results (0 = unlimited). (default: 25)
• compact — Core fields only (for AI-agent/MCP workflows). (default: false)
• incrementalMode — Compare against previous run state. stateKey is optional — defaults to a key derived from your search inputs so different filter sets never share state. (default: false)
• googleTrendsSessionCookie — Optional. Cookie header from a signed-in Google Trends browser session, used only to unlock Related topics. Without it every other field is still returned. Never stored or shared.
• ...and 20 more parameters

Input examples

Basic search — Keyword-driven search with a result cap.

→ Full payload per result — all standard fields populated where the source provides them.

{
  "query": "US",
  "maxResults": 50
}

Incremental tracking — Only emit keywords that changed since the previous run with this stateKey.

→ First run builds the baseline state. Subsequent runs emit only records that are new or whose tracked content changed. Set emitUnchanged: true to include unchanged records as well.

{
  "query": "US",
  "maxResults": 200,
  "incrementalMode": true,
  "stateKey": "us-tracker"
}

Compact output for AI agents — Return only core fields for AI-agent and MCP workflows.

→ Small payload with the most important fields — ideal for piping into LLMs without token overhead.

{
  "query": "US",
  "maxResults": 50,
  "compact": true
}

Output

Each run produces a dataset of structured keyword records. Results can be downloaded as JSON, CSV, or Excel from the Dataset tab in Apify Console.

Example keyword record

{
  "keyword": "msft stock",
  "category": 3,
  "portalUrl": "https://trends.google.com/trends/explore?q=msft%20stock&geo=US",
  "trendsShareUrl": "https://trends.google.com/trends/explore?q=msft%20stock&geo=US",
  "recentTrend": "rising",
  "recentChangePercent": 500,
  "geo": "US",
  "searchVolume": 100000,
  "startedAt": "2026-07-29T20:00:00.000Z",
  "breakdownQueries": [
    "msft stock",
    "msft",
    "microsoft stock",
    "microsoft stock price",
    "microsoft earnings",
    "... 1 more items"
  ],
  "newsArticleIds": [
    4753682660,
    4753686227,
    4757079927,
    4756989338,
    4757379943,
    "... 7 more items"
  ],
  "listingId": "60b68797f494552189fa53346c1a5ef697565d3e5ed81014529eaf67341ab14a",
  "searchQuery": "US",
  "contentQuality": "serp_only",
  "detailFetched": false,
  "scrapedAt": "2026-07-30T14:37:39.756Z",
  "source": "trends.google.com"
}

Incremental fields

When incremental mode is on, each record also carries:

• changeType — one of NEW, UPDATED, UNCHANGED, REAPPEARED, EXPIRED. Default output covers NEW / UPDATED / REAPPEARED; set emitUnchanged: true or emitExpired: true to opt into the others.

How to scrape trends.google.com

1. Go to Google Trends in Apify Console.
2. Enter a search keyword and optional location filter.
3. Set maxResults to control how many results you need.
4. Click Start and wait for the run to finish.
5. Export the dataset as JSON, CSV, or Excel.

Use cases

• Extract keyword data from trends.google.com for market research and competitive analysis.
• Monitor new and changed keywords on scheduled runs without processing the full dataset every time.
• Feed structured data into AI agents, MCP tools, and automated pipelines using compact mode.
• Export clean, structured data to dashboards, spreadsheets, or data warehouses.

How much does it cost to scrape trends.google.com?

Google Trends uses pay-per-event pricing. You pay a small fee when the run starts and then for each result that is actually produced.

• Run start: $0.001 per run
• Per trending search (primary event): $0.00049

You are billed only for the events your run actually triggers. Prices below are the Free plan tier.

Event	Price (Free tier)	Charged when
Actor Start	$0.001 (one-time)	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Trending search (primary)	$0.00049	One trending term from the Trending Now feed, with search volume, growth and related searches.
Keyword analyzed	$0.00299	One keyword: interest over time, interest by region, and related + rising queries. Charged only when a time series is actually returned.

Example costs (primary event only — other events above add cost when they fire):

• 10 results: $0.0059
• 25 results: $0.013
• 100 results: $0.05
• 200 results: $0.099
• 500 results: $0.25

Example: recurring monitoring savings

These examples compare full re-scrapes with incremental runs at different churn rates. Churn is the share of keywords that are new or whose tracked content changed since the previous run. Actual churn depends on your query breadth, source activity, and polling frequency — the scenarios below are examples, not predictions.

Example setup: 100 keywords per run, daily polling (30 runs/month). Costs scale linearly with the number of keywords.

Numbers below are for the primary Trending search event. Other events (Keyword analyzed) are billed separately when they fire.

Churn rate	Full re-scrape run cost	Incremental run cost	Savings vs full re-scrape	Monthly cost after baseline
5% — stable niche query	$0.05	$0.00345	$0.05 (93%)	$0.10
15% — moderate broad query	$0.05	$0.00835	$0.04 (83%)	$0.25
30% — high-volume aggregator	$0.05	$0.02	$0.03 (69%)	$0.47

Full re-scrape monthly cost at the same cadence: $1.50. First month with incremental costs $0.15 / $0.29 / $0.51 for the 5% / 15% / 30% scenarios because the first run builds baseline state at full cost before incremental savings apply.

Platform usage is included in the per-result fee shown above.

FAQ

How many results can I get from trends.google.com?

The number of results depends on the search query and available keywords on trends.google.com. Use the maxResults parameter to control how many results are returned per run.

Does Google Trends support recurring monitoring?

Yes. Enable incremental mode to only receive new or changed keywords on subsequent runs. This is ideal for scheduled monitoring where you want to track changes over time without re-processing the full dataset.

Can I integrate Google Trends with other apps?

Yes. Google Trends works with Apify's integrations to connect with tools like Zapier, Make, Google Sheets, Slack, and more. You can also use webhooks to trigger actions when a run completes.

Can I use Google Trends with the Apify API?

Yes. You can start runs, manage inputs, and retrieve results programmatically through the Apify API. Client libraries are available for JavaScript, Python, and other languages.

Can I use Google Trends through an MCP Server?

Yes. Apify provides an MCP Server that lets AI assistants and agents call this actor directly. Use compact mode and excludeEmptyFields to keep payloads manageable for LLM context windows.

Is it legal to scrape trends.google.com?

This actor extracts publicly available data from trends.google.com. Web scraping of public information is generally considered legal, but you should always review the target site's terms of service and ensure your use case complies with applicable laws and regulations, including GDPR where relevant.

Your feedback

If you have questions, need a feature, or found a bug, please open an issue on the actor's page in Apify Console. Your feedback helps us improve.

You might also like

• Elpris — Danish Electricity Prices & Suppliers — Scrape every electricity product Danish suppliers report to elpris.dk — supplier, price bands.
• Transfermarkt [Just 💰$0.5] — football market values — 💰 $0.5 per 1,000 records. Scrape transfermarkt.com — player market values with full history ·.

Getting started with Apify

New to Apify? Create a free account with $5 credit — no credit card required.

1. Sign up — $5 platform credit included
2. Open this actor and configure your input
3. Click Start — export results as JSON, CSV, or Excel

Need more later? See Apify pricing.

Related topics (optional): supplying a Google session cookie

Interest over time, interest by region, and related/rising queries are returned on every run with no login. Related and rising topics are the one exception: Google only serves them to a signed-in browser session, so they are opt-in. Leave the cookie field empty and every other field is still returned — related topics simply report AUTH_REQUIRED.

To enable them, paste a Google Cookie request-header value into the secret input googleTrendsSessionCookie.

Use a dedicated Google account you own and are authorised to use — not your main account. A session cookie is an account credential; treating it like one keeps your primary account out of scope. A dedicated account reduces the blast radius but does not guarantee Google cannot correlate it with your other accounts (via IP, device, recovery details, or behaviour).

How to get the cookie

1. In Chrome, sign in to the dedicated account and open https://trends.google.com/trends/explore?q=coffee&geo=US.
2. Open DevTools (F12) → Network tab. Refresh the page.
3. Click the first trends.google.com request in the list.
4. Under Request Headers, find the cookie: header and copy its entire value (one long line, everything after cookie: ).
5. Paste that value into the googleTrendsSessionCookie field. It is stored as a secret — masked in the input, never written to the dataset or logs.

Good to know

• The cookie is used only in the actor's browser step for related topics; it is never sent through the proxy or attached to any other request.
• Cookies expire — if related topics start returning AUTH_REQUIRED, refresh the cookie by repeating the steps above.
• Deleting your copy of the cookie does not sign the browser out; it only removes that one copy. To revoke it, sign the account out in the browser you copied it from.

Disclaimer

This actor accesses only publicly available data on trends.google.com. You are responsible for how you use the extracted data — in particular any personal information such as names, phone numbers, or email addresses — and for complying with Google Trends's terms of use, applicable data-protection law (including the GDPR where it applies), and the anti-spam rules of your jurisdiction.

This actor is not affiliated with, endorsed by, or connected to Google Trends.

Search keywords

google trends scraper, google trends api, apify google trends, google trends data extraction, trends.google.com scraper, trends.google.com data, trends.google.com api.