Google Search volume API

Google Trends shows relative interest on a 0-100 scale. This page documents how to pull estimated absolute weekly query volume for any keyword through the Trends MCP REST API, read the volume field in responses, and pair it with growth calculations.

The Google Trends website caps out at relative interest. A keyword scoring 80 tells you nothing about whether that means 8,000 or 8 million weekly searches. The volume field in Trends MCP responses closes that gap for the google search source.

Endpoint

POST https://api.trendsmcp.ai/api
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

One endpoint handles time series, growth, and live trending feeds. For volume data, use source: "google search" with any keyword.

Get a time series with volume

Request weekly history. Each data point returns value (normalized 0-100) and volume (estimated weekly query count).

{
  "source": "google search",
  "keyword": "artificial intelligence"
}

Response excerpt (Trends MCP API snapshot, June 19 2026):

[
  {
    "date": "2026-05-30",
    "value": 100,
    "volume": 1314655,
    "keyword": "artificial intelligence",
    "source": "google search"
  },
  {
    "date": "2026-06-13",
    "value": 38,
    "volume": 499569,
    "keyword": "artificial intelligence",
    "source": "google search"
  }
]

The May 30 point hit the normalized ceiling (100) at roughly 1.3 million estimated weekly queries. The June 13 reading dropped to 38 on the index with volume near 500,000. Both fields move together, but volume gives the order of magnitude that relative scores hide.

Daily mode for the last 30 days:

{
  "source": "google search",
  "keyword": "artificial intelligence",
  "data_mode": "daily"
}

Measure growth on volume

Growth responses include volume_available, recent_volume, baseline_volume, and volume_growth when absolute counts exist for both endpoints.

{
  "source": "google search",
  "keyword": "nike",
  "percent_growth": ["12M", "3M"]
}

Response excerpt (June 19 2026):

{
  "search_term": "nike",
  "data_source": "google search",
  "results": [
    {
      "period": "12M",
      "growth": 5.36,
      "direction": "increase",
      "volume_available": true,
      "recent_volume": 17657452,
      "baseline_volume": 16759615,
      "volume_growth": 5.36
    },
    {
      "period": "3M",
      "growth": -6.35,
      "direction": "decrease",
      "volume_available": true,
      "recent_volume": 17657452,
      "baseline_volume": 18854567,
      "volume_growth": -6.35
    }
  ]
}

Nike's normalized index rose 5.4% year over year while the three-month window shows a 6.4% pullback. The volume fields confirm the same direction, which matters when the normalized score compresses near seasonal peaks.

Custom date windows work for event analysis:

{
  "source": "google search",
  "keyword": "artificial intelligence",
  "percent_growth": [
    { "name": "post-GPT-5 spike", "recent": "2026-06-13", "baseline": "2026-05-16" }
  ]
}

Preset periods: 7D 14D 30D 1M 2M 3M 6M 9M 12M 1Y 18M 24M 2Y 36M 3Y 48M 60M 5Y MTD QTD YTD

How value and volume relate

The normalized value field rescales each keyword to its own peak within the returned window. Two keywords both at 80 are not guaranteed equal absolute demand. The volume field removes that ambiguity for google search.

Field What it measures Best for
value Relative interest, 0-100 Comparing shape and timing across keywords
volume Estimated weekly query count Sizing market demand, ranking keywords by magnitude
volume_growth Percent change in absolute volume Reporting growth in real query terms

When comparing keywords, pull separate calls and compare volume on the same date. Do not compare raw value scores across different keywords without volume context.

What this does not replace

Google Keyword Planner still holds the official numbers for paid search planning. Trends MCP volume estimates serve research workflows: content prioritization, market sizing direction, and AI agent reasoning. The Google Trends data page covers MCP setup and live trending feeds; this page focuses on the volume field inside REST responses.

Code examples

Python

import requests

res = requests.post(
    "https://api.trendsmcp.ai/api",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    json={"source": "google search", "keyword": "artificial intelligence"}
)
series = res.json()
latest = series[-1]
print(f"Index: {latest['value']}, Volume: {latest['volume']:,}")

JavaScript

const res = await fetch("https://api.trendsmcp.ai/api", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_API_KEY",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({ source: "google search", keyword: "artificial intelligence" })
});
const series = await res.json();
const latest = series[series.length - 1];
console.log(`Index: ${latest.value}, Volume: ${latest.volume}`);

cURL

curl -X POST https://api.trendsmcp.ai/api \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"source": "google search", "keyword": "nike", "percent_growth": ["12M"]}'

get_trends

Pull a weekly time series with both normalized value and absolute volume for any Google Search keyword.

get_trends(keyword='artificial intelligence', source='google search', data_mode='weekly')

get_growth

Calculate period growth on both the normalized index and absolute volume when volume_available is true.

get_growth(keyword='nike', source='google search', percent_growth=['12M', '3M'])

Common questions

No. Google Keyword Planner and Google Trends both withhold programmatic access to absolute query counts. Trends MCP returns directionally accurate volume estimates derived from its search interest pipeline. Suitable for trend comparison and momentum analysis, not for paid search budgeting.
value is the normalized 0-100 interest index, comparable across keywords and time periods. volume is the estimated absolute weekly query count for that keyword. A keyword at value 50 with volume 500,000 has roughly half the search demand of one at value 100 with volume 1,000,000.
Some sources in Trends MCP return volume as null when absolute counts are unavailable. For google search, volume is populated on most weekly data points. If volume is null on a specific date, the normalized value field still works for trend direction.
Estimates track relative changes reliably. Absolute numbers are modeled, not audited Google reporting. Cross-keyword ranking (which term has more volume) is generally trustworthy. Treat single-week counts as directional, not exact.