Not all numbers in Search Console are equally reliable. Clicks are the clearest metric because they count a real event. Average position is the most misleading: it is an average across dozens of different queries and tells almost nothing about a single page's "position." Below, each metric is examined in terms of what it measures and where it can mislead.
Where the Data Comes From and How Much It Lags
Search Console reports are built from Google's own logs — meaning they do not depend on any script or counter on the site. For this reason, the number of clicks here will never exactly match the "organic session" shown by GA4 or Metrika: browser extensions, ad blockers, and pages closed before fully loading are missed by the on-site counter.
The data is not real-time. The last one or two days in the Performance report are usually incomplete, so it is incorrect to conclude that "traffic dropped yesterday" based on yesterday's row. History is stored for 16 months — if you need older data, you should export it monthly and keep it yourself.
Another important aspect: property type. sc-domain: (Domain property) covers all subdomains and both protocols, while a URL-prefix property covers only that exact prefix. If the numbers differ between two properties, the reason is often this.
What Average Position Measures
Average position is the average of the best position your page achieved in each impression. Two problems are hidden in this definition.
First — averaging. If a page ranks 3rd for one query and 40th for twenty other queries, the report shows a number around 35. No decision can be made based on that number — it hides both situations.
Second — position is calculated only for cases where there was an impression. If a page drops to 60th and is not shown at all, that query does not enter the average, and the position appears to have improved. When traffic is declining, the "growth" in position is exactly this effect.
Practical rule: always filter position by query + country + device. Average position without filters is a decorative number.
Metrics Table
| Metric | What It Measures | Typical Mistake |
|---|---|---|
| Clicks | Clicks from search results to your site | Most reliable; assuming it is an error when compared with GA4 |
| Impressions | Times the result was shown | Treating any increase as always good |
| CTR | Clicks / Impressions | Comparing different positions together |
| Position | Average of the highest position | Viewing it without filters and interpreting it as the page's "position" |
If impressions are growing but clicks are not, this usually indicates that the site has started appearing for new but long (lower-ranking) queries. This is not bad in itself, but presenting a report saying "impressions increased" as a result is a waste of effort.
Why the query list is incomplete
In the Performance report, the sum of the rows is always lower than the total figure. There are two reasons.
First — Google removes rare queries that may contain personal information (anonymized queries). These remain in the total number of clicks, but they do not appear in the query table. The official explanation is provided in the Search Console documentation.
Second — the interface table displays a limited number of rows. For a large website, this is a serious limitation: there may be hundreds of thousands of queries, while you only see the top 1,000. The solution is to export the data via the Search Console API or Looker Studio, then group it on your end.
For this reason, do not conclude that “we have no traffic for this query” based only on the interface table.
Statuses in the Indexing Report
The list of reasons in the Pages report is the most valuable source of information about your site's technical condition, but the names are confusing.
- Crawled — currently not indexed: Google crawled the page but did not add it to the index. This is almost always a quality and duplication issue: thin content, text very similar to other pages, or a page left without internal links.
- Discovered — currently not indexed: Google knows about the page but has not crawled it yet. This is more closely related to crawl budget and server response speed.
- Duplicate, Google chose different canonical: your canonical was ignored. The cause is often that internal links point to a different URL.
- Excluded by 'noindex' tag: the most common accidental error — a meta tag carried over from a test environment.
Reviewing this list once a month, along with the other items in the SEO audit checklist, catches many problems early.
URL Inspection: Two Different Answers
URL Inspection provides two types of information, and they are often confused. The result shown when opened is about the indexed version, i.e., the state Google last saw. The "Test live URL" button, however, requests the page right now.
A useful real-world scenario: you fixed the page, but the report still shows the old error. If the live test returns a clean response — the fix worked, and you're only waiting for reindexing. If the live test also returns an error — the issue is still present.
The live test also shows the HTML rendered by JavaScript. If your page content is rendered via JavaScript, this is exactly where you check whether it is visible.
Discover and Google News Are Counted Separately
This is important for sites that publish news or blogs: Discover traffic does not appear in the "Search results" section of the Performance report. There is a separate "Discover" report in the left menu (it appears only when there is sufficient traffic).
Therefore, when discussing "traffic from Google," it is necessary to clarify which report is being referred to. In media projects, Discover can account for a significant share — in the Zamin.uz experience, a news site's traffic mix is not limited to search results only. Discover visibility responds differently to title, image size, and page speed than search does.
How to Read the Report
A sequence that works for each monthly review:
- Pages → Indexing: Does the number of indexed pages differ significantly from what is expected? If so, start with the list of reasons.
- Performance → 3-month comparison: Click trends. Look only at clicks; don’t look at position yet.
- Filter by pages: Which URLs dropped? If one or two pages dropped — it’s a page issue; if everything dropped evenly — it’s a site or algorithm issue.
- Open the dropped page by query: Which query disappeared, and what changed in the SERP for it?
- URL Inspection: Does the indexed version of that page match the current version?
The point of this sequence is to move from the overall number to a specific page, and from the page to a specific query. Working in the opposite direction takes more time and often leads to the wrong conclusion.
Frequently Asked Questions
Why don't Search Console and GA4 numbers match?
They are measured in different places: Search Console on Google's side, GA4 on the site's side. Blockers, pages that close quickly, and bot filters cause discrepancies. A difference in the 10–30% range is normal; if the difference is several times larger, check that the GA4 code is running on all pages.
When does a new site start showing data in Search Console?
Data appears once the site begins to be indexed — this can take anywhere from a few days to a few weeks, and no exact timeframe is guaranteed. Submitting a sitemap and adding internal links from the homepage speeds up the process.
Can I analyze it myself, or do I need a specialist?
A site owner can independently follow the 5-step process above — it doesn't require specialized knowledge. A specialist is usually needed at the next stage: once the cause is found, fixing it may require technical or content work. The Services page explains how each type of work is carried out.
Is traffic from AI search visible in Search Console?
Clicks from links inside AI Overviews are included in the overall part of the Performance report, but not separately broken out — meaning they cannot be distinguished from other results. Traffic from external services such as ChatGPT or Perplexity does not appear in Search Console at all; you need to look for it in GA4 referral sources. This topic is covered in detail in the Visibility in AI search article.
The main value of Search Console is not in the growth chart, but in narrowing a problem down to a specific page. A review that begins with click trends and ends with indexing causes and URL Inspection takes about one hour per month and usually reveals several quietly underperforming pages.