Google offers an access-controlled Trends API alpha and CSV downloads from the Trends website. They are different data routes with different scaling. As checked on 21 October 2026, the public API page still invites alpha applications. A website's internal requests, or a third-party wrapper around them, should not be mistaken for that official API.
Choose the route before writing the integration
| Route | Suitable starting point | What to confirm |
|---|---|---|
| Official Google Trends API alpha | Programmatic analysis for accepted testers | Approved account, current private documentation, supported fields, limits and terms |
| Trends website CSV export | A chart you can inspect and export manually | Chart type, selected terms or topics, region, dates and downloaded file structure |
| Third-party service or unofficial wrapper | A separately evaluated integration | Actual data source, contract, response schema and support; a product name is not Google approval |
The current official API page describes a rolling five-year data window, daily/weekly/monthly/yearly aggregation and region or subregion comparisons. It also describes consistent scaling across requests. That is a useful basis for evaluating the API, but the public page does not establish access for your account or document every field you may need.
For example, a project that needs related queries must confirm that exact capability in the documentation available to its approved account. Do not infer it simply because the website has a related-queries chart. Likewise, do not copy a quota or authentication pattern from an unofficial library into an official-API specification.
API scaling is not the website's 0–100 scale

The 24 July 2025 announcement explains that consistently scaled API values still represent search interest, not absolute search counts. The current API page also explicitly distinguishes its scale from the website's 0–100 output. Do not apply a CSV rule such as “the peak must be 100” to every API response.
For website charts, Google's data FAQ describes normalization by searches for the relevant time and geography, followed by scaling to 0–100. Changing the comparison or time window can change the scale. Export alternatives together when they need a common website-chart comparison; do not casually join independently scaled files as though equal values meant equal search counts.
Check alpha access using the invited account
- Start from the current official API page and its application link, rather than an endpoint copied from an old tutorial.
- If accepted, use the email address that received the invitation. Google's documentation-access guide says an accepted tester seeing a documentation 404 should first check that account; organization accounts may also need Google Developers enabled by their Workspace administrator.
- Read the available authentication, fields, quotas and usage terms before scheduling jobs. Confirm that the data and freshness fit your use case.
- Store request settings, retrieval time and failed attempts separately from successful data. An alpha integration needs a recovery plan appropriate to its documented behavior.
The access guide is specifically about accepted testers and documentation access. It does not mean every 404 is an authentication problem. We have not performed an approved-account API call for this guide, so the example does not establish an account quota, service-level agreement or successful production integration.
Export a chart, then inspect the actual CSV
Google's export instructions say to open Trends, search for a term and use Download at the top right of the chart. Record the term or topic, geography, time range, category, search type and retrieval time. Follow the options available in the actual chart; different chart types do not necessarily have the same columns.
Before naming columns or calculating an average, inspect the file. This Python standard-library example previews at most eight CSV records without assuming a fixed header row or converting values:
import csv
from itertools import islice
with open("trends_export.csv", encoding="utf-8-sig", newline="") as f:
for number, row in enumerate(islice(csv.reader(f), 8), 1):
print(number, row)
It is a local file-inspection example, not an API client or a universal Trends parser. After looking at the real file, explicitly select its header and data region. Preserve the raw download. Record any transformation used to create a consistent analysis table, including the chosen date interval and time zone.
- Do not force two column names onto a multi-term export.
- Do not automatically turn a blank, a missing field or a value such as
<1into numeric zero. - Check whether a current period is incomplete before comparing it with complete periods.
- Keep separately normalized website exports separate unless you have a justified comparison method.
The comparison guidance distinguishes terms, topics and grouped comparisons. Choose them deliberately. The data FAQ also describes short-window data and statistical noise, so “Trends never changes within a day” is not a sound universal caching rule. Choose freshness and cache behavior for the actual route and analysis.
Treat a failed request as a failed observation
Internal website routes may appear in browser network traffic, but that does not establish a supported developer contract. A third-party vendor may offer its own API and support; inspect those terms separately from Google's alpha. Do not claim that switching routes guarantees the disappearance of rate limits.
An HTTP 429, an empty JSON result and an unexpected HTML response require different checks. The Trends response-diagnosis guide shows that distinction with local examples. Keep failures out of the demand series rather than filling them with zero.
Turn the export into a page decision
Use relative-interest and seasonality analysis to investigate timing, then compare with appropriate volume estimates and other research metrics. Read the actual results and customer questions before choosing whether to update an existing page or develop a missing answer. An export is an input to that decision, not evidence of future rankings.
Guangsuan's Google SEO service combines technical work, content and the wider agreed project scope. The practical deliverable is useful research connected to pages and follow-up measurement, rather than an unexplained spreadsheet of scores.
Portions of this page are reproduced from work created and shared by Google and used according to terms described in the Creative Commons 4.0 Attribution License.