The best Google Trends APIs in 2026 are paid scraping proxies (SerpApi, ScrapingBee), SEO data platforms with Trends endpoints (DataForSEO), fragile open-source wrappers (pytrends / forks), and managed multi-source servers such as Trends MCP. There is still no fully open, self-serve official Google Trends API for most developers. SerpApi led brand demand in this roundup at Google Search interest score 46 on August 1, 2026 after +48.39% 12-month growth, while the query "Google Trends API" sat at score 15 after +7.14% over 12 months (Trends MCP API). Trends MCP Free stays at 100 requests/month with MCP and REST access as of August 5, 2026 (Trends MCP pricing). This guide ranks options by reliability, pricing shape, and whether the output is Trends-only scrape JSON or normalized multi-source demand.
What counts as a Google Trends API
A Google Trends API returns structured interest, related queries, geo breakdowns, or live trending boards without a human clicking through trends.google.com. SerpApi documents an engine=google_trends endpoint for timeseries, geo maps, related topics, and related queries (SerpApi Google Trends API, accessed August 5, 2026). ScrapingBee sells a Google Trends scraper that returns rendered HTML or parsed fields behind proxy rotation (ScrapingBee Google Trends scraper, accessed August 5, 2026). Trends MCP exposes Google Search demand through get_growth, get_time_series, and a live Google Trends board via get_top_trends, plus 25+ other sources on one key. pytrends historically scraped unofficial endpoints; it remains a free path but is maintenance-fragile for production.
The label "API" matters because browser-only tools do not solve cron jobs, agent tools, or dashboards. For free browser options and non-API free tiers, see best free Google Trends alternatives. For Python-first setup notes, see Google Trends API in Python. Teams that only need a free trial key before writing code should start at Trends API free.
August 2026 demand table for Google Trends API tools
Search interest for API and scraper brands shows DataForSEO and SerpApi far ahead of ScrapingBee on recent score, while "Google Trends API" as a job query grew year over year even after a sharp spring cool-down. On August 1, 2026 (Trends MCP API, google search, 0-100 interest):
| Keyword | Score (Aug 1 2026) | 12M growth | 6M growth | 3M growth | 30D growth |
|---|---|---|---|---|---|
| DataForSEO | 47 | +147.37% | +11.9% | −22.95% | −46.59% |
| SerpApi | 46 | +48.39% | −13.21% | −28.12% | −34.29% |
| Google Trends | 37 | −11.9% | −50.67% | −55.95% | −50.0% |
| Google Trends API | 15 | +7.14% | −71.7% | −81.01% | −76.19% |
| Trends MCP | 13 | −7.14% | −56.67% | −82.89% | −82.43% |
| pytrends | 12 | −45.45% | −79.66% | −72.09% | −78.18% |
| ScrapingBee | 3 | 0.0% | −75.0% | −96.39% | −96.0% |
SerpApi's weekly series peaked at interest 100 on June 20, 2026, then settled to 46 by August 1, 2026 (Trends MCP API get_time_series, google search). That pattern fits a product that already has search mindshare, not a brand still waiting for discovery. ScrapingBee's score of 3 does not mean the product is unused; it means Google Search brand demand is thin relative to SerpApi and DataForSEO in this window.
SerpApi for structured Google Trends JSON
SerpApi is the default pick when the job is a faithful scrape of Google Trends UI data as clean JSON. The public pricing page lists Free at $0 for 250 searches/month, Starter at $25 for 1,000, Developer at $75 for 5,000, and Production at $150 for 15,000 (SerpApi pricing, accessed August 5, 2026). That pricing shape fits prototypes and mid-volume SERP workloads. It does not include absolute search volume on Trends endpoints the way some SEO databases market volume estimates.
Demand for the SerpApi brand rose +48.39% over 12 months to score 46 (Trends MCP API, August 1, 2026). The same series fell −34.29% over the latest 30 days from a July 4, 2026 baseline of 70, so short-term cooling sits on top of a still-strong year-over-year gain. For teams that already pay SerpApi for Google Search or Maps, adding engine=google_trends is operationally cheap. For teams that need TikTok, Amazon, Steam, or npm in the same schema, a Trends-only scrape leaves gaps.
ScrapingBee when the full Trends page must be scraped
ScrapingBee fits pipelines that need proxy rotation, CAPTCHA handling, and browser rendering against arbitrary Google Trends URLs rather than a single normalized schema. Public pricing starts at Freelance $49/mo, then Startup $99/mo, Business $249/mo, and Business+ $599/mo, with a 1,000-credit free signup path (ScrapingBee pricing, accessed August 5, 2026). Google Search interest for "ScrapingBee" was flat at +0.0% over 12 months and sat at score 3 on August 1, 2026, with −96.0% over 30 days (Trends MCP API). Treat that as a weak brand-search signal, not a quality verdict on the scraper.
Choose ScrapingBee when engineering wants HTML control or multi-site scraping under one vendor. Choose a structured Trends endpoint when analysts want related queries and timeseries without writing parsers. ScrapingBee is the wrong default for an AI agent that expects a small JSON growth object per call.
DataForSEO for SEO stacks that already buy SERP data
DataForSEO led this demand table at score 47 with +147.37% 12-month growth and +11.9% over 6 months (Trends MCP API, August 1, 2026). That is the strongest long-window brand move in the set. Pricing is pay-as-you-go with a stated minimum payment of $50 on the public pricing page; endpoint rates should be confirmed in the account panel before budgeting a Trends workload (DataForSEO pricing, accessed August 5, 2026).
DataForSEO makes sense inside SEO platforms that already consume its SERP and keyword APIs. It is a heavier commercial relationship than a 250-search SerpApi free tier or Trends MCP Free. Teams that only need occasional Trends pulls will overpay if they open a DataForSEO account solely for one endpoint.
pytrends and community forks after the archive
pytrends remains the free Python library people still type into Google, but demand is fading: score 12 on August 1, 2026 after −45.45% over 12 months and −78.18% over 30 days (Trends MCP API). Community forks such as trendspyg appear in blog roundups as maintained successors; Trends MCP flagged the "trendspyg" series as low quality with over 90% zero values, so this post does not treat that brand query as a reliable demand signal. Use an open-source wrapper for notebooks and teaching. Do not put an unofficial scraper on a revenue-critical cron without monitoring for 429s and schema breaks.
Trends MCP for MCP-native and multi-source demand
Trends MCP is the option when the consumer is an AI client (Claude, Cursor, VS Code) or a product that needs Google Search demand next to TikTok, Amazon, YouTube, Wikipedia, and live boards. Pricing on August 5, 2026: Free 100 requests/month, Starter $19 for 1,000, Pro $49 for 5,000, Business $199 for 25,000 (Trends MCP pricing). Google Search interest for "Trends MCP" was score 13 (−7.14% over 12 months) on August 1, 2026 (Trends MCP API). The differentiator is not brand search share. It is normalized multi-source delivery plus MCP tools (get_growth, get_time_series, get_top_trends) without per-site scraping keys.
A live Google Trends board pull on August 5, 2026 at 18:01 UTC returned top terms including "perez hilton", "michigan primary", "idaho murders", "tom holland spider man movies", and "glen hansard" (Trends MCP API, type Google Trends, limit 15). That board call is the API shape product teams want for "what is trending now" widgets, separate from keyword timeseries.
Who should not buy a Google Trends API
Skip paid Trends APIs when weekly manual checks in the Google Trends UI answer the question, or when the real need is TikTok Shop / Amazon velocity rather than Google interest. SerpApi and ScrapingBee are poor fits for researchers who never write HTTP clients. pytrends is a poor fit for anyone who cannot tolerate sudden breakage. Trends MCP Free is a poor fit for workloads above 100 requests/month without upgrading; Starter at $19/month is the next step, not a silent overage model.
Pricing and feature claims above were checked on vendor pages on August 5, 2026. Plan limits change; confirm on the linked pricing pages before procurement.
Sources
- SerpApi Google Trends API and SerpApi pricing, accessed August 5, 2026
- ScrapingBee Google Trends scraper and ScrapingBee pricing, accessed August 5, 2026
- DataForSEO pricing, accessed August 5, 2026
- Trends MCP pricing, accessed August 5, 2026
- Trends MCP API
get_growth/get_time_series/get_top_trendspulls, August 5, 2026 (interest scores dated August 1, 2026)