Google Trends Has No Public API — Here Is How Its Hidden Endpoints Actually Work
Google Trends operates through internal JSON endpoints used by its own web app, with no officially documented public API available to developers. These endpoints can return HTTP 200 responses with empty bodies when Google detects bot-like behavior, effectively soft-blocking requests without issuing a standard 429 rate-limit error. All responses also include an XSSI security prefix that must be stripped before JSON parsing, and the prefix format varies inconsistently across endpoints. Google silently renamed a key geographic data endpoint from 'multiGeo' to 'comparedgeo' in mid-2026 with no deprecation notice, breaking regional interest queries for unattended scrapers. Additional quirks include the string 'Breakout' being returned instead of a numeric value for explosive search trends, and a hard limit of five keywords per comparison request.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in