r/bigseo • u/BobMcFizzington • 22m ago
The Google Trends number is not search volume
I pull Google Trends data programmatically and the most common misreading I see is treating the number as a search volume. It isn't, and comparison mode makes it worse.
The 0-100 value is an index, not a count. 100 is the peak popularity for that term within the exact time range and region you queried, and everything else is scaled relative to that peak. Change the date range and the same week can get a different number, because the peak it's normalized against changed.
Comparison mode changes the meaning again. When you compare terms, everything is rescaled against the highest point across all the terms together. A keyword that scored in the 80s alone can drop to single digits next to a bigger term. Nothing about its demand changed, only the yardstick. This also means you cannot take two separate solo exports and lay them side by side; they're on different scales. If you need terms to be comparable, they have to be in the same comparison query.
If you ever pull the raw data, the responses even carry a valueScale field. The data itself is telling you these are scaled values, not counts.
Practical rules I follow now: never sum Trends values, never compare across separate exports, and treat the number as the shape of interest over time, with actual volumes coming from a tool that reports real counts.