How to Read Clicks and Impressions in Search Console

For search engine optimization (SEO), Google Search Console’s Performance report shows how often your site appeared in Google Search and how often people clicked through to it. An impression is a recorded appearance in Google Search, counted under rules that vary by result type; a click is a recorded click on a link to your site. These numbers help you assess search visibility and visits, but they do not show whether someone noticed a result or what they did after arriving.

Read clicks and impressions together, then check the affected pages and queries before deciding what changed. Click-through rate (CTR) connects the two: clicks divided by impressions. Search Console measures search activity; analytics tools measure behavior on your site, so their totals will not necessarily match.

What Google counts as a click or impression

For an ordinary search result, Google can count an impression when the result appears on the current results page, even if the person does not scroll far enough to see it. Some result formats have different rules: an item in a carousel or expandable section, for example, may need to be brought into view or expanded. An impression is therefore a recorded opportunity for exposure, not proof that a person read the result. Google describes these rules in its guidance on clicks, impressions, and position.

A click records a person following a link from a Google result to your site. It does not equal an analytics session, which is a measure of activity on your site. Consent settings, tracking tags, attribution, and other analytics settings affect what those tools record. When comparing Search Console with analytics, look for similar trends rather than expecting identical totals, as Google’s comparison guidance recommends.

CTR is calculated as:

CTR = clicks ÷ impressions

CTR is useful when you read it alongside the query, page, device, result format, and comparison period.

Check the report before reading a change

In the Search Console Performance report, first confirm the date range, search type, and filters. The report can separate Web, Image, Video, and News search, so a chart with a different search type or filter does not describe the same scope. Recent data can also be preliminary. For comparisons, use equivalent periods and check that the dates are complete. The Performance report overview describes its available controls and groupings.

Use the chart to spot when clicks or impressions moved, then use the table to find where the change occurred. Check pages, queries, devices, and countries. If a query stands out, select it and inspect the Pages view to see which pages appeared for it. This shows whether the change is limited to one query or page or affects a broader set.

A chart total and the sum of visible table rows may not match. The chart groups data at the property level (the site or part of a site tracked in Search Console), while table dimensions such as pages group data by different criteria. Google also omits some query data for privacy and limits the rows shown. Treat the table as useful detail, not a complete inventory of every search or URL. The report’s data-grouping guidance explains these limits.

Interpret the pattern, then investigate

If impressions rise faster than clicks, Google recorded more exposure without a matching increase in visits. Find the queries and pages behind the added impressions, then compare CTR, device mix, and result appearance. A high-impression, low-CTR query is a reason to inspect the result and its match to the search, not proof that the title or description caused the pattern. Google also identifies such queries as opportunities to investigate in its common report tasks.

If clicks and impressions both fall, first identify the dates and the pages or queries affected. Check whether the report scope changed, whether the period normally has different demand, and whether Google documented a data issue for those dates. A decline alone does not establish that rankings fell.

If clicks rise while impressions stay level or decline, CTR may have improved. The mix may also have shifted across queries and pages, across devices, or among result types. Segment the report before attributing the change to an edit. Average position can add context, but it is an average based on impressions, not a fixed rank that every searcher sees. Search results vary, so use position as a trend alongside clicks and impressions rather than as a precise description of an individual search.

Know why reported numbers may not line up

Search Console assigns performance data to Google’s chosen canonical URL, the URL Google treats as the main version of a page. Page-level totals can therefore appear under a different URL than the one you expected. If that happens, check which canonical Google selected before treating the discrepancy as missing traffic.

Search Console data also has a reporting delay. Google says data normally appears within two to three days, and a new property can take up to a week to show data. Standard report dates use Pacific Time, while the 24-hour view uses the browser’s local time zone. Check the data freshness and time-zone guidance before drawing conclusions from the newest dates or comparing daily totals.

Google’s data anomaly log records reporting issues that affect particular dates and metrics. For example, Google documented an impression-reporting issue from May 13, 2025, through April 27, 2026, followed by a correction that could cause a drop in reported impressions. When a chart changes sharply, check whether an anomaly overlaps the period before interpreting the movement as a change in site performance.

What Search Console shows about AI search

Google says clicks on links in AI Overviews and AI Mode count in the regular Search Performance report. Its dedicated generative AI report shows impressions for those features. You can view results by page and country; the report also provides device and date views. That report does not provide a separate AI click count or CTR, so it cannot show how many visits those impressions generated. See Google’s generative AI performance report details.

Use the AI report to assess recorded impressions, and use the regular Performance report to assess reported clicks. The available reports do not connect an AI impression to a separately attributed click, visit, or conversion. Treat AI visibility and site outcomes as different measurements.

Key Takeaways

• Read both metrics together: Impressions show recorded exposure under Google’s rules; clicks show link clicks from results. CTR is clicks divided by impressions.
• Check scope before comparing: Confirm dates, search type, and filters, then use the chart to spot movement and table dimensions to locate it.
• Investigate patterns before assigning causes: Segment by page, query, device, or result appearance; a CTR change alone does not identify what caused it.
• Expect reporting limits: Privacy filtering, row limits, canonical URL assignment, reporting delays, and known anomalies can affect the numbers you see.
• Separate AI visibility from traffic: The dedicated AI report shows impressions, while the regular report includes clicks from AI-feature links without separately isolating them.

What I'm building

Delegate tasks. Get software.

Give Vroni a GitHub issue, bug report, spec, or rough idea. It reads the repo, plans the change, writes code, runs checks, and works toward a review-ready pull request.

Take a look at vroni.com