Use your GoAnyAPI key.
Call the GoAnyAPI endpoint with your own API key. You do not need admission to Google’s separate API alpha to use this endpoint.
Manage API keys →Compare search interest over time, inspect rising related queries and investigate seasonality. Test a query here, then use the JSON in Python, Node.js or a connected MCP client.
Compare keywords over time · One region per request
https://api.goanyapi.com/api/v1/google-trends?date=today+12-m&data_type=TIMESERIESRun a request to see the visual result
The response is organized into metrics, lists and tables that match the JSON on the right.
Run a request to see the response here
Fill in the demo parameters to preview an example response for free. Sign in to send live requests with your own parameters.
Use GoAnyAPI to add trend research to an application, without building your integration around a scraping library.
Call the GoAnyAPI endpoint with your own API key. You do not need admission to Google’s separate API alpha to use this endpoint.
Manage API keys →Send a standard HTTP request and read a JSON response. You do not need pytrends in your application; the examples below use requests and fetch.
See request examples →Live requests use credits per keyword, including successful empty results. Check the current rate before testing or scheduling repeated requests.
Understand costs →Move from a broad research question to the trend data that can help answer it.
Compare search interest for up to 5 product ideas, terms, or brands. Check the direction and persistence of interest before deciding what to investigate next.
“Compare standing desk and walking pad interest in the US over the past year.”TIMESERIES
Start with a seed keyword, then explore its top and rising related queries. Turn relevant phrases into content ideas that you can validate with further research.
“Find rising searches related to home office, then suggest useful article angles.”RELATED_QUERIES
Look for recurring patterns across a longer time range. Use historical interest to inform campaign timing and editorial calendars, alongside your own business data.
“Check historical interest in air purifiers and describe recurring seasonal peaks.”TIMESERIES
Every mode returns structured JSON. Select a mode to see the request and response shape.
Compare up to 5 comma-separated keywords over a selected time range, with one optional region shared by all keywords.
Response shape excerpt. Arrays are empty placeholders, not a live query result.
GET /api/v1/google-trends?q=ai+video%2Cchatgpt&data_type=TIMESERIES&geo=US&date=today+12-m
// Response shape excerpt; empty arrays are placeholders.
{
"interestOverTime": {
"timeline_data": [],
"averages": []
}
}Use GoAnyAPI MCP with a compatible AI client, or pass API results into your own application. Your assistant can compare patterns, explain limitations, and draft a research brief from the returned data.
Requires a configured tool connection. These prompts are examples, not automatic features of an unconnected chat.
Compare “standing desk” and “walking pad” search interest in the US over the past 12 months. Describe sustained changes and one-off spikes. Then find rising related queries for “walking pad” and propose five content ideas. Keep observations separate from hypotheses, and do not treat interest scores as search volume or sales.
Choose a region and a supported time range, then use the JSON in a chart, a report, or an AI workflow.
curl --get 'https://goanyapi.com/api/v1/google-trends' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data-urlencode 'q=ai video,chatgpt' \
--data-urlencode 'data_type=TIMESERIES' \
--data-urlencode 'geo=US' \
--data-urlencode 'date=today 12-m'Trend values describe relative Google search interest. They are not exact search counts, website visits, sales, or ChatGPT conversation statistics. Keep the time range and region consistent when comparing terms.
A short spike can have several explanations. Compare longer periods and related queries, and validate your interpretation with other evidence before making a business decision.
Some queries return no trend points or related results. Partial time-series points may be flagged. This endpoint does not provide forecasts, automatic alerts, or a global Trending Now feed.
Per-keyword billing. A time-series request with three keywords uses three times the current configured per-keyword rate.
Successful empty results are charged. A completed query with no data still consumes credits.
Invalid or failed requests are not charged. Incomplete responses do not consume credits either.
These are separate APIs. Choose by access and the research output you need; do not assume that their fields or scales can be swapped.
| Decision point | GoAnyAPI Google Trends API | Google Trends API alpha |
|---|---|---|
| Getting access | Use a GoAnyAPI key and the documented endpoint. | Apply to Google’s limited alpha program; access depends on acceptance. |
| Research output | Request time-series interest, related queries, or related topics; one geo applies per request. | Google describes a five-year rolling window, interval aggregation, and region or subregion data. |
| Comparing requests | Interpret values as relative interest; keep period and region consistent when comparing. | Google describes consistently scaled data across its alpha API requests. |
Google’s published alpha access and scope checked on 26 Oct 2026. The two APIs have separate access and response rules.
For a single keyword, compare the first paid top-up, one-call results and the cost of 1,000 trend queries. Both services offer pay-as-you-go access without a subscription.
1,000 successful, single-keyword Web interest-over-time requests, each for one region and preset date range.
Scroll horizontally to see all columns.
| Service and mode | Billing model | First paid top-up | 1,000 one-keyword tasks | Retrieval and scope |
|---|---|---|---|---|
| GoAnyAPI | One-time shared credits; no monthly subscription. Credits are charged per keyword. | $10.00 · 10,000 credits6 credits / keyword | $6.00 | One HTTP request returns a time series for one Web keyword in this scenario; one region and a supported preset date range. |
| DataForSEO Google Trends Live | Pay as you go; no subscription. One task can contain up to five keywords for the same task price. | $50 minimum paid top-up; new accounts receive $1 trial credit. | $11 for 1,000 tasks ($0.011 per task). | One POST returns a result. Also supports custom dates, five search types and additional result types. |
| DataForSEO Google Trends Standard | Pay as you go; no subscription. One task can contain up to five keywords for the same task price. | $50 minimum paid top-up; new accounts receive $1 trial credit. | $2.70 for 1,000 tasks ($0.0027 per task). | Queued POST plus later GET; published turnaround is up to 45 minutes and can vary with load. Additional date, search-type and result controls. |
Prices checked October 27, 2026. The GoAnyAPI calculation uses the current configured per-keyword credit rate and base USD pack; multi-keyword requests consume more GoAnyAPI credits, while DataForSEO charges the same task price for up to five keywords. The $1 DataForSEO trial credit is separate from its $50 paid top-up. No comparable latency benchmark is available.
Answers for keyword research, AI workflows, and integration.
Compare keyword interest over time, explore top and rising related queries, and discover related topics. Use the results for content research, seasonality analysis, product idea comparisons, and reporting.
Yes. Google has announced a separate Trends API alpha with its own access process. GoAnyAPI provides the endpoint documented on this page through a GoAnyAPI account and API key. You do not need admission to Google’s alpha to call this endpoint.
Live requests are billed in credits per keyword, including successful empty results. Check the current rate on the API page and any credits available in your account. This page does not promise a permanent free tier or unlimited free requests.
Compare the supported data types, keyword limit, date and region controls, response fields, integration options, and total cost for your workflow. GoAnyAPI supports three data modes, up to 5 keywords in a time-series request, one shared region, and REST plus MCP access. It does not offer a Trending Now feed, region-ranking maps, or built-in monitoring through this endpoint.
GoAnyAPI MCP includes the goanyapi_google_trends tool, with the same query modes and per-keyword billing as this REST endpoint. Configure GoAnyAPI MCP in a compatible client before asking the assistant to request or analyze trend data.
An AI client with a configured GoAnyAPI MCP connection can request the data and help analyze it. You can also supply API results to your own AI application. Tool availability depends on the client and its configuration; an unconnected chat does not automatically call this API.
Yes. TIMESERIES accepts up to 5 comma-separated keywords in q. RELATED_TOPICS and RELATED_QUERIES each accept exactly one keyword. Each keyword can contain up to 100 characters.
No. geo accepts one region code, shared by every keyword in the request. Use separate requests to investigate different regions, and do not treat independently scaled scores as absolute market-size comparisons.
Choose from past 1 hour, past 4 hours, past day, past 7 days, past month, past 3 months, past 12 months, past 5 years, all available history. The default is past 12 months. The available data and time-point granularity depend on the query.
No. It returns relative search interest and related-search data. Use the separate Keyword Search Volume API when your workflow needs search-volume data; that endpoint has its own inputs and billing.
Related queries are search phrases associated with your seed query. Related topics describe associated subjects or entities. Each mode provides top and rising arrays when results are available.
No. Search interest alone does not establish purchase intent, revenue, or future demand. Use it to generate and test hypotheses, alongside search-volume research, customer feedback, and your own business data.
Low search interest can produce zero values, and some query, date, and region combinations return no results. Check the returned data rather than interpreting missing data as proof that nobody is interested.
Yes. A completed query with empty result arrays is successful and charged at the current per-keyword rate. Invalid parameters, failed requests, and incomplete responses do not consume credits.
No. This endpoint returns data when requested. Scheduling, storing results, setting thresholds, or sending notifications would need to be implemented in your application or automation workflow.
You can request supported recent date ranges, including the past hour, for a keyword you supply. The endpoint does not provide a country-wide Trending Now feed. A request alone does not establish a fixed data freshness guarantee.
Use RELATED_QUERIES with one seed keyword and inspect relatedQueries.rising. Investigate the returned terms with a time-series query before prioritizing them. Results depend on the seed, date, and region; the endpoint does not guarantee breakout terms or automatic alerts.
You can schedule requests in your own application or automation tool, store results, and apply your own alert rules. This API does not run the schedule or deliver alerts for you. Account for all queried keywords, including successful empty results, when estimating the recurring cost.
Yes. Call the documented REST endpoint directly from your application using an HTTP client. The Python example uses requests, and the JavaScript example uses fetch. Your application does not need to maintain a pytrends integration.
No unlimited-request or no-blocking guarantee is offered on this page. Use the documented endpoint and your API key, handle request failures, and apply retry backoff rather than assuming unrestricted concurrency. A numeric throughput guarantee needs to be confirmed for your intended workload.
Yes. Send a GET request with your GoAnyAPI key in the Authorization: Bearer header. The examples above show Python and JavaScript requests. The response includes a status, selected mode data, the charged credits, and the remaining balance.
Choose another signal for your research, then compare the results in context.