---
title: "Trending searches"
method: GET
path: "/v1/google/trends/trending"
tags: ["Google Trends"]
---

# Trending searches

`GET /v1/google/trends/trending`

Get trending searches with related queries via Google's TrendsUi.

Primary path: ``POST /_/TrendsUi/data/batchexecute?rpcids=i0OFE``,
Google's internal RPC backend for the ``/trending`` page. This
endpoint is **not** protected by SearchGuard / BotGuard — no
cookies or anti-abuse token required — and returns the trending
list **with related queries embedded per trend** (10-25 queries
each), the same data that powers the trending UI's expanded view.

Fallback: ``GET /trending/rss?geo=US`` — also cookieless but
returns only title + approximate traffic, no related queries.

Verified working 2026-05-08 (research from a parallel investigation
confirmed 30 rapid bursts from one IP all returned 200, payloads
145 KB - 1 MB).

## Query parameters

- `geo` string — Country code
- `hl` string
- `hours` integer — Hours-back window for the trending list. Google supports 24, 48, 168 (= 1 week).

## Response `200`

Successful Response

- TrendsTrendingResponse — Response for GET /api/v1/trends/trending.
  - `trending` TrendsTrendingItem[]
    - `title` string, required
    - `traffic` string, nullable
    - `articles` TrendsTrendingArticle[]
      - `title` string, required
      - `link` string, nullable
      - `source` string, nullable
      - `thumbnail` string, nullable
  - `country` string

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/scrapebadger/apis/scrapebadger-account-api.md) · [All operations](https://skmtc.net/scrapebadger/apis/scrapebadger-account-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/scrapebadger/scrapebadger-account-api/versions/4a1ef8777baf/schema)