Zero-click search and your Search Console data
A zero-click search ends on the results page: the searcher gets an answer, or changes the query, without visiting a website. This page explains what that does to the numbers in Google Search Console, how to read a CTR change without guessing its cause, and what Click Decay's research will and will not be able to show.
What counts as a zero-click search
Any Google search after which the searcher does not click through to a website. The answer may come from an AI Overview, a featured snippet, a knowledge panel, a local pack, a "People also ask" box or a calculator built into the results. The searcher may also refine the query, or simply leave. This page is about search behaviour only, not about "zero-click" security exploits.
Zero-click searches are not new. Answer boxes and knowledge panels resolved simple queries long before AI Overviews. What changed is how many kinds of queries the results page can now answer on its own.
How zero-click searches show up in Search Console
Search Console counts an impression when a link to your site is shown in Google's results, and a click when someone follows it. A search that is answered on the results page can still give your page an impression, without a click. More zero-click searches therefore tend to show up as impressions that hold or grow while clicks and CTR fall.
The same pattern has other causes, and Search Console totals cannot tell them apart:
- Your pages start appearing for new, broader queries, often on lower positions, which add impressions with few clicks.
- Rankings move for some queries and not others, while the average position barely changes.
- Demand shifts with the season, the news or the market.
- Google changes how it counts. Search Console reported an impressions logging issue from 13 May 2025 to 27 April 2026, listed on Google's data anomalies page.
How to read a CTR change without blaming one cause
Start with arithmetic, then look for evidence:
- Split the click change. The CTR calculator divides a click change into a part from impressions and a part from CTR. If most of it comes from impressions, the question is visibility and demand, not CTR.
- Compare like with like. Use periods of the same length, the same search type and the same filters, and avoid dates with a known reporting issue.
- Narrow the scope. A site-wide CTR mixes branded and non-branded queries, informational and commercial ones, and every position. A change that shows up in one group and not in another says more than the site total.
- Check the results page itself. Search for the queries that changed most and note what appears above the organic results. This is the only direct evidence of an AI Overview or another feature, and it is a sample, not a record.
None of these steps proves why clicks changed. Together they show which explanations fit your data and which do not, and that is usually enough to decide what to work on next.
How to read a CTR curve
A CTR curve plots click-through rate against position: what share of impressions turns into clicks at position 1, 2, 3 and further down. On a plain list of results the curve drops steeply over the first few positions and then flattens into a long tail.
When you read one, keep four things in mind:
- It needs query-level data. Each point comes from queries that held that position. A site's average position is weighted across all its queries, so a daily site total cannot draw a curve.
- Position counts result blocks, not screen space. Ads take no position, so position 1 can sit below several ads. An AI Overview takes one position of its own: a link to your page inside it gets the overview's position, and the first ordinary result below it is reported at position 2. The same position number can mean very different places on the screen.
- The mix matters. Branded queries produce steep, high curves because the searcher already wants your site. Informational queries that the results page can answer produce flatter, lower ones. A curve over both shows neither.
- Volume matters too. 50,000 impressions at 2% CTR are 1,000 clicks; 500 impressions at 15% are 75. A low CTR on a large query can still be worth more than a high CTR on a small one.
A flat curve with a low CTR even at the top is the shape zero-click searches leave. For such queries, being shown and being cited can matter more than being clicked, and impressions are the better measure of visibility.
What a daily Chart.csv export can show, and what it cannot
The Chart.csv file in a Search Console export holds one row per day for the whole property: date, clicks, impressions, CTR and average position. That is enough to:
- compare two periods of the same length;
- split a click change into impressions and CTR;
- see trends and the dates where they turn;
- see how a known reporting issue lines up with a change.
It is not enough to:
- draw a CTR curve by position, because the daily average position mixes every query;
- tell which impressions had an AI Overview or another feature on the page;
- attribute a click change to AI features, rankings or seasonality.
Search Console's Generative AI report shows impressions only, without clicks, so it cannot measure CTR either. Click Decay does not analyse it for clicks.
How to export your data from Search Console
- Open the Performance report for Search results.
- Keep the search type on Web and remove any query, page, country, device or search appearance filter.
- Choose a date range that covers both periods you want to compare. To compare impressions and CTR, neither period may touch 13 May 2025 to 27 April 2026.
- Use Export and download the CSV files. Search Console saves them as one ZIP file.
The ZIP holds one file per tab of the report:
| File | What it holds |
|---|---|
| Chart.csv | Daily clicks, impressions, CTR and average position for the whole property |
| Queries.csv | The top queries only, up to 1,000 rows, so they do not add up to the totals |
| Pages.csv | Top pages; Search Console counts pages differently from the property |
| Countries.csv, Devices.csv, Search appearance.csv | Breakdowns of the same period |
| Filters.csv | The search type and filters the export was made with |
Keep the ZIP as it is. Click Decay's Search Console analysis reads it in your browser and uses Chart.csv for every total.
The Zero-Click Report: research in preparation
Click Decay is preparing a study of how clicks, impressions and CTR change over time in Search Console data. It will be built from data that users choose to share: the Search Console analysis is free, and in return the user shares the daily metrics shown to them before they press Share. Research collection is not open yet.
What is shared, and what is not:
- Shared: daily clicks, impressions and average position for the two periods compared, and how the export was read.
- Never shared: the ZIP file, search queries, page URLs, the site address, file names, e-mail addresses or company names.
Because the shared data is daily site totals, the first reports will cover what that data supports: period comparisons, the impressions and CTR parts of click changes, trends over time, and the effect of known reporting issues. CTR curves by position need query-level data from a separate, verified panel, and will come later if at all.
Every published result will state:
- how many submissions and how many likely distinct sources it is based on;
- that submitted data is not verified;
- the date range it covers;
- that it does not show CTR by position, and does not attribute clicks to AI features.
Results will be published in aggregate only. They will describe the submissions received, not every industry or country. Submissions carry no site identity, so one site may be counted more than once; counts of verified sites need a separate, verified panel.
Frequently asked questions
Is zero-click search the same as AI Overviews?
No. AI Overviews are one way a search can end without a click. Featured snippets, knowledge panels, local packs and built-in answers did the same before them, and many searches end with a new query instead.
Does a falling CTR prove that AI Overviews took my clicks?
No. A falling CTR fits AI Overviews, but it also fits new low-position impressions, ranking changes, seasonal demand and reporting changes. Split the change into impressions and CTR first, then check the results pages for the queries that moved.
Can Search Console show which impressions had an AI Overview?
Not in the Performance totals. The Generative AI report shows impressions without clicks, so it cannot give a CTR. Checking the results page by hand is the only direct evidence, and it is a sample.
Should I stop writing informational content?
Not because of a site-wide CTR. Some informational queries rarely brought clicks even before AI answers, and others still do. Look at the queries one by one: where clicks hold, depth pays; where even the top position earns few clicks, measure visibility rather than visits.
How do I check my own site?
Enter the totals of two periods into the CTR calculator. It shows how much of the click change came from impressions and how much from CTR, with each number labelled as observed, calculated or modelled.