Search Console, Honestly
Search Console is Google’s reporting interface for how your site appears and receives clicks in Google Search surfaces. Its performance metrics describe result exposure, not your whole website analytics, true demand, or an absolute ranking truth, so impressions, clicks, CTR, and average position must be read through their grouping and filters.
The problem is that Search Console looks deceptively like a simple SEO scorecard. Engineers see clicks, impressions, CTR, and average position, then infer demand, page quality, ranking movement, or conversion potential. Those inferences are often too strong. The data is about Google result events, sliced through a reporting interface. It is useful, but it is not a complete analytics system and it does not measure every user who wanted the thing you offer.
A practical model is a large table keyed by things such as query, URL, country, device, date, and search appearance. An impression is counted when a result is eligible to be seen in Google’s results. A click is a Google-recorded click from search. CTR is clicks divided by impressions. Average position is the mean position of the highest result from your site across the counted impressions, not a fixed rank for a page.
The trade-off is aggregation. Changing the dimension changes the question being answered. Query reports show which searches exposed you; page reports show which URLs received exposure. CTR is not safely comparable across unlike query mixes, devices, or result layouts. Average position can worsen because you appeared for more broad, low-rank queries, not because existing rankings fell. Filters also change the denominator, so filtered and unfiltered totals are easy to misread.
Engineers meet this in performance reports, dashboards, exports, and the Search Console API. The disciplined workflow is to compare like with like, then segment by query, page, device, country, and date until the change has a plausible mechanism. Ask whether you are seeing ranking movement, demand change, query mix change, a SERP layout effect, or a reporting artefact. The honest answer is often: it depends on what was counted.
Common questions
- Is average position my Google ranking?
- Not in the way people usually mean it. Average position is averaged over the impressions included in the report, using your topmost result for those impressions. If the query mix, country mix, device mix, or filters change, the number can move even when important rankings are broadly stable.
- Why do page totals and query totals not always tell the same story?
- They group different things. A page can receive impressions from many unrelated searches, while a query can expose several URLs from the same site over time. Once data is grouped, filtered, and averaged, the headline figures answer different questions. Treat them as different views of search exposure, not perfectly reconcilable ledgers.
- Can I use CTR to judge whether a title or snippet is good?
- Sometimes, but only after controlling for the comparison. CTR depends on intent, position, device, brand familiarity, ads, rich results, and the kind of query. A lower CTR can mean worse snippet appeal, but it can also mean broader impressions, lower-intent searches, or a changed results page.