Pp Google Trends

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/marketing/google-trends/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

Google Trends — Printing Press CLI

Prerequisites: Install the CLI

This skill drives the google-trends-pp-cli binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to $HOME/.local/bin on macOS/Linux and %LOCALAPPDATA%\Programs\PrintingPress\bin on Windows:

   npx -y @mvanhorn/printing-press-library install google-trends --cli-only

2. Verify: google-trends-pp-cli --version
3. Ensure the reported install directory is on $PATH for the agent/runtime that will invoke this skill.

If the npx install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into $GOPATH/bin (default $HOME/go/bin), so add that directory to $PATH instead:

go install github.com/mvanhorn/printing-press-library/library/marketing/google-trends/cmd/google-trends-pp-cli@latest

If --version reports "command not found" after install, the runtime cannot see the binary directory on $PATH. Do not proceed with skill commands until verification succeeds.

pytrends — the de-facto standard Python wrapper — was archived in April 2025, and Google Trends throttles anonymous access aggressively and unpredictably. This CLI absorbs the full explore-to-widget contract with built-in retry/backoff, caches every query locally so history compounds instead of evaporating, and answers questions the live site simply cannot: what was trending three weeks ago, what changed since your last check, and which related terms are actually worth a content brief.

When to Use This CLI

Use this CLI for programmatic Google Trends research: interest-over-time pulls, multi-keyword and cross-geo comparisons, related/rising query discovery for content planning, and tracking trending topics over time via the local cache. It is the right tool whenever you need history Google Trends' own UI discards, or when you're automating what used to be a manual pytrends script.

Anti-triggers

Do not use this CLI for:

• Do not use this CLI for absolute search volume — Google Trends only exposes relative 0-100 interest, never real query counts.
• Do not use this CLI for real-time (sub-hourly) trend monitoring at scale — the API's aggressive rate limiting makes tight polling loops unreliable.
• Do not use this CLI for authenticated Google Ads Keyword Planner-style volume data — that requires a separate Google Ads account and API, not Trends.

Unique Capabilities

These capabilities aren't available in any other tool for this API.

Local state that compounds

• trends trending at — See what was trending on a specific past date and geo — a question Google Trends' own live UI cannot answer.

  Reach for this when reconstructing what was trending on a specific past day instead of scraping the live site, which cannot show historical trending snapshots at all.

  google-trends-pp-cli trends trending at --date 2026-06-15 --geo US --agent

• trends history search — Full-text search across every related-term and trending-topic result you've ever synced, offline.

  Use this to check whether a term you tracked weeks ago ever surfaced as related or trending, without re-querying the rate-limited live API.

  google-trends-pp-cli trends history search "electric vehicle" --table related --agent

• trends changes — See exactly what changed for a keyword's related terms and interest score since your last sync.

  Reach for this instead of re-eyeballing a chart when you need to know precisely what's new since last week.

  google-trends-pp-cli trends changes coffee --since 7d --agent

• trends opportunities — Ranks a keyword's related/rising terms by rising-momentum times parent-topic growth, surfacing the best content ideas first.

  Use this when you need a shortlist of content ideas ranked by momentum, not the raw related-queries dump.

  google-trends-pp-cli trends opportunities "meal prep" --agent

Computed insight

• trends seasonality — Computes monthly averages, peak month, and a seasonality strength score for a keyword from cached history.

  Reach for this to detect a keyword's seasonal pattern from cached history instead of eyeballing a chart by hand.

  google-trends-pp-cli trends seasonality "pumpkin spice" --geo US --agent

• trends geo-gap — Ranks the regions where two keywords' interest diverges most, instead of raw per-region values you'd have to compare by hand.

  Use this for a ranked list of the biggest regional gaps between two keywords, not the raw per-region compare.

  google-trends-pp-cli trends geo-gap nike adidas --resolution REGION --agent

Reachability mitigation

• trends stale — Lists tracked keywords whose local data hasn't been refreshed recently, so you know what to re-sync before you hit a rate limit.

  Check this before a bulk re-sync so you refresh only what's actually stale, given this API's confirmed rate-limit fragility.

  google-trends-pp-cli trends stale --older-than 14d --agent

HTTP Transport

This CLI uses Chrome-compatible HTTP transport for browser-facing endpoints. It does not require a resident browser process for normal API calls.

Discovery Signals

This CLI was generated with browser-observed traffic context.

• Capture coverage: 29 API entries from 226 total network entries
• Protocols: google_batchexecute (95% confidence), rpc_envelope (90% confidence), rest_json (75% confidence)
• Auth signals: api_key — headers: X-Goog-Api-Key; api_key — query: key, token
• Generation hints: browser_http_transport, has_rpc_envelope, requires_protected_client, weak_schema_confidence
• Candidate command ideas: create_GetAsyncData — Derived from observed POST /$rpc/google.internal.onegoogle.asyncdata.v1.AsyncDataService/GetAsyncData traffic.; create_batchexecute — Derived from observed POST //TrendsUi/data/batchexecute traffic.; create_browserinfo — Derived from observed POST //TrendsUi/browserinfo traffic.; create_explore — Derived from observed POST /trends/api/explore traffic.; create_reload — Derived from observed POST /recaptcha/enterprise/reload traffic.; create_startup_config — Derived from observed POST /v1/survey/startup_config traffic.; create_trigger_anonymous — Derived from observed POST /v1/survey/trigger/trigger_anonymous traffic.; create_ubd — Derived from observed POST /recaptcha/api2/ubd traffic.
• Caveats: empty_payload: API-looking request returned an empty or null payload; schema confidence is weak.; empty_payload: API-looking request returned an empty or null payload; schema confidence is weak.; empty_payload: API-looking request returned an empty or null payload; schema confidence is weak.; empty_payload: API-looking request returned an empty or null payload; schema confidence is weak.; empty_payload: API-looking request returned an empty or null payload; schema confidence is weak.; empty_payload: API-looking request returned an empty or null payload; schema confidence is weak.; empty_payload: API-looking request returned an empty or null payload; schema confidence is weak.; empty_payload: API-looking request returned an empty or null payload; schema confidence is weak.; empty_payload: API-looking request returned an empty or null payload; schema confidence is weak.; empty_payload: API-looking request returned an empty or null payload; schema confidence is weak.

Command Reference

trends — Core Google Trends explore/widget flow. explore and pickers_* are directly callable; widget_* endpoints require a token minted by a prior explore call (chained by hand-written wrapper commands in Priority 0/1 — see the absorb manifest). All responses are prefixed with Google's XSSI defense string )]}', which must be stripped before JSON decoding.

• google-trends-pp-cli trends explore — Requests per-widget tokens for a comparison of up to 5 keywords.
• google-trends-pp-cli trends pickers-category — Full category id-to-name lookup tree. Openly accessible, no clearance cookie required.
• google-trends-pp-cli trends pickers-geo — Full geo code-to-name lookup tree (country/region/DMA/city). Openly accessible, no clearance cookie required.
• google-trends-pp-cli trends widget-comparedgeo — Interest-by-region data for the GEO_MAP widget.
• google-trends-pp-cli trends widget-multiline — Interest-over-time data for the TIMESERIES widget.
• google-trends-pp-cli trends widget-relatedsearches — Related queries and related topics (both top and rising) for the RELATED_QUERIES/RELATED_TOPICS widgets.

Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

google-trends-pp-cli which "<capability in your own words>"

which resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code 0 means at least one match; exit code 2 means no confident match — fall back to --help or use a narrower query.

Recipes

Compare a brand against two competitors

google-trends-pp-cli trends interest nike --compare adidas,puma --geo US --timeframe "today 3-m" --json

Returns all three keywords on the same 0-100 scale in one call, the shared-scale comparison pytrends required manual payload construction for.

Find this week's best content ideas from a topic

google-trends-pp-cli trends opportunities "home workout" --agent

Ranks rising related terms by momentum instead of dumping the raw related-queries list.

See what changed since last week without re-scraping

google-trends-pp-cli trends changes coffee --since 7d --agent

Diffs the last two local snapshots — a question the live site cannot answer since it has no history.