Skip to main content

Integrations

Google Search Console

Connect Search Console to see the search terms bringing people to your site, alongside what they did once they arrived.

The Keyword tab is empty for most sites, and that is not a fault in your setup. Search engines stopped putting the search term in the referrer years ago, so a visit from Google arrives here saying only "Google". Connecting Search Console reads the terms from Google directly.

What you get

Once connected, the Keyword tab fills in with:

  • Search terms people used to reach you

  • Average position for each term — 1 is the first result, so lower is better

  • Impressions and CTR, so you can see a term that gets shown often and clicked rarely

  • The page each term led to, shown under the term

  • Country, device and search appearance — including whether you appeared in an AI Overview

Every row from Search Console carries a small Search Console mark. It matters because Visitors on those rows is Google's click count, not a visitor we measured: the same term can read differently in the two halves of the panel, and the mark says which half you are looking at.

Search Console terms live on the Keyword tab of the Sources card. Hover a row for its position, impressions and click-through rate.

Hover a row for the full set, or press Show all for the whole list with sortable columns. Sorting starts from the useful end of each column: lowest position first, highest clicks first.

Show all on the Keyword tab. Every column sorts; the long tail is the point — terms with hundreds of impressions and a click or two.

Connecting

Verify the site in Search Console

Your site must already be verified at search.google.com/search-console. You need owner or full user permission on the property — restricted access is not enough to read performance data.

Open the site's Integrations tab

In TrueStat, go to your site's Settings → Integrations and press Connect.

Connecting Search Console: the card before connecting, Connect pressed, and the same card connected after Google grants access
Before connecting. The card says what will be read, what Google keeps back, and how far back the import goes, so there is no surprise after.

Approve read-only access

Google asks you to confirm. TrueStat requests one permission, webmasters.readonly — it can read your Search Console data and change nothing.

Data starts arriving within a few minutes, and refreshes once a day after that.

A brand-new site shows nothing at first, and that is expected. Search Console runs a day or two behind, so a site connected today has no finished day to report yet. TrueStat says so rather than showing an empty table — an empty table would read as "nobody found you in search", which is a different thing.

The first import covers the current month, starting from the day you added the site to TrueStat if that is more recent.

The last two days keep changing. Google finishes counting a day well after it ends, so a recent day can read lower than it will settle at. Those days are marked, and each refresh reaches four days back to pick up the revisions.

What you will not see, and why

Google withholds most search terms. Usually more than half of your clicks arrive with no term attached.

This is Google's decision, not a limitation of this integration — no analytics product can recover those terms. Google hides queries that are rare enough to identify the person who searched.

On a smaller site the share is larger, because Google's threshold is a fixed number of searches rather than a percentage of yours.

Two consequences follow, and both are visible on screen:

Your keyword clicks will not add up to your total clicks. The gap is the withheld terms. Nothing is missing from your account.

A keyword row cannot filter the rest of the dashboard. Google reports terms and pages as separate lists and never says which visitor searched which term. So a keyword cannot narrow your visitor list the way a referrer can — the link simply does not exist in the data. What it can tell you is the page it led to, which is the next section. Any product showing you revenue per keyword is estimating, and cannot tell you when the estimate is wrong.

The page behind each term

Every search term shows the page it led to. Almost always there is exactly one: a search carries a specific intent and Google sends it to the page that matches. When a term does lead to several, the busiest ones are listed.

This is the one place where the two halves meet. Search Console knows a term brought 7 clicks to /pricing; TrueStat knows what happened on /pricing afterwards.

Who saw you, not only who arrived

Search Console reports the people who saw your result, which is a larger group than the ones who came. Someone who searched, found you at position 8 and did not click exists nowhere else in TrueStat — our script never ran for them.

Three breakdowns come from that side:

  • Country — where the searcher was

  • Device — desktop, mobile or tablet

  • Search appearance — how your result was drawn, including AI Overview

Search appearance is reported for the whole date range rather than per day — Google does not break it down by date, so a range gives one figure per type.

Beyond web search

Image, video, news and Discover traffic are fetched too, each counted separately. They are different surfaces and their numbers are never added together: position 3 in image search and position 3 in web search do not mean the same thing.

Most sites have only web traffic, and the other surfaces stay empty.

How far back the data goes

The current month, and never before the day you added the site here.

Google keeps 16 months and we deliberately do not import it. Those months would show search data sitting beside empty conversion and revenue columns — not because nothing converted, but because TrueStat was not measuring your site yet. An absent measurement and a real zero look identical in a table, and reading one as the other leads to exactly the wrong conclusion about a page.

Your older data is still in Search Console, where you can see it any time.

Keeping it current

Data refreshes once a day, and each refresh re-reads the last five days rather than only the newest one. Google keeps revising recent days as it finishes counting, and a single-day refresh would freeze whatever partial number happened to be there first.

Disconnecting

Settings → Integrations → Disconnect removes the stored authorisation and stops future syncing. Search data already imported stays on your dashboard; delete the site to remove it.

You can also revoke access from Google's side at myaccount.google.com/permissions. If you do that, syncing stops and the Integrations tab shows the connection needs renewing.

If something is not working

Was this page helpful?

Last updated September 14, 2026