Values are relative, 0 to 100
Each website chart is scaled to its own peak for the chosen terms, time range and location. Change any of them and every value is rescaled, so store the exact request with each result.
Marketers, analysts and SEO teams use Google Trends to see how interest in a topic rises and falls, and how it compares between countries, states, metro areas and cities. Beyond the website's chart downloads there is no open API, so tools pull data through unofficial clients such as pytrends, which quickly run into 429 Too Many Requests errors (pytrends' own repository was archived in April 2025). Google's official Trends API is still in alpha for approved testers, so most teams combine careful pacing with requests spread across many IPs.
How Google Trends localises, limits and checks traffic, and what that means for your setup.
Each website chart is scaled to its own peak for the chosen terms, time range and location. Change any of them and every value is rescaled, so store the exact request with each result.
Trends is built from a sample of Google searches, so the same request can return slightly different values on different days. Compare terms inside one request, or average several pulls.
Unofficial clients call the same endpoints as the website, and Google answers fast or repeated calls with 429 errors. The limit is not published: slow down and back off when it appears.
Google announced a Trends API alpha in July 2025, with consistently scaled data across requests, a rolling five-year window and region and sub-region breakdowns. Access is by application, so use it first if you're accepted.
Our recommendation for Google Trends, and when the second option is the better choice.
Trends limits how fast one IP can request data, so 429 errors arrive per address. Rotating residential proxies spread requests across ordinary home IPs, and country targeting lets you open the website as visitors in each market do.
Residential IPs in 190+ countries with country, state and city targeting. Rotate on every request or hold a sticky session for up to 24 hours; GB never expire.
If you pull a small, fixed set of comparisons every day, static ISP proxies give you a few dedicated US or Canadian IPs with unlimited bandwidth. Split the schedule across them and keep the pace slow.
Dedicated static IPs registered to US and Canadian ISPs. The address stays the same for as long as you hold it, with unlimited bandwidth and HTTP(S) or SOCKS5 access.
Every CleanProxies proxy connects over HTTP(S) with the credentials in your dashboard; ISP and ISP subnet proxies also run SOCKS5. Test them with the free proxy checker and convert lists with the proxy list formatter.
If Trends data is central to your product, apply for Google's alpha. Its consistently scaled data removes the rescaling problem.
List each term set, time range, location and category, and keep one anchor term in every comparison so batches can be joined.
Send requests through rotating residential proxies a few at a time, and wait longer after each 429 before retrying.
Save every response with its parameters and date, and re-pull only the recent period instead of the full history.
Google's terms restrict automated access to its services, and unofficial Trends clients are not supported by Google. Keep volumes low, prefer the official Trends API if you have access, and use the data for analysis. Trends values show relative interest, not search volume, so label them that way in reports. CleanProxies customers must follow our Terms of Service and the laws that apply to them; this page is general guidance, not legal advice.
Setup guides and best practices from the CleanProxies blog.
Guides for websites that check and limit traffic in similar ways.
Localized rank tracking and SERP research by country and city.
Learn MoreCity-level ad checks, assets and landing page geo-redirects.
Learn MoreRank tracking and Microsoft Advertising checks by market and city.
Learn MorePrices, sellers and Shopping placements by country and city.
Learn MoreStraight answers about running proxies on Google Trends.
Google limits how fast one IP can call the Trends endpoints, and the limit isn't published. Slow down, cache results and spread requests across rotating residential IPs with backoff. pytrends is archived, so it won't get fixes for Google's changes.