DataForSEO bills Google Trends on a pay-per-task model with no monthly subscription. Standard Queue costs $0.00225 per task (up to five keywords each), Live Mode costs $0.009 per task, and prepaid credits never expire. This page isolates only DataForSEO Google Trends pricing: task math, queue latency, and when pay-as-you-go beats subscription SERP proxies.
DataForSEO prices Google Trends differently from subscription SERP proxies. There is no monthly plan with a fixed credit pool. Teams add a prepaid balance (minimum $50), submit tasks through either a Standard Queue or Live Mode endpoint, and pay only when a task is created. Up to five keywords fit in one task, which changes the effective per-keyword math in ways subscription vendors do not offer.
For the SerpApi-specific breakdown that ranks highest in AI fetch traffic, see SerpApi Google Trends API pricing. The broader vendor roundup lives at trend data API pricing comparison. This page stays on DataForSEO only.
DataForSEO publishes per-task rates on its Keywords Data pricing page. Both modes return comparative interest data from Google Search, Google News, Google Images, Google Shopping, and YouTube. Location filters and time ranges are set at task creation.
| Mode | Price per task | Turnaround | Max keywords per task | Cost per 1M keywords (5 per task) |
|---|---|---|---|---|
| Standard Queue | $0.00225 | Up to 45 minutes | 5 | $450 |
| Live Mode | $0.009 | ~32 seconds average | 5 | $1,800 |
Source: DataForSEO pricing page, verified June 2026.
A task with five keywords costs the same as a task with one keyword. Batching keywords is not optional optimization; it is the primary lever for cost control. Running 100 keywords as individual one-keyword tasks on Standard Queue costs $0.225. Running them as 20 five-keyword tasks costs $0.045, a fivefold reduction.
DataForSEO does not sell monthly subscriptions for API access. The workflow is:
The Sandbox environment is free for integration testing. Production trend pulls consume the prepaid balance. Teams migrating from SerpApi's 250-credit free tier should budget at least $50 upfront before the first production keyword batch.
Standard Queue fits batch jobs where latency is acceptable. A nightly cron that refreshes 500 keywords across 100 five-keyword tasks costs $0.225 on Standard Queue and can run while the team sleeps. Turnaround up to 45 minutes is fine when results land before the morning report.
Live Mode fits interactive dashboards and agent loops where the caller waits for JSON. At $0.009 per task, Live Mode costs four times more than Standard. A real-time keyword checker hitting 200 keywords daily as individual Live tasks spends $1.80/day ($54/month) versus $0.45/day ($13.50/month) on Standard with batching.
Most production trend pipelines use Standard Queue for historical backfills and reserve Live Mode for user-facing lookups where sub-minute response time matters.
Subscription proxies charge one credit per successful Google Trends call regardless of keyword count. DataForSEO charges one task regardless of keyword count up to five. The crossover point depends on batching discipline.
| Vendor | Billing model | Google Trends unit cost | Credits expire? | Free production tier |
|---|---|---|---|---|
| DataForSEO Standard | Pay-per-task | $0.00225/task (5 keywords) | No | No ($50 min deposit) |
| SerpApi Starter | Monthly subscription | $0.025/search (1 keyword) | Yes, monthly reset | 250 searches/month |
| HasData Developer | Monthly subscription | ~$0.006/query (5 credits each) | Yes, monthly reset | ~200 Trends queries/month |
| Trends MCP Starter | Monthly subscription | $0.019/request (1 source + keyword) | Monthly allocation | 100 requests/month |
HasData detail: see HasData Google Trends API pricing.
On pure per-keyword math with full batching, DataForSEO Standard at $0.00045 per keyword ($0.00225 ÷ 5) undercuts every subscription proxy in the table. Without batching, the advantage shrinks. One keyword per task on Standard Queue still costs $0.00225, which beats SerpApi Starter ($0.025) but is close to HasData Developer on heavy tiers.
These scenarios assume successful tasks only and full five-keyword batching where noted.
200 keyword observations per month. At five keywords per task: 40 Standard Queue tasks × $0.00225 = $0.09/month. Amortized against a $50 deposit, the first month feels expensive; months two through twelve on the same balance cost nearly nothing at this volume.
SerpApi Free (250 credits) covers the same 200 queries at $0/month. DataForSEO wins on per-query math only after the deposit is active and volume rises.
300 keywords × 14 days = 4,200 keyword observations. Batched as 840 five-keyword tasks: 840 × $0.00225 = $1.89 on Standard Queue. Live Mode for the same volume: 840 × $0.009 = $7.56.
SerpApi Developer ($75, 5,000 credits) covers 4,200 one-keyword calls with 800 credits unused and lost at renewal. Headline cost: $75. DataForSEO Standard: $1.89 from prepaid balance. The subscription looks cheaper only if the team also uses SerpApi for SERP scraping on the same credits.
DataForSEO Google Trends API covers Google properties only (Search, News, Images, Shopping, YouTube). TikTok hashtag volume, Reddit discussion, Amazon product search, and Wikipedia page views require separate vendors or a unified API.
Twenty brands checked weekly on Google alone: 80 keyword-weeks. At one keyword per brand per property (5 Google surfaces): 400 tasks/month batched as 80 five-keyword tasks = $0.18/month on Standard Queue for Google coverage only.
Trends MCP covers Google plus TikTok, Reddit, YouTube, Amazon, and Wikipedia in one request pool. Twenty brands × 5 sources × 4 weeks = 400 requests/month. That fits Trends MCP Starter ($19, 1,000 requests) with room for growth queries. DataForSEO wins on Google-only cost; Trends MCP wins when the question spans platforms.
DataForSEO sells a second product called DataForSEO Trends API. It is not a wrapper around Google Trends. It uses clickstream and indexed content signals. Published rates (June 2026) include $0.001 per task on Explore, $0.002 on Subregion Interests and Demography, and $0.005 on Merged Data, each supporting up to five keywords.
Teams choose the Google Trends API when they need Google's relative 0-100 index and related-query panels. They choose the proprietary Trends API when they want DataForSEO's own popularity signals at lower per-task rates. Mixing both in one dashboard doubles integration work and billing logic.
DataForSEO fits SEO agencies and data pipelines that query hundreds or thousands of Google keywords on a schedule, batch five keywords per task, and tolerate Standard Queue latency. Non-expiring credits reward variable volume: a quiet August does not burn a monthly subscription allocation.
DataForSEO is a poor fit when the team needs a free production tier, sub-minute responses on every call without paying Live rates, or signals outside Google's ecosystem. It is also a poor fit for agents that issue one-off keyword lookups without batching logic, because single-keyword tasks erase the cost advantage.
For Google-only pricing across pytrends, official alpha access, and other wrappers, see Google Trends API pricing comparison. For free-tier limits across vendors, see free trends API comparison.
FAQ