Google Search Trends API avatar

Google Search Trends API

Pricing

from $0.23 / result

Go to Apify Store
Google Search Trends API

Google Search Trends API

Collects Google Trends Trending Now rows by country, time window, category, and sort order. Returns search volume, growth, status, related queries, and trend metadata from the current /trending page.

Pricing

from $0.23 / result

Rating

0.0

(0)

Developer

AgentX

AgentX

Maintained by Community

Actor stats

1

Bookmarked

2

Total users

0

Monthly active users

a day ago

Last modified

Categories

Share

Affiliate disclosure: Apify links marked with the fpr=aiagentapi referral parameter may credit the publisher without changing your Actor price.

Google Search Trends API turns the current Google Trends Trending Now view into one structured dataset record for a selected country, time window, category, and sort order.

  • One default dataset item per successful run, with the exact source view and filter labels.
  • Four time windows, 20 category choices, and four supported sort orders.
  • Nine top-level output fields plus detailed volume, growth, timing, status, and related-query data.
  • Country-level monitoring with source availability documented instead of assumed.

Run a one-result test · View the API

Test risk: a successful test bills Actor Start, variable Actor Usage, and one Result event. A country with no current source rows can finish without a dataset result.

This is a community Actor for the Google Trends Trending Now page. It is not Google’s limited-access Google Trends API Alpha, which serves consistently scaled historical interest data with different coverage and semantics.


Why Choose This API

🌍 Country-focused monitoring

Select a country or region from the Actor input and preserve the matching Trending Now URL in the output. Google’s Trending Now help states that coverage is available for more than 100 countries and regions where applicable; source availability can vary even though the input offers a broader country list.

⏱️ Four current-trend windows

Choose trends that started in the past 4 hours, 24 hours, 48 hours, or 7 days. These are the same time-window concepts documented for Google Trends Trending Now, making the result useful for recurring editorial, research, and monitoring workflows.

🏷️ Category and sort controls

Keep all categories or focus on areas such as Business and Finance, Entertainment, Politics, Shopping, Sports, or Technology. Order the returned rows by relevance, search volume, recency, or title.

📊 Analysis-ready trend details

Each trend includes its rank, query text, search-volume bucket, growth percentage, start and end timing, status, category labels, related queries, article count, and a Google Trends Explore URL. The Actor also summarizes active, ended, and related-query counts at the record level.

Google describes Trending Now as recently surging Google Search queries connected to a newsworthy story or cluster. Search volume is bucketed, and growth is measured against a predicted baseline. Treat these fields as current trend signals rather than exact keyword-planner volumes.


Quick Start Guide

Step 1: Configure the request

Open the Actor input and keep the default scenario:

{
"location": "Canada",
"time_range": "Past 24 hours",
"category": "All categories",
"sort_by": "Relevance"
}

Step 2: Run the Actor

Click Start. A successful run collects the selected Trending Now view and writes one item to the default dataset.

Step 3: Use the result

Open the default dataset to inspect or export the record. JSON preserves the nested trends array. For a flat table, expand that array in your spreadsheet, database, notebook, or workflow tool after export.


Input Parameters

Configuration fields

ParameterTypeRequiredSupported valuesDefault
locationstring/selectYesCountry or region names offered by the inputUnited States
time_rangestring/selectYesPast 4 hours, Past 24 hours, Past 48 hours, Past 7 daysPast 24 hours
categorystring/selectYesAll categories or one of 19 named categoriesAll categories
sort_bystring/selectYesRelevance, Search volume, Recency, TitleRelevance

All four fields are required. Values must match the input options exactly. If Google Trends has no available rows for a selected view, the run can finish without a dataset result rather than returning invented or stale trend data.

Choosing the right filter combination

  • Use Past 4 hours for fast-moving news desks and event monitoring.
  • Use Past 24 hours for a balanced daily snapshot.
  • Use Past 48 hours or Past 7 days when you want a wider discovery window.
  • Use Search volume to surface the largest volume buckets first.
  • Use Recency to prioritize the newest starts.
  • Use Title for deterministic alphabetical review.

The Actor does not expose Trending Now’s “active only” status filter. The output includes both active and ended rows and labels each row so you can filter downstream.


Output Data Schema

One record per successful run

The default dataset contains one top-level item with these fields:

Open the current Actor output

FieldTypeMeaning
processorstringActor URL associated with the result
processed_atstringUTC processing timestamp
locationstringSelected country or region label
time_rangestringSelected started-trending window
categorystringSelected category label
sort_bystringSelected sort order
trends_urlstringGoogle Trends Trending Now URL for the filters
data_countsobjectCounts of trends, active rows, ended rows, and related queries
trendsarrayDetailed trend rows

Abbreviated example output

The values below illustrate the structure; live topics and counts change with Google Trends.

{
"processor": "https://apify.com/agentx/google-search-trends-api",
"processed_at": "2026-07-23T15:30:00+00:00",
"location": "Canada",
"time_range": "Past 24 hours",
"category": "All categories",
"sort_by": "Relevance",
"trends_url": "https://trends.google.com/trending?geo=CA&hl=en-US",
"data_counts": {
"trends": 125,
"active_trends": 42,
"ended_trends": 83,
"related_queries": 390
},
"trends": [
{
"rank": 1,
"trend": "example topic",
"primary_query": "example topic",
"search_volume": 200000,
"formatted_search_volume": "200K+",
"growth_percentage": 900,
"formatted_growth": "900%",
"started_at": "2026-07-23T12:00:00+00:00",
"ended_at": null,
"status": "Active",
"categories": ["Sports"],
"related_queries": ["example topic schedule"],
"article_count": 12,
"explore_url": "https://trends.google.com/trends/explore?geo=CA&hl=en-US&date=now+1-d&q=example+topic"
}
]
}

Some timing or duration fields can be null when a trend is still active or when the source does not provide an end time. article_count is a count only; this Actor does not return article titles or article bodies.


Integration Examples

Actor ID

agentx/google-search-trends-api

REST API

This synchronous endpoint runs the same Canada scenario and returns default dataset items. Replace YOUR_API_TOKEN with an Apify API token.

curl -X POST "https://api.apify.com/v2/acts/agentx~google-search-trends-api/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{"location":"Canada","time_range":"Past 24 hours","category":"All categories","sort_by":"Relevance"}'

Python client

from apify_client import ApifyClient
client = ApifyClient("YOUR_API_TOKEN")
run_input = {
"location": "Canada",
"time_range": "Past 24 hours",
"category": "All categories",
"sort_by": "Relevance",
}
run = client.actor("agentx/google-search-trends-api").call(run_input=run_input)
items = list(client.dataset(run["defaultDatasetId"]).iterate_items())
print(items[0]["data_counts"] if items else "No trends returned")

JavaScript client

import { ApifyClient } from "apify-client";
const client = new ApifyClient({ token: "YOUR_API_TOKEN" });
const input = {
location: "Canada",
time_range: "Past 24 hours",
category: "All categories",
sort_by: "Relevance",
};
const run = await client.actor("agentx/google-search-trends-api").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]?.data_counts ?? "No trends returned");

Apify MCP

In an Apify MCP-enabled client, first use fetch-actor-details for agentx/google-search-trends-api, then pass this payload to call-actor:

{
"actor": "agentx/google-search-trends-api",
"input": {
"location": "Canada",
"time_range": "Past 24 hours",
"category": "All categories",
"sort_by": "Relevance"
},
"waitSecs": 45
}

The call returns the run and storage identifiers. Read the default dataset to retrieve the result. The tool names, Actor ID, input, and wait setting were verified against the current Apify MCP surface on July 23, 2026.


Pricing & Cost Calculator

Pay per event

Review current Store pricing

Each successful run produces one default dataset result and therefore triggers one Result event. The platform also triggers the Actor Start event, while Actor Usage is charged in $0.00001 units according to resource consumption during execution. Prices are expressed in USD per event.

EventFREEBRONZESILVERGOLDPLATINUMDIAMOND
Actor Usage$0.00001$0.00001$0.00001$0.00001$0.00001$0.00001
Actor Start$0.01000$0.01000$0.01000$0.01000$0.01000$0.01000
Result$0.23000$0.22233$0.21467$0.20700$0.20700$0.20700

For example, a successful FREE-tier run with $0.00200 of Actor Usage costs $0.00200 + $0.01000 + $0.23000 = $0.24200. Actual usage depends on the run. A run that exits before writing a result can still incur Actor Start and Actor Usage events. Check the current Store pricing before production scheduling because public prices may change after this documentation date.


Use Cases & Applications

Editorial and newsroom monitoring

Run the same country and time window on a schedule, compare the nested trend arrays, and flag newly active topics. Editors can use query clusters, volume buckets, growth, and start times as prioritization signals while keeping human review in the publishing workflow.

SEO and content discovery

Use category-filtered Trending Now rows to discover emerging terminology and related queries for briefs, FAQs, and timely explainers. These current signals complement, but do not replace, historical interest analysis or keyword-volume research.

Market and brand intelligence

Monitor categories and countries relevant to a market, then join the output with internal campaigns, sales events, or media calendars. The preserved trends_url provides a convenient source view for review.

Research and event analysis

Archive periodic snapshots to study when topics become active, how long they remain elevated, and which related queries appear together. Account for source sampling, bucketed volumes, changing query clusters, and gaps in country availability before drawing conclusions.

Workflow enrichment

Send trend titles into content, shopping, hiring, or video research workflows. Use the related AgentX Actors below when a trend becomes a lead for deeper platform-specific collection.


FAQ

No. This is an independent Apify Actor that structures the current Google Trends Trending Now view. Google’s official Google Trends API remains an Alpha product with limited tester access and focuses on consistently scaled historical search interest rather than this Actor’s Trending Now record.

How fresh is the data?

Google says Trending Now data refreshes on average every ten minutes. The Actor returns what is available for the selected view when the run executes; it does not guarantee that every row changed during the latest refresh.

Does search volume mean an exact query count?

No. Google documents Trending Now search volume as bucketed traffic for the selected timeframe, with growth compared against a predicted baseline. Use the numeric and formatted fields as source-provided trend magnitude signals, not exact advertising keyword volume.

Can I request historical keyword interest?

No. This Actor is for current Trending Now windows up to the past 7 days. For keyword-focused interest workflows, use Google Keyword Trends or apply for Google’s official Alpha API if its historical data model fits your use case.

Not through the current input. The record includes active and ended rows, and each trend has a status value. Filter trends after collection when you need active rows only.

Why can a selected country return no result?

Google documents Trending Now as available in more than 100 countries and regions where applicable, while the Actor input lists a wider set of country names. A selection without current source rows can end without a dataset item. Try a major supported market or a broader time window.

No. Each trend can include an article_count, but this Actor does not return article titles, publishers, URLs, or bodies.

Can I schedule recurring snapshots?

Yes. Use Apify schedules with a saved input. Estimate the Actor Start and Result events for every planned run and set platform spending controls appropriate to your workflow.

OptionBest fitMain trade-off
Google Search Trends API ActorCurrent Trending Now snapshots with structured rows and Apify automationNot historical keyword-interest data; source availability varies
Google Trends API AlphaConsistently scaled historical interest for approved testersLimited-access Alpha with a different data model
Google Trends browser exportOccasional manual CSV, clipboard, or RSS exportManual workflow rather than scheduled Actor output
Google Keyword Trends ActorKeyword-focused interest researchNot a complete Trending Now page snapshot

Why do active rows have null end fields?

An active trend has not ended, so ended_at, ended_timestamp, duration, and duration_seconds may be null. Ended rows can populate those values when the source provides the timestamps.


Trust & Certifications

  • Source-aligned semantics: Filter and field descriptions are checked against Google’s current Trending Now help documentation.
  • Schema-backed output: Input, dataset, output, and pricing documentation are aligned with the current local Actor contract.
  • Transparent limits: The README distinguishes Trending Now from Google’s official Alpha API and documents nullable fields, source availability, and unsupported filters.
  • Public snapshot: On July 23, 2026, the Apify Store showed 4 total users, 1 bookmark, and 100% succeeded runs for the observed public history. These volatile values are not uptime or future-success guarantees.

Google Trends presents anonymized, categorized, and aggregated samples of Google searches. Users remain responsible for their collection frequency, downstream processing, retention, publication, and compliance with applicable laws and platform terms.

Do not interpret a Trending Now result as private-user data, an exhaustive copy of Google Search activity, or proof of causation. Google’s data FAQ notes that Trends data is sampled and can contain statistical noise or omit low-volume searches.

For licensing, compliance review, or custom integration questions, contact @AiAgentApi.


Trend and local context

Cross-platform enrichment


Support & Community

Run a one-result test · View the API


Last Updated: July 23, 2026