Term → page

curl --request GET \
  --url 'https://truestat.io/api/v1/sites/{siteId}/search/term-pages' \
  --header 'Authorization: Bearer <token>'

{
  "data": [
    {
      "path": "/tools/youtube-title-checker",
      "term": "youtube title checker",
      "clicks": 7,
      "hostname": "codivupload.com",
      "impressions": 138
    }
  ],
  "meta": {
    "page": {
      "limit": 100,
      "offset": 0,
      "has_more": false
    },
    "range": {
      "to": "2026-09-16T00:00:00.000Z",
      "tz": "UTC",
      "from": "2025-09-16T00:00:00.000Z",
      "clamped": false
    },
    "site_id": "6fed8980-a119-4a9c-a4d4-53e448ef9f9e"
  }
}

The pairing between a search term and the page Google chose to show for it.

Google's figures — see totals for why they do not reconcile with the rest of your analytics.

The one without a cap

Terms embeds up to three landing pages per term, which is enough for most reading. This endpoint returns every pairing for the terms you name.

Reach for it when three is not enough:

• One term ranks for a dozen of your pages and you want the whole picture

• You are auditing which page Google prefers for a query, and the answer is the wrong page

• You are checking whether two of your pages compete for the same term

terms is required

There is no "all terms" mode. The result is per term, so an unfiltered query would be your site's entire search history crossed with its pages — a large answer to a question nobody asked.

Name the terms, usually the ones terms just returned. There is a cap per request — the terms parameter above states it, and asking for more is refused rather than silently truncated. Send them in batches beyond that.

Separate terms with a newline, not a comma

This matters more than it looks. People search for shoes, red.

Split that on a comma and you look up two terms nobody typed, and both return nothing — which reads as "no data for this term" rather than as a mistake in the request. So the separator is a newline (%0A once url-encoded):

curl -G https://truestat.io/api/v1/sites/$SITE_ID/search/term-pages \
  -H "Authorization: Bearer $TRUESTAT_API_KEY" \
  --data-urlencode "period=last30d" \
  --data-urlencode "terms=youtube title checker
yt title checker"

Reading the result

Rows carry the term back in term, so a response covering several terms can be grouped without tracking the order you sent them in.

A term appearing with two of your pages, both with meaningful clicks, usually means those pages compete for it — and consolidating them tends to rank better than either did alone.

Authorizations

Path parameters

Query parameters

Response