Search-interest time series (0-100) for 1-5 keywords, with per-keyword summary (mean, latest, peak, direction over the whole window, direction_now = recent slope, growth_3m/growth_12m % and a plain-English insight). Use direction_now to decide whether to write about a topic now; direction can be 'rising' or 'new' for a topic that peaked months ago. Long series are downsampled to ~60 points. gprop: '' (web), 'news', 'youtube' (authority channels answer engines cite), 'images', 'froogle'.

Compare 2-5 keywords head-to-head: relative share, leader and trend direction for each. Use to pick the strongest angle among alternatives.

Top and rising search queries related to a keyword. 'rising' includes % growth and is_breakout (>5000%); every item carries a title angle, and questions lists the question-shaped ones. Rising items flagged suspect=true look like injected spam (one name across unrelated queries, or a domain) and are left out of questions. Best single source of fresh blog angles.

Top and rising Knowledge-Graph topics related to a keyword. Google often returns nothing here; if available=false fall back to related_queries.

Where a keyword is searched most. resolution: COUNTRY (geo='' only), REGION (states/provinces within geo), CITY and DMA (US metro areas; geo='US' or worldwide only). Non-US countries support REGION only.

Google's entity suggestions for a keyword (title, type, mid). Use to disambiguate ambiguous terms or find the canonical topic id.

Real-time trending searches (last ~24h) for a country or US state, with approximate traffic and linked news headlines. Good for newsjacking. topic_filter keeps only trends whose title or headlines contain every word given (e.g. 'coffee'); the full feed is still fetched and cached once.

Browse/search Google Trends category ids (e.g. 'coffee' -> Food & Drink > Coffee & Tea). Pass the id as category to other tools to narrow results.

One-shot topic discovery for blog ideation. For 1-5 seed keywords, pulls 12-month trend context (direction, direction_now, growth_3m) plus rising/top related queries, de-duplicates and ranks candidates as breakout > rising > evergreen, each tagged with a title angle and an explainable score. questions collects question-shaped searches across seeds; suspect lists spam-like rising queries kept out of the ranking. site_queries = queries the site already ranks for (fill from a Search Console MCP or page titles): each topic then gets coverage covered / partial / gap, and exclude_covered drops the covered ones. Partial failures are reported per seed in errors instead of failing the call. First call of a session: start with 1-2 seeds to avoid a 429.

Long-tail questions people type about a seed, from Google Autocomplete ('how to', 'why', 'what is', 'vs' ... expansions), de-duplicated and tagged with a title angle. Feeds FAQ sections and answer-engine (AEO) content. Up to ~16 throttled requests per call; results cached 24 h. limit: 1-100.

AEO opportunity finder. For 1-5 seeds: question-shaped searches (Trends + a capped Autocomplete pass) clustered by seed and title angle, each scored with the seed's recent trend (direction_now over 12 months, growth_3m), Google News coverage (who to quote / pitch), Wikipedia presence, the site's own coverage and the evidence type that makes the answer citable (score_breakdown explains every point). site_queries = queries the site already ranks for (fill from a Search Console MCP or page titles); clusters then carry coverage covered / partial / gap and exclude_covered drops covered ones. Spam-like rising queries are ignored. Up to ~1+10 requests per seed; partial failures per source in errors. limit: clusters (1-25).

Who is covering a topic in Google News: recent headlines, a publisher frequency table (mention / pitch targets) and a recency histogram with a coverage label. One request, cached 15 min. limit = headlines returned (1-50).

Does Wikipedia have an exact-title article for a topic, and is attention growing? Exact article (title, encoded URL, wordcount), daily pageviews for days (7-90) with direction / growth / insight, or has_article=false with a related_article suggestion (when search finds a different title); verify gaps before citing. lang = Wikipedia edition ('en', 'pt', 'de'). Own rate lane; cached 24 h.

What changed for 1-5 seeds since the last snapshot at least since_days (1-90) old: new_breakouts and promoted (action: investigate now), new_rising (consider), cooled / dropped queries (review: verify with interest_over_time before retiring, or refresh existing post), rank_moves and a direction_flip on direction_now. Leaving Google's relative list is not proof of falling demand. Refreshes current data first (1 + N requests, cached), then compares complete snapshots from the local observation archive, which fills up as any tool fetches fresh data. No baseline yet -> per-seed reason with the date to rerun.

Local archive of what the tools have seen about a keyword (as a seed or as a related query under other seeds) in the last days (1-365): first_seen / last_seen, breakout_episodes (separate breakout runs; >= 3 = recurring, durable page) vs breakout_observations (polling count), direction_timeline per timeframe and seen_under_seeds. Free: makes no network requests.

When demand for a keyword peaks each year (5-year weekly data): monthly_index, peak_months, seasonal_strength, next_peak and publish_by (6 weeks before the peak), with a plain-English insight. One request; seasonal=null with a reason when fewer than 3 full years exist.

Which Google property a topic grows on: web, youtube, news, images, shopping, each with direction / direction_now / growth_3m, plus fastest_channel and a format_hint (video tutorial, buying guide, newsjacking piece ...). 5 requests (web first; the rest are skipped on a 429). Channels are separate 0-100 scales: compare growth, never means.

Health of every data source (google_trends, google_autocomplete, google_news, wikipedia: live / error / idle with the last error), cache usage, observation archive (rows, dates, last_error) and effective settings. Free: makes no network requests.