The proxy currently pinned for queries, if a pool is configured.
Every region Google accepts: [code, name, slug] per country, each with its
subregions. Useful for validating a geo before querying it.
Where keyword is searched, broken down at resolution.
timeframe defaults to the past year; narrow it to ask where something was searched
during a specific window rather than across the whole year.
Relative interest for up to five terms over timeframe.
timeframe takes a Timeframe or a custom "YYYY-MM-DD YYYY-MM-DD" range, and
region any Google geo code — a country, a sub-region like "US-CA", or a metro code.
Top and rising searches related to keyword.
region defaults to worldwide, which is what this returned unconditionally before it was
a parameter — pass a country to ask what is searched alongside the term there.
Entity suggestions for a partial query — the picker behind the UI's "Topic" results.
Pass a returned mid as a keyword to any query method to measure the topic rather
than the literal phrase; a topic aggregates every spelling and translation of the same
concept, so it usually scores far higher than the raw string.
Needs no cookie and no proxy: this RPC answers on IPs the widgetdata endpoints reject.
Trending searches for a region. Accepts any country code, not a fixed list, and worldwide works too.
backend selects the source:
"rpc" (default via "auto") — 50 items with growth percentages and volume."rss" — 10 items with the news articles behind each trend, which the RPC does
not carry, but no growth figures. window does not apply: Google ignores it on the
feed. There is no worldwide feed, so a country code is required."auto" — the RPC, falling back to RSS if it fails. RPC first because it returns five
times the items with real growth numbers; defaulting to RSS would quietly degrade
results.TrendingResult.source reports which one answered.
Fetches data via the in-tree Google Trends HTTP session.