alternatives

Stop scraping Google Trends. Call it instead.

A Trends scraper rents the website's limits and layout. This API returns the series as JSON rows: date, 0-100 value, volume. One POST, no browser farm.

A Google Trends scraper works until it does not, and the failure is never scheduled. Cookies expire, tokens rotate, the widget layout shifts, or the request budget runs out mid backfill. The data on the other side is simple: a dated series. Trends API returns that series as JSON from one POST, with a Bearer key and no browser, session, or page structure in the loop. This page is for teams replacing a scraper that already exists and already breaks. The vendor-shaped comparison sits on SerpApi alternative.

What the scraper was really renting

Every scraper rents four things from the Trends website: a session, a token, a layout, and silence about rate limits. Rent is due without warning. The classic symptom list (empty responses, sudden 429s, charts that stop at odd dates) is catalogued on Google Trends API 429. None of those are data problems. They are tenancy problems.

The contract that replaces it

POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>

{"mode":"get_time_series","source":"google search","keyword":"cold plunge"}

The envelope is {"statusCode": int, "body": string}; parse body a second time and store the rows. History, growth, and the live board are three modes of this one call, so the scraper's second and third scripts retire with the first.

What migration actually touches

Storage, charts, and alerts downstream stay. Only collection changes: out goes the headless browser or token client, in goes one request per keyword and source. Teams coming from the best known scraper client get the step list on Migrate from pytrends.

Past Google

A scraper is built per site, so TikTok or Amazon means a second scraper. The same key here reads 16 keyword sources and 24 live feeds on one 0-100 scale; the second platform is a source string. The full list sits on the sources reference, and caps sit on pricing.

Google Trends scraper alternative

What you get

One POST instead of browser or token scraping

Weekly rows with date and 0-100 value

No cookies, sessions, or page layout to track

Same key for 16 keyword sources

FAQ

Common questions

Why do Google Trends scrapers keep breaking?

They depend on things Google never promised: session cookies, request tokens, widget layouts, and an unspoken request budget. Any of the four can change without notice, and the failure usually arrives as a 429 or an empty block in the middle of a scheduled run.

What does the API return that a scraper was collecting?

The same underlying series, as rows. get_time_series returns weekly points with a date, a 0-100 value, and volume when the source publishes it. get_growth returns one percent per named window. get_top_trends returns the live board with no keyword at all.

Is scraping Google Trends against the terms?

Automated access outside the offered interfaces sits in grey territory, and accounts and IP ranges pay for it with blocks. A keyed API is the vendor taking that risk on contract, which is the practical difference for a business process.

What happens to existing scraper code after switching?

The collection step collapses to one POST with a Bearer key, and the parsing step disappears because the reply is already rows. Jobs keep their storage and charts. The migration shape from pytrends sits on the migrate page.

Keep exploring

SerpApi for Google Trends, and where it stops SerpApi reprints Google Trends Explore and Trending Now as JSON. That is a SERP product. It is not a multi-source trend score. Treat HTTP 429 as a stop, then back off A 429 from Google Trends is a scrape block. A 429 from POST /api is a quota or burst signal. Retry with jitter. Do not loop time series to invent a budget. Map each pytrends method to one POST mode interest_over_time becomes get_time_series. trending_searches becomes type Google Trends. gprop values become other source strings. Delete TrendReq.

Start pulling trend data in 60 seconds.

100 requests a month free. No credit card, no sales call. One key works for every source.

Get a free API key