Google Search Console

Four figures per day, two of them averages

Clicks, impressions, CTR and average position are stored per day. Clicks and impressions are summed over a range; CTR and average position are re-derived, because thirty days of CTR is not the sum of thirty daily percentages. On position a lower number is also better, so a rising line reads as a decline rather than as a win.

Movers, against the previous period

The movers drill-down answers the question a marketeer actually asks: which queries moved. It compares average position in the selected range with the equal-length window right before it, per query, and sorts on the size of the change, gains and losses together. Queries missing from either window are left out — with no starting point there is no change to report.

• Top queries with clicks, impressions, CTR and position
• Top pages, each linking out to the page itself
• Movers, with the position change as its own number

Late data heals itself

Search Console only finalises the most recent days two to three days later. So the nightly run does not just fetch yesterday — it re-pulls the whole trailing week and overwrites the days it already had. Figures from the day before yesterday can therefore change once more, by design: the alternative would leave the first, incomplete reading standing forever.

Impressions in AI: through the export button, because not through the API

Since June 2026 Search Console shows how often a site appears in AI Overviews and AI Mode, in a Generative AI report of its own. The Search Console API does not return those figures, and deriving them from the web totals is not possible: they are folded in there with no way to separate them. So schakl. never estimates them. What Google does offer is an export button, and that file you upload on the card on the dashboard. The figure lands as Vertoningen in AI (impressions in AI) beside the other four, on the same daily rows, so the tile, the trend, the comparison, the cross-client overview and the AI Overviews report chapter read it the way they read clicks. For a client nobody has uploaded anything for there is no tile and no chapter: a zero would be a claim about their visibility that nothing on the screen could contradict.

• Export by day: a weekly or monthly export is refused with a sentence, because storing one row as one day would show the month a seventh of its size
• A nightly sync never overwrites an upload
• The card says when the last upload was and which days it covered, because a figure somebody has to upload must say how far it runs
• An assistant can send the same figures as JSON instead of as a file

A read surface of its own, for an assistant too

The dashboard asks Search Console one question: how is this client doing. For everything else (which queries land on which page, whether a URL is indexed and why not, which sitemap has errors, what happened at nine this morning) there is the Google Search Console integration: thirteen read routes in the API, which are also the MCP section /mcp/google-search-console and part of the growth bundle. They store nothing and read live, under the Google consent of whoever asks. Nothing is ever written, so everything stays readable on an expired licence too. Ask an assistant about AI visibility and the answer says honestly that the API does not have that figure, and gives the link to the report.

• Sites and sitemaps, an overview, the split across search types, daily and hourly figures, a breakdown and the movers
• URL inspection: what Google's index knows about one address
• A free-form query with your own dimensions and filters, behind a permission of its own
• An unknown dimension or filter is refused here, with the list that would have worked, before Google is asked