Google Trends hub

Google Trends Related Queries API

The top and rising searches around one term, with relative values and breakout rows kept distinct.

GET /v1/google-trends/related-queries

1 credit Failed requests are free

About this endpoint

GET /v1/google-trends/related-queries takes one query plus geo, time, and optional category, source and language. It returns two lists. data.top[] holds up to 25 queries with a value from 0 to 100 relative to the leading query. data.rising[] holds up to 25 queries with change.percent for a measured rise, or change.breakout: true when the rise is too large to put on the same scale, in which case change.percent is null.

When both lists are empty the answer is lookupStatus: "no_data" with empty arrays. The query list is fixed at one term: send a second term and the schema refuses the request before any lookup.

Google Trends Related Queries API FAQ

What does a breakout mean?

A breakout is a rise too large to express on the usual percentage scale. The row has change.breakout true and change.percent null, so treat it as a strong signal rather than a missing number.

Are the values comparable between terms?

No. top values are relative to the leading query in that request, so compare rows inside one answer, not across answers.

How many related queries come back?

The answer carries up to 25 top and up to 25 rising queries. The response allows up to 50 in each array for shape stability, but Google Trends lists at most 25.

Can I ask for more than one term?

No. This route takes exactly one term. Use interest over time or interest by region when you need to compare up to five.

What does no_data mean here?

Both lists are empty for a valid request, often for a term with little related activity. HTTP is 200 and lookupStatus is no_data, not an error.

How much does a related-query lookup cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.