All notable changes to Google Trends Scraper are recorded here. The newest release is first.
Apify renders this as a Changelog tab on the Store page. Keeping it current is a
visible signal that the Actor is maintained, which feeds the quality score that
drives Store and MCP search ranking. Add an entry with every published build.
- Compare mode (
compareTerms): up to 5 terms on one timeline and one 0-100 scale. Every compared keyword row now also has comparisonGroup, comparisonRank (1 = most searched) and shareOfInterest (% of the comparison's interest); a new Comparison view shows them side by side. This also applies to the existing comma syntax (coffee, tea).
- A 6th term in a comparison is no longer dropped silently: it comes back as a free
error row that says so.
- Keyword aliases (
keywordAliases): your own label per term or topic id, written as alias on its rows (searchTerm is unchanged).
- Topic suggestions (
includeTopicSuggestions, off by default): the Google Trends topics that match each keyword (topicSuggestions: [{topicId, title, type}]), so you can search the topic instead of the text. No extra charge: in flat format the topic_suggestion rows are free.
- Prices and all existing fields are unchanged.
First public release.
- Interest over time, interest by region (country, subregion, city, metro area) and related queries for single terms or comparisons of up to 5 terms, plus Trending now per country with news articles.
- Reads Google Trends' own public endpoints with no login and no API key; handles the cookie handshake and rate limits, and switches to Apify Proxy (datacenter) when Google slows the run down.
- One result per keyword by default: interest over time, by region and related queries nested in one row with latest/average/peak values. A flat one-row-per-data-point format is available for spreadsheets.
- Every row carries
status, so a missing record (not_found) and a failure (error) are told apart from real data. Only ok rows are charged.
- Records are validated against a schema before they are written, so an upstream change produces loud warnings instead of silently billing for empty rows.
- Callable with no arguments by an AI agent, which the input schema's defaults make safe.