logo
EN

Google Trending Now

The full list of searches trending on Google in any country or state over the past 4, 24 or 48 hours or 7 days: one row per trend with approximate search volume, growth, start and end time, categories and related searches. Data from Google Trends' public Trending now page; this app is not an official Google product

Developer
Pricing
$0.0004 / Trending search returned
Last updated
2026-11-17

Overview

Find out what people are searching for on Google right now, in any country or in a single state. You get the full trending list Google Trends shows for the past 4, 24 or 48 hours or the past 7 days: often several hundred searches for a large country in a day. Each result is one trending search with Google's rounded search count, how fast it grew, when it started and whether it is still trending, its categories and the related searches Google groups under it, which usually tell you why it is trending.

Content teams, newsrooms, marketers and SEO specialists use it to catch topics while they are rising, to watch one field such as sports or finance, and to compare what different countries or states care about today.

Data notes

  • Data comes from the trending searches that Google Trends publishes openly and that anyone can view for free on the Google Trends website. This app provides a collection and structuring service: it turns those lists into rows that programs and AI assistants can use directly. The fee covers servers, network and maintenance, is counted per trend returned and is not a fee for the data itself. This app is not an official Google product and is not affiliated with Google; Google Trends is the authoritative source. Credit "Google Trends" when you publish the data.
  • Results follow Google's own order on the Trending now page, most relevant first; "Rank" is the position in that full list. Searches are counted from the moment a trend starts, so a new trend can show a modest number such as 200+ while still climbing.
  • Times are in UTC. Lists are shared between runs for up to ten minutes, so two runs a few minutes apart can return the same trends.
  • If Google's page cannot be read for a moment, a region returns only the 10 searches that most recently started trending, without growth, end time or categories, and says so in "Status details".
  • Not covered: news articles for each trend, interest over time for a keyword, and mainland China, which Google Trends does not cover.

What the results look like

Each result is one search trending in one requested country or state.

RegionRankTrending searchApprox. searchesGrowth (%)Started trendingCategoriesRelated searches
US2emergency alert system200K+10002026-11-16T20:50:00+00:00Law and Governmentemergency alert system / fema test / fema / nationwide blackout
US-CA1chargers vs ravens200K+10002026-11-16T19:50:00+00:00Sportschargers vs ravens / chargers / ravens vs chargers / ravens
US-CA7apple outage10K+10002026-11-17T17:40:00+00:00Technologyapple outage / apple / apple down / is apple pay down

Plus other fields such as Region name, Searches (at least), Stopped trending, Still trending, Google Trends page and Status.

Use cases

  • To pick timely content topics, take the past 4 hours, sort by "Searches (at least)" and read "Related searches" to see what each story is about.
  • To follow one field, choose a category such as Sports or Business and Finance and compare several countries in one run.
  • To see what is still rising rather than what has passed, keep rows where "Still trending" is true.
  • To track trends through the day, run every 10–30 minutes and keep new values of "Trend key"; "Started trending" and "Stopped trending" show how long each topic lasted.

Scope and boundaries

Up to 50 region codes per run, one Google Trends list per region and time window (4, 24, 48 or 168 hours); up to 3,000 trends per region, 100 by default, in Google's own order. Categories are filtered from the same list. No news articles and no search-interest history for keywords. To protect the shared connection, new lists are read at about 12 per minute, and lists are shared across runs for 10 minutes, so runs within the same 10 minutes return the same trends. If Google's page cannot be read, a region falls back to Google's latest 10 trends and says so in status_text. Billed per trend returned; regions without trends get a row but are not billed. The fee covers fetching and structuring the public lists, not the data itself

  • Good for
  • You want to know what people in a country or state are searching for right now or over the past day or week, for content ideas, news monitoring or timely marketing
  • You want trending searches of one kind only, e.g. Sports or Business and Finance: set categories
  • You compare several countries or states in one run: list them all in geos
  • You monitor trends over the day: run every 10–30 minutes and collect the rows; trend_key stays the same for the same trend
  • Do not use for
  • You need news articles for each trend: this app returns related searches, not news
  • You need how interest in a keyword changed over weeks or months (interest over time): this app does not provide it
  • You need trends for mainland China: Google Trends has no trending list for CN

Failure handling

Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.

  1. 1Every requested region gets at least one row. `status` says what happened: ok (one row per trend, billed via `billed_trends` = 1), no_trends, invalid_geo, rate_limited, failed; only ok rows are billed
  2. 2rate_limited means Google is briefly limiting our servers: retry after the minutes given in status_text
  3. 3invalid_geo: use a two-letter country code (US) or a state code (US-CA)
  4. 4When only Google's latest 10 trends could be read instead of the full list, ok rows say so in status_text and have no growth, end time or categories

Input

Parameters required to call this App, generated from the input.schema in manifest.json.

  • Countries or statesgeosRequiredarray<string>
    Region codes, 1–50: a two-letter country code (US, GB, JP, DE, IN, BR) or a state / province code (US-CA, GB-SCT, DE-BY, JP-13). Each region gets its own trending list.
    Itemsup to 50 itemsDefaultUSExample["US"]
  • Time window (hours)hoursOptionalinteger
    Searches that trended in the past 4, 24 or 48 hours, or 168 (7 days). Longer windows list many more searches.
    Default24
  • CategoriescategoriesOptionalarray<string>
    Only return searches in these Google Trends categories; empty = all categories.
    Default
  • Max trends per regionmax_trends_per_geoOptionalinteger
    At most this many searches per region, in Google's own order (most relevant first). A large country can list several hundred searches in 24 hours and a few thousand in 7 days.
    Range1–3000Default100

Output

Field structure of a single record, generated from the output.schema in manifest.json.

  • Trend keytrend_keystring
    Region | keyword | start time: stays the same for the same trend across runs and time windows, so repeated runs can be de-duplicated on it. Rows without trends use region | status
    ExampleUS|nsa|2026-11-17T10:50:00+00:00
  • Regiongeostring
    The requested region code: a country (US) or a state / province (US-CA)
    ExampleUS
  • Region namegeo_namestring
    Name of the region as Google Trends shows it
    ExampleUnited States
  • Rankrankinteger
    Position in the region's full trending list, in Google's own order (most relevant first). With categories selected, ranks keep their place in the full list, so gaps are normal
    Example1

Sample data

Generated from output.schema. Fields without a sample value use structural placeholders.

output.example
{
  "trend_key": "US|nsa|2026-11-17T10:50:00+00:00",
  "geo": "US",
  "geo_name": "United States",
  "rank": 1,
  "keyword": "nsa",
  "approx_traffic": "200K+",
  "traffic_min": 200000,
  "growth_pct": 1000,
  "started_at": "2026-11-17T10:50:00+00:00",
  "ended_at": "2026-11-16T23:40:00+00:00",
  "is_active": true,
  "categories": "<categories>",
  "related_queries": "<related_queries>",
  "related_queries_count": 29,
  "trends_url": "https://trends.google.com/trends/explore?q=nsa&geo=US&date=now%201-d",
  "source_url": "https://trends.google.com/trending?geo=US&hours=24&hl=en-US",
  "data_source": "Google Trends",
  "time_window_hours": 24,
  "fetched_at": "2026-11-17T18:44:56+00:00",
  "status": "ok",
  "status_text": "Trending search",
  "billed_trends": 1
}

Integration

This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.

With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.

Client config

Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.

mcpServers config
{
  "mcpServers": {
    "octoparse_datahub": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=MagicData/google-trending-now",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

Let AI set it up for you

Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)

detail.access.mcp.composeHint

Pricing

Trending search returned

Metered by summing the output field billed_trends. Failed runs are not charged.

$0.0004/ Trending search returned

Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.

View credits

Try it now

Fill in the parameters and run. Results come from a real call.

Example
Parameters are validated against input.schema before submission
$0.0004 / Trending search returned