useterra.app / Use cases / Search & rankings
1 providers · free on the account you already own · $0.000 markup

Google Search Console API: clicks, impressions and top queries, read by your agent

Connect the Search Console property you already own and your agent can read the same numbers the UI shows: every query, its clicks, impressions, CTR and average position, for any date range. It runs on your own Google account, so useterra.app never meters it.
Start freeSee the comparison
$1.00 of free credit once per new verified account · no provider signup · no card
1 of 1 endpoints on this page are live-verified against the provider.
Try it

What’s the best way to ask ChatGPT?

1Set your agent up, once
in your agent's chat
set up terra — https://useterra.app/llms.txt
2Ask for the job
the prompt
Using terra, show me the queries useterra.app ranked 8 to 20 for in the last 28 days with more than 50 impressions, sorted by impressions, and tell me which ones have the worst CTR.
works in
ChatGPTClaudeClaude CodeCodexCursorGemini CLI

Why this prompt works

Connect once

One OAuth click for the property you own. useterra.app holds the token, not you.

Ask in plain words

Date ranges, filters and sorting are the agent's job, not yours.

End the window 3 days back

Search Console lags 2 to 3 days; yesterday is preliminary data.

It costs nothing

Your own account, so the call is never metered.

Why useterra.app

Why go through useterra.app

No code to write

Connect once, keep the token server side, and call from any agent.

Nothing to integrate

No SDK, no OAuth dance per vendor, no seats.

How it works

One provider, on the account you already own

Google Search Console answers this job. You connect it once, useterra.app keeps the token server side, and the call is never metered.

the call
terra call google-search-console.performance --data '{"startDate":"2026-07-01","endDate":"2026-07-21","rowLimit":2}'

Every endpoint on this connection is listed on the Google Search Console shelf.

The detail

What actually differs

Ending a window on yesterday silently ends it on preliminary data.

Score a 28-day window that ends 3 days back.

The UI caps the query table at 1,000 rows; the API paginates past that, which is where the long tail lives.

Queries with very low volume are withheld for privacy, so the totals in a query breakdown will not add up to the site total.

That gap is expected.

Background

What is the Search Console API?

The Search Console API returns your site's Google Search performance as data: clicks, impressions, CTR and average position, broken down by query, page, country, device and date. It is the same data as the Performance report, without the UI's row limits, and it is the only first-party source for what people actually searched before they reached you.

Questions

Before you start

Does this cost anything?

No. Search Console runs on your own Google account, so useterra.app relays the call and meters nothing. Only calls on useterra.app's own provider keys are billed.

What do I have to connect?

The Google account that already has access to the property, once, through an OAuth screen. useterra.app stores the token server side; your agent never sees it.

Can my agent see other people's sites?

No. The API returns only the properties your connected account can access.

Which agents can do this?

Any client that can reach useterra.app: ChatGPT, Claude, Claude Code, Cursor and the rest of the supported list.