The latest Google News articles for any keyword or topic in 84 country and language editions: one row per article with headline, publisher, publish time and Google News link, plus other outlets covering the same story; more than 100 articles per keyword by reading the time range day by day. Data from Google News public RSS feeds; this app is not an official Google product
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
Übersicht
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.
| Region | Rank | Trending search | Approx. searches | Growth (%) | Started trending | Categories | Related searches |
|---|---|---|---|---|---|---|---|
| US | 2 | emergency alert system | 200K+ | 1000 | 2026-11-16T20:50:00+00:00 | Law and Government | emergency alert system / fema test / fema / nationwide blackout |
| US-CA | 1 | chargers vs ravens | 200K+ | 1000 | 2026-11-16T19:50:00+00:00 | Sports | chargers vs ravens / chargers / ravens vs chargers / ravens |
| US-CA | 7 | apple outage | 10K+ | 1000 | 2026-11-17T17:40:00+00:00 | Technology | apple 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.
Anwendungsbereich & Grenzen
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
- Geeignet für
- 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
- Nicht verwenden für
- 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
Fehlerbehandlung
Vom Entwickler deklariertes Fehler- und Wiederholungsverhalten. Wir empfehlen, es bei der Integration in Ihren System-Prompt aufzunehmen.
- 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
- 2rate_limited means Google is briefly limiting our servers: retry after the minutes given in status_text
- 3invalid_geo: use a two-letter country code (US) or a state code (US-CA)
- 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
Eingabe
Parameter, die zum Aufruf dieser App erforderlich sind, generiert aus dem input.schema in der manifest.json.
- Countries or states
geosErforderlicharray<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.Anzahlbis zu 50 EinträgeStandardUSBeispiel["US"] - Time window (hours)
hoursOptionalintegerSearches that trended in the past 4, 24 or 48 hours, or 168 (7 days). Longer windows list many more searches.Standard24 - Categories
categoriesOptionalarray<string>Only return searches in these Google Trends categories; empty = all categories.Standard - Max trends per region
max_trends_per_geoOptionalintegerAt 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.Bereich1–3000Standard100
Ausgabe
Feldstruktur eines einzelnen Datensatzes, generiert aus dem output.schema in der manifest.json.
- Trend key
trend_keystringRegion | 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 | statusBeispielUS|nsa|2026-11-17T10:50:00+00:00 - Region
geostringThe requested region code: a country (US) or a state / province (US-CA)BeispielUS - Region name
geo_namestringName of the region as Google Trends shows itBeispielUnited States - Rank
rankintegerPosition 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 normalBeispiel1
Beispieldaten
Aus output.schema erzeugt. Felder ohne Beispielwert verwenden strukturelle Platzhalter.
{
"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
Diese App kann über MCP, API, SDK oder Dateiexport integriert werden — alle Kanäle teilen sich dieselben Fähigkeiten und Preise. Jede Anfrage authentifiziert sich über den Authorization: Bearer-Header mit einem API Key (langlebig, in der Data Hub Konsole erstellt); MCP-Clients können sich zusätzlich per OAuth ohne Key anmelden. Weitere Optionen wie CLI und Skill sind in Vorbereitung. Diese App läuft asynchron und kann zwischendurch abgebrochen werden: Nach dem Abbruch stoppt der Lauf. Bereits gelieferte Datensätze bleiben erhalten und werden abgerechnet.
Über das MCP (Model Context Protocol) können Sie diese App direkt aus KI-Clients wie Claude und Cursor aufrufen. Wählen Sie Ihren Client und den Authentifizierungsmodus und kopieren Sie dann die Konfiguration unten.
Client-Konfiguration
Ersetzen Sie den Wert nach Bearer durch Ihren langlebigen API Key. Funktioniert in jedem Client, in CI und in Headless-Umgebungen.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=MagicData/google-trending-now",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Lassen Sie die KI die Einrichtung übernehmen
Sie möchten Konfigurationen nicht von Hand bearbeiten? Kopieren Sie den Installations-Prompt und fügen Sie ihn in einen beliebigen KI-Client ein — er schließt die Einrichtung auf seine eigene Weise ab. (Standardmäßig führt er Sie durch die Anmeldung und fordert Sie nie auf, Ihren API Key im Chat zu senden.)
detail.access.mcp.composeHint
Preise
Gemessen durch Aufsummieren des Ausgabefelds billed_trends. Fehlgeschlagene Läufe werden nicht berechnet.
Mehrere Abrechnungsereignisse werden unabhängig voneinander kumuliert. Details siehe jeweilige Position. Fehlgeschlagene Läufe werden nicht berechnet.
Credits ansehenJetzt ausprobieren
Füllen Sie die Parameter aus und starten Sie — die Ergebnisse stammen aus einem echten Aufruf.