Google Search Console
Takt measures what happens on your site. Search Console measures what happens before: the Google searches you show up in, the ones people click, and at which position. A site’s Search Console tab pulls those numbers next to your analytics, over the same period.
What the tab shows
For the selected period, for the linked property:
- clicks, impressions, CTR and average position;
- a day by day series of clicks and impressions;
- the queries you show up for;
- the pages that collect those impressions;
- countries and devices.
Every row carries its four metrics, so a query with plenty of impressions and no click stands out immediately.
The queries and pages tables cross each other. The chevron at the end of a row opens, right under it, the detail for that single value: a page shows its queries, countries and devices; a query shows its pages, countries and devices. The totals at the top of the expansion cover only the opened value, and clicking a page listed inside an expansion opens its own.
Linking a property
You need a Google account that has already verified your site in Search Console. Linking a property neither verifies nor creates it: Takt only reads what Google already agrees to show you.
- Open Settings on the site, section Google Search Console.
- Click Connect a Google account. The Google consent screen lists the permissions being requested.
- Keep the Search Console permission ticked. Google shows it as a checkbox you can untick; if you do, Takt stays connected but the tab stays empty.
- Pick the property in the list, then Link. Takt preselects the one matching the site domain.
Two measurements that do not line up
Search Console clicks and Takt visitors are not counting the same thing, and they will never match exactly.
| Search Console | Takt | |
|---|---|---|
| Who measures | Google, on the results page | Takt, on your page |
| The unit | a click on a result | a visitor, a visit, a pageview |
| Scope | Google search only | every source |
| Delay | two to three days | real time |
A click that never reaches your page (instant back, dropped network, blocker) is counted by Google and not by Takt. The other way around, Takt sees traffic from everywhere else, which Search Console knows nothing about.
The pages table still carries an Entries column: the visitors Takt measured whose visit started on that path, over the same period. The two sources are matched on the URL path, the only honest key they share. A zero means no visit started there; a dash means Takt could not compute the value, not that it is zero. A domain property covers every subdomain: pages on a host other than the tracked one show a dash rather than a number borrowed from the site.
Those two columns are not a funnel: entries count every source, not just Google. Read side by side they say something else, something more useful. A page clicked a lot in the results with almost no measured entry deserves a look (redirect, slow page, blockers). A page with plenty of entries and a distant average position has room to gain on the search side.
Freshness and limits
- Google publishes this data two to three days late. The last days of a recent period are partial, not wrong: they fill in on their own.
- Search Console history stops at 16 months. An older period comes back empty.
- Each block is capped at the top 1,000 rows, ranked by clicks.
- The reconciliation reads Takt’s top 1,000 entry paths for the period. A page far down that tail can therefore show zero entries.
- Responses are cached for about thirty minutes. A freshly linked property can take a moment to fill in. An expansion has its own cache, per opened value.
- Google omits rare queries to protect searchers’ privacy. The queries always add up to less than the total shown at the top: that gap is expected.
Unlinking
The Unlink button removes the property from the site: the tab stops showing data, and the Google connection stays in place for the GA4 import. To cut Takt’s access to your Google account entirely, disconnect it from the Data import section, or revoke access in your Google account permissions.
Next
- AI visibility for traffic coming from assistants.
- Goals to tie that traffic to a conversion.
- Privacy for what Takt collects, and what it does not.