Google Search Console: Where to Start
Google Search Console is a free service where Google shows you its data about your site: which queries surface it, what made it into the index and what did not, and which pages Search considers a problem. It is the only source of that data — no third-party service has it, they all estimate.
The lesson follows the service's own help: the performance report and how impressions, position and clicks are counted. The second one is read less often, and it explains almost every discrepancy that makes people stop trusting the tool.
Google Search Console is Google's free diagnostic dashboard. It exposes queries, impressions, clicks, CTR, average position, indexing status, sitemaps, crawl issues and messages from Google. An audit starts here not by tradition but because every other tool works with estimates, and this one holds Search's own data.
Why an SEO needs Google Search Console
The service answers two questions: how Google sees the site and how people meet it in search. It does not replace analytics: Search Console shows what happens before the click — impressions, queries, positions, CTR, indexing. GA4 shows what happened after: sessions, engagement, conversions.
The before/after split is not a formality. It sorts problems into two classes immediately: impressions but no clicks means the results page and the snippet; clicks but no result means the page itself. Getting the class wrong means a month spent fixing the wrong thing.
What to Check on Day One
1. Verify the right property
For a new project, the best starting point is a Domain property: it covers http/https, www/non-www and subdomains. If you only have a URL-prefix property, make sure it matches the live version of the site.
2. Open Performance → Search results
The four core metrics are clicks, impressions, CTR and average position. Do not look only at clicks. A page with many impressions and weak CTR is a ready-made snippet task. Queries in positions 4-10 are good optimization candidates because Google already considers the page relevant.
3. Check Pages / Page indexing
Indexation does not mean "the page exists"; it means Google is willing to show it in Search. Look beyond the number of indexed URLs and read exclusion reasons such as Crawled - currently not indexed, Discovered - currently not indexed, Duplicate without user-selected canonical, Alternate page with proper canonical, Blocked by robots.txt and Excluded by noindex.
4. Use URL Inspection for important pages
URL Inspection shows the status of one URL: whether Google knows it, when it was last crawled, which canonical the site declares and which canonical Google selected. If organic traffic suddenly disappears, start here.
5. Check Sitemaps
A sitemap does not guarantee indexation, but it helps Google discover important URLs and notice changes faster. In the Sitemaps report, check processing status, discovered URLs and errors such as Couldn't fetch or Has errors.
6. Open Manual actions and Security issues
Usually these reports should be empty. If there is a manual action or security issue, it takes priority over rewriting content or expanding keywords.
What counts as a click, an impression and a position
These definitions are worth one careful read — they answer most of the "why do the numbers disagree" questions. Everything below is from the help page on impressions, position and clicks.
| What the help says | What follows from it |
|---|---|
| A click is counted when the person leaves Google. Clicking a link that stays inside the platform is not counted | Some of the interaction with your brand in the results never reaches the report at all |
| Ads do not occupy a search position | Position 1 in the report does not mean the top of the screen: ads, a map or a questions block can sit above you |
| Position is the topmost link to your site among the results, averaged across queries | If a page appears twice, the report takes the higher appearance, not the average of the two |
| A featured snippet typically occupies position 1 | An average position of 1 can mean "our passage is in the answer block", not "we top the list" |
Hence the main conclusion about comparing with analytics: Search Console and GA4 count different events by different rules, and they are not obliged to agree. Hunting for the "correct" number is pointless — each report answers its own question. Comparing them is useful only for direction: did it fall in both places or in only one?
Where AI traffic sits in the reports
Everyone who finished the AI module asks it: how do you separate visits that came from an AI answer? The short answer is that you cannot, and that is documented. Pages that appear in AI features are counted in the overall search traffic of the performance report, under the "Web" search type — as stated in the documentation on AI features. There is no separate row.
So the measurement is indirect: split queries into those where an AI answer appears and those where it does not, then compare the direction within each group. The method is in the AI lesson; what matters here is simpler — do not go looking in the interface for a filter that does not exist.
How to read the metrics without fooling yourself
| Metric | How to read it | The usual mistake |
|---|---|---|
| Impressions | How often a link to the site could have been seen in Google. | Treating every impression as useful. What matters is impressions on queries that suit you. |
| Clicks | Visits from Google to the site — only those that leave the platform. | Comparing them one to one with GA4. |
| CTR | Clicks divided by impressions. Shows how well the snippet earns the visit. | Judging CTR apart from position and from whatever sits above on screen. |
| Average position | The averaged topmost position of a link to the site across impressions. | Reading it as the exact spot every person saw. |
The CTR lens works these metrics on your own data (where CTR is below normal at the same position) and the lost clicks finder shows where impressions stayed and clicks left. The glossary covers the terms: CTR and index coverage.
Alex's rule: once a week, look at three reports: performance by page, performance by query, and page indexing. That is enough to catch a CTR drop, important pages falling out of the index, and new technical problems in time.
A starter checklist for a new project
- Add and verify a Domain property — it covers http and https, www and non-www, and subdomains. The verification methods are in the getting started help.
- Submit a sitemap and check how it was processed in the sitemaps report. The glossary covers the term: XML sitemap.
- Run the home page, three to five commercial pages and three to five articles through URL Inspection. The URL auditor does it faster.
- Find the pages in the performance report with high impressions and low CTR — that is a ready-made list of snippets to rewrite.
- Write down, from the page indexing report, why the important pages are not in the index. The glossary covers the term: canonical.
- Link Search Console to GA4 so you can separate a before-the-click problem from an after-the-click one. The GSC export pulls the data out in full.
Practice: your first week with Search Console
Five steps on your own project. If the service is already connected, start at step three:
- Add a Domain property and wait for data — the first few days the reports will be empty.
- Submit a sitemap and check a day later how many URLs were discovered.
- Open the performance report over 28 days and write down the five pages with the most impressions. That is your real entrance from search — often not the one you thought was the main page.
- For each, look at position and CTR. Good position, low CTR — open the query in the results and see what sits above you.
- Go into page indexing and write down the exclusion reasons for pages that should have been indexed. Wins and losses and top pages compare periods for you.
The help for each report: performance, impressions and positions, page indexing, sitemaps, URL Inspection.
How to tell you are using the service, not just opening it
The sign is that a report became the start of the work rather than its conclusion. People used to open Search Console to see "how things are going". Now you open it with a question and leave with a list of pages to fix.
Three questions to check yourself. Do you know your five pages with the most impressions — from the report, not from memory of what you promoted? Can you explain why a specific important page is not indexed? Would you notice a drop in impressions on the fourth day rather than a month later?
What not to expect: complete data. Some queries are not shown in the reports, and some interactions with the results are not counted as clicks. Search Console is the best source available, not the full picture, and decisions are made with that caveat.
What comes next
The next lesson is SEO platforms and tools: what third-party services can do, and where the line runs between data and estimates. The previous lesson, on E-E-A-T, is here.