Compare keywords by region: which term wins where
Put your product against a rival and get the winner in every state from one call. €0.0015 per call, about 51 rows for the US.
AutomaticPaste a Google Trends link, choose Compare regions, and we use this API for you.trends.google.com/trends/explore?q=…
- per 1,000 calls
- €1.50
- per call
- €0.0015
- 0.15 cents
- rows per call
- up to 51
- per 1,000 rows
- ≈ €0.0294
Head to head, state by state
The compare regions API takes a Google Trends link with two or more search terms and tells you which one people search more in each region. For the US that's about 51 rows, the 50 states plus Washington DC, from one call at €0.0015. A thousand comparisons cost €1.50. All other sources and prices are on our data APIs page. Save the link once, and every run's regional scoreboard is stored in your Scrapewise account for the table, Excel, your AI assistant or the API.
Each row answers one question: in this state, which of my terms leads? The answer is a number that points back to your list. 0 is the first term in your link, 1 the second, and so on.
We tested it on 16 September 2026 with bitcoin against ethereum in the US. Bitcoin led in all 51 regions. A clean sweep is an answer too. If you'd been planning a regional campaign for the second term, you'd know there's no state where it's ahead.
This page is for match-ups. If you only care about one keyword and want to know how strong it is in each state, the interest by region API scores one term from 0 to 100 per region. Use this one when the question has a "versus" in it.
Who compares terms by region
Brands with a named rival
Your brand against the market leader. Find the states where you already win and spend there first, and the states where you lose before a rep flies out.
Sellers writing local listings
Do shoppers in Georgia type "sneakers" or "tennis shoes"? Compare the two and use the winning word in titles and ads for that area.
Multi-warehouse sellers
Stock the variant that wins in each warehouse's states. A two-term comparison per product line tells you which color, flavor or size name leads where.
How it works
List your terms
Compare two or more terms on Google Trends, like stanley cup and yeti tumbler, copy the link and pick Compare regions. The term order in the link is how you'll read the results.
Pick a range and schedule
Country and time range come from the link. Schedule it monthly, and each run is saved with its date.
Read the leader per region
Count rows per term in the table or Excel, pull rows by API, or ask your AI assistant: 'in how many states does stanley cup lead this month?'
Set it up once. The data keeps coming.
Save your search once and it runs by itself. Every run lands in your own Scrapewise database, and you pick how to read it.
Set it up once
Add your ASINs, keywords, places or apps to a scraper in the web app. New accounts get 5 free requests.
Runs on your schedule
Pick daily, weekly on the days you choose, every few days, or the first or last day of the month. Scheduled runs start at night, European time. Need it more often? Start runs from your own code.
Saved in your database
Each run adds dated rows, so this week sits next to last week. Rows are kept for 90 days.
Use it your way
Open the table in the web app and download the latest run as an Excel file. Ask your own AI assistant about it. Or pull the rows into your code with an API key.
Ask your AI assistant about your own data
Connect Claude Desktop or Claude Code with a read-only key. The assistant reads the rows you've already collected, at no extra cost on Scrapewise. With a full-access key it can start a run for you too.
- Which of my ASINs lost the Buy Box this week?
- Which competitor cut prices the most since Monday?
- Show the keywords where I dropped out of the top 10.
What you send and what you get back
You paste a Google Trends link that compares two or more terms. Country and time range come from the link. You get one row per region with its name, its code and the index of the leading term.
- Link to Google Trendsrequired
Compare your terms on Google Trends, then copy the address. Terms, country and time range come from the link.
https://trends.google.com/trends/explore?date=today%2012-m&geo=US&q=air%20fryer,slow%20cooker&hl=en - What do you want from this Trends link?required
- Over time and by region
- Interest over time
- Interest by region
- Compare regions
- Related queries
- Related topics
Up to 51 rows per call, 12 columns
- sw status
- sw source url
- sw fetched at
- geo
- location
- max_value_index
- value
- extracted_value
- ctx_search_parameters_q
- ctx_search_parameters_geo
- ctx_search_parameters_date
- ctx_search_metadata_google_trends_url
Sample rows: "bitcoin, ethereum" in the US
Real rows from a call on 16 September 2026, past 12 months. max value index 0 means bitcoin, the first term, leads in that state. The value fields came back empty on this comparison, so read the leader column.
All 12 columns
- sw status
- sw source url
- sw fetched at
- geo
- location
- max_value_index
- value
- extracted_value
- ctx_search_parameters_q
- ctx_search_parameters_geo
- ctx_search_parameters_date
- ctx_search_metadata_google_trends_url
sw status_sw_statusResult of this row: OK, no results, or an error | sw source url_sw_source_urlThe link you pasted for this request | sw fetched at_sw_fetched_atWhen we collected this row (UTC) | geogeoRegion code | locationlocationRegion name | max_value_indexmax_value_indexMax value index | valuevalueValue as shown | extracted_valueextracted_valueNumeric value | ctx_search_parameters_qctx_search_parameters_qRequest context: search parameters q | ctx_search_parameters_geoctx_search_parameters_geoRequest context: search parameters geo | ctx_search_parameters_datectx_search_parameters_dateRequest context: search parameters date | ctx_search_metadata_google_trends_urlctx_search_metadata_google_trends_urlRequest context: search metadata google trends url |
|---|---|---|---|---|---|---|---|---|---|---|---|
| OK | https://trends.google.com/trends/explore?q=bitcoin%2Cethereum&geo=US | 2026-09-16T11:11:42Z | US-AK | Alaska | 0 | 0 | bitcoin,ethereum | US | today 12-m | https://trends.google.com/trends/embed/explore/GEO_MAP?hl=en&tz=420&req=%7B%22category%22%3A0%2C%22comparisonItem%22%3A%5B%7B%22geo%22%3A%22US%22%2C%22keyword%22%3A%22bitcoin%2Cethereum%22%2C%22time%22%3A%22today+12-m%22%7D%5D%2C%22property%22%3A%22%22%7D | |
| OK | https://trends.google.com/trends/explore?q=bitcoin%2Cethereum&geo=US | 2026-09-16T11:12:19Z | US-AL | Alabama | 0 | 0 | bitcoin,ethereum | US | today 12-m | https://trends.google.com/trends/embed/explore/GEO_MAP?hl=en&tz=420&req=%7B%22category%22%3A0%2C%22comparisonItem%22%3A%5B%7B%22geo%22%3A%22US%22%2C%22keyword%22%3A%22bitcoin%2Cethereum%22%2C%22time%22%3A%22today+12-m%22%7D%5D%2C%22property%22%3A%22%22%7D | |
| OK | https://trends.google.com/trends/explore?q=bitcoin%2Cethereum&geo=US | 2026-09-16T11:12:56Z | US-AR | Arkansas | 0 | 0 | bitcoin,ethereum | US | today 12-m | https://trends.google.com/trends/embed/explore/GEO_MAP?hl=en&tz=420&req=%7B%22category%22%3A0%2C%22comparisonItem%22%3A%5B%7B%22geo%22%3A%22US%22%2C%22keyword%22%3A%22bitcoin%2Cethereum%22%2C%22time%22%3A%22today+12-m%22%7D%5D%2C%22property%22%3A%22%22%7D | |
| OK | https://trends.google.com/trends/explore?q=bitcoin%2Cethereum&geo=US | 2026-09-16T11:13:33Z | US-AZ | Arizona | 0 | 0 | bitcoin,ethereum | US | today 12-m | https://trends.google.com/trends/embed/explore/GEO_MAP?hl=en&tz=420&req=%7B%22category%22%3A0%2C%22comparisonItem%22%3A%5B%7B%22geo%22%3A%22US%22%2C%22keyword%22%3A%22bitcoin%2Cethereum%22%2C%22time%22%3A%22today+12-m%22%7D%5D%2C%22property%22%3A%22%22%7D | |
| OK | https://trends.google.com/trends/explore?q=bitcoin%2Cethereum&geo=US | 2026-09-16T11:14:10Z | US-CA | California | 0 | 0 | bitcoin,ethereum | US | today 12-m | https://trends.google.com/trends/embed/explore/GEO_MAP?hl=en&tz=420&req=%7B%22category%22%3A0%2C%22comparisonItem%22%3A%5B%7B%22geo%22%3A%22US%22%2C%22keyword%22%3A%22bitcoin%2Cethereum%22%2C%22time%22%3A%22today+12-m%22%7D%5D%2C%22property%22%3A%22%22%7D | |
| OK | https://trends.google.com/trends/explore?q=bitcoin%2Cethereum&geo=US | 2026-09-16T11:14:47Z | US-CO | Colorado | 0 | 0 | bitcoin,ethereum | US | today 12-m | https://trends.google.com/trends/embed/explore/GEO_MAP?hl=en&tz=420&req=%7B%22category%22%3A0%2C%22comparisonItem%22%3A%5B%7B%22geo%22%3A%22US%22%2C%22keyword%22%3A%22bitcoin%2Cethereum%22%2C%22time%22%3A%22today+12-m%22%7D%5D%2C%22property%22%3A%22%22%7D | |
| OK | https://trends.google.com/trends/explore?q=bitcoin%2Cethereum&geo=US | 2026-09-16T11:15:24Z | US-CT | Connecticut | 0 | 0 | bitcoin,ethereum | US | today 12-m | https://trends.google.com/trends/embed/explore/GEO_MAP?hl=en&tz=420&req=%7B%22category%22%3A0%2C%22comparisonItem%22%3A%5B%7B%22geo%22%3A%22US%22%2C%22keyword%22%3A%22bitcoin%2Cethereum%22%2C%22time%22%3A%22today+12-m%22%7D%5D%2C%22property%22%3A%22%22%7D | |
| OK | https://trends.google.com/trends/explore?q=bitcoin%2Cethereum&geo=US | 2026-09-16T11:16:01Z | US-DC | District of Columbia | 0 | 0 | bitcoin,ethereum | US | today 12-m | https://trends.google.com/trends/embed/explore/GEO_MAP?hl=en&tz=420&req=%7B%22category%22%3A0%2C%22comparisonItem%22%3A%5B%7B%22geo%22%3A%22US%22%2C%22keyword%22%3A%22bitcoin%2Cethereum%22%2C%22time%22%3A%22today+12-m%22%7D%5D%2C%22property%22%3A%22%22%7D |
What each column means
sw columns tell you where, when and how each row was collected. The others come straight from Google Trends.
The region
location is the region's name and geo its code, like US-AK. Google sorts the list by region code, and geo lets you match rows across monthly runs.
- location
- geo
Who leads
max value index is the answer: 0 for your first term, 1 for the second, and so on. value and extracted value hold a score when Google supplies one. On a comparison they're often empty, as in the sample.
- max_value_index
- value
- extracted_value
Row identity and links
sw source url opens the comparison on Trends. sw status says OK, no results or error, and sw fetched at is when we collected it in UTC.
- sw source url
- sw status
- sw fetched at
Your request
ctx search parameters q holds your full term list in the order you sent it. Keep it next to max value index so 0 and 1 always mean the right thing. Country, range and the Trends link sit beside it.
- ctx_search_parameters_q
- ctx_search_parameters_geo
- ctx_search_parameters_date
- ctx_search_metadata_google_trends_url
What sellers do with a regional match-up
Target ads where you already win
Compare your brand with a rival and put ad budget in states where your index leads. Winning ground is cheaper to hold than losing ground is to take.
Choose the local word
"Soda" or "pop", "hoodie" or "sweatshirt". One call shows which word leads in each state so your listing matches what local buyers type.
Split regional stock
Run one comparison per product line. If the matte version leads in the West and the glossy one in the South, ship accordingly.
Pick test markets
Compare your category term with the older alternative. Launch in states where the new term already leads, because buyers there already know what they're looking for.
Track a rival's spread
Rerun the same pair every month and count how many states each term leads. A rival going from 5 states to 12 is a story worth hearing early.
What it costs in real life
Brand manager watching rivals
Compares the brand with 4 competitors, one pair each, every week. About 17 calls a month, around €0.03.
- calls per month
- 17
- cost per month
- €0.0255
Seller with 3 warehouses
Runs 40 product-variant comparisons once a month to split stock. 40 calls, €0.06.
- calls per month
- 40
- cost per month
- €0.06
Agency with 25 clients
Tracks 3 rival pairs per client every week for regional reports. About 325 calls, roughly €0.49 a month.
- calls per month
- 325
- cost per month
- €0.487
Why use this API for regional match-ups
The winner, not a pile of charts
One row per state with the leading term. No need to pull each keyword separately and line them up yourself.
Your order is kept
The term list from your link is stored on every row, so the leader index still reads correctly months later.
Cents, not a subscription
Four weekly match-ups, one per rival, cost about €0.03 a month. Nothing to pay when you stop.
What your comparisons cost
One comparison is one call at €0.0015, for 2 terms or 5. Enter how many match-ups you run and how often. Compare all data APIs
- Rows (up to)
- 51,000
- You pay
- €1.50
Frequently asked questions
Two or more, in one Trends link. Google Trends compares up to 5 terms at a time, so split longer lists into groups that share one anchor term.
Ready to pull Compare data into your stack?
5 requests are free when you sign up. After that, top up from €5 and pay €0.0015 per comparison. Pay-as-you-go pricing has the details.