Google Trends scraping: API flow, rate-limit handling, and what's server-side gated

Short summary

Google Trends has no official API; its internal endpoint uses single-use tokens and aggressive per-IP rate limiting that causes 429s. The article documents the full handshake (explore → widgetdata), the anti-XSSI response prefix, and which data is server-side gated for anonymous scrapers (related topics always empty, city-level geo returns no data). A working approach requires IP rotation, cookie-jar warming, and exponential backoff. Trending Now has a free RSS feed with no token needed.

• •Google Trends internal API uses token-signed widget requests with aggressive per-IP 429 rate limiting
• •Related topics and city-level geo are server-side gated for anonymous sessions — not beatable without logged-in cookies
• •Trending Now RSS feed works anonymously with no token handshake required

Generated with AI, which can make mistakes.