- Ignore unsupported hidden detail input so Trending Now runs never schedule redundant per-term work.
First release. Two surfaces, billed as two separate events.
- Interest over time (weekly series), interest by region, and related + rising queries for any keyword.
averageInterest, peakInterest and peakDate are derived from the returned series.
- Accepts a pasted
trends.google.com/trends/explore?q=… URL as a keyword.
- Related topics are available when an authenticated session is supplied via the optional
googleTrendsSessionCookie input; without it every other field is still returned and the
record reports relatedTopicsStatus: "AUTH_REQUIRED".
- Live trending terms per country with search volume, growth percentage, the related searches
Google groups under each trend, start/end times and backing news article references.
- Windows of 4, 24, 48 or 168 hours; accepts a pasted
trends.google.com/trending?geo=… URL.
- Google rations these endpoints per keyword, so retries cycle across keywords in passes
rather than hammering one term, and only the widgets still missing are re-requested.
- A previously fetched series is served from cache when the live fetch is rationed, labelled
with
fromCache and cachedAt so cached data is never presented as fresh.
- A keyword that returns no time series is still delivered — with
error: "NO_SERIES" — and
is never charged for.