ScrapingBee Google Trends Alternative

ScrapingBee's Google Trends scraper page describes the product as a URL in, HTML or extracted JSON out. Proxies, JavaScript, and CAPTCHA handling sit behind https://app.scrapingbee.com/api/v1/. The caller still names the Trends URL. Trends API does not. It names mode, source, and keyword. The contract is on the API reference.

Pass a URL, own the parse

A typical call sends api_key, the Trends URL, and custom_google=true. Optional flags include render_js, stealth_proxy, country_code, extract_rules, and ai_extract_rules. The JSON shape is the rule set. Change the page, change the rules.

That is the opposite of a trend API. Trends API returns date and value (0-100) for keyword history. Live boards return a ranked list. The caller does not write CSS.

A small Python helper on PyPI (google-trends-scraper-api) wraps ScrapingBee for the public trending RSS. That helper returns title, traffic buckets, and news. It is still a scrape of Google's feed, not get_top_trends.

custom_google is a scraper flag

Google properties are not ordinary pages on ScrapingBee. The flag is required. Trends API has no equivalent flag. source google search is a data source. custom_google is a fetch permission. URL plus selectors versus mode sits on Trends API vs ScrapingBee.

Do not put custom_google in a Trends API body. Do not put source in a ScrapingBee query string.

No shared 0-100 with TikTok

ScrapingBee can fetch other sites with other URLs. Each URL is a new parse. There is no type list like TikTok Trending Hashtags, YouTube Trending, or Amazon Best Sellers Top Rated. Those strings belong to live feeds.

No extract_rules. No Trends URL. Parse the body string.

When a renderer is the wrong tool

Keep ScrapingBee when the company already pays for rendered Google HTML and Trends is one more URL. Check ScrapingBee's current credit pricing. Leave when on-call should not include broken selectors. An actor-shaped scrape is Apify. A target=google_trends_explore POST is Decodo.

Common questions

Does ScrapingBee have a dedicated Google Trends engine?

ScrapingBee documents a Google Trends scraper page and the generic HTML API. Google hosts need custom_google. Structured output comes from extract_rules, ai_extract_rules, or a helper that reads the public RSS. There is no source google search mode on that API.

What happens if a Trends URL is sent without custom_google?

ScrapingBee's own Trends helper text says a trends.google.com URL through the HTML API without the flag is refused. That is a scraper rule, not a Trends API error. Trends API never accepts a Trends URL as the target.

Can extract_rules replace a trend score?

Only if the caller writes selectors that survive the next Google markup change. The result is whatever those selectors caught. It is not a documented 0-100 series with volume on the same row.

When is ScrapingBee still useful for Trends?

When the team already buys render_js for other Google pages and needs a one-off HTML dump. When the team needs a daily cron on google and youtube, selectors are the wrong contract.

ScrapingBee for Google Trends, and where it stops

Pass a URL, own the parse

custom_google is a scraper flag

No shared 0-100 with TikTok

When a renderer is the wrong tool

What you get

Common questions

Related

Start pulling trend data in 60 seconds.

Get your free API key

Check your inbox