Your impressions chart looks roughly the same as last year. Your clicks chart does not, and nobody in the room can explain the gap with the numbers on the screen. That mismatch is the practical shape of the zero-click problem, and it is worth understanding before you decide whether it deserves any of next quarter's budget.
This post is about what actually changes when a buyer gets a usable answer without visiting anything, and what still gets you visited. It deliberately does not contain a headline percentage. There are several in circulation, they come from different measurement bases, and most of them do not survive a question about how they were collected.
What zero-click means on an assistant surface
"Zero-click" started as a description of search result pages that resolved a query in place: a weather box, a currency conversion, a definition snippet. The user got what they came for and the result page was the destination.
Assistant surfaces extend that idea in a way that matters for brands. A model can assemble an answer from several sources, summarise them, compare them, and present a shortlist, all inside one response. Some assistants attach citations to that response, some do so inconsistently, and the presence of a citation does not mean anyone opened it. So there are really three outcomes stacked inside the phrase:
| Outcome | What the buyer got | What you can see in analytics |
|---|---|---|
| Answer resolved in place, no source named | A usable answer | Nothing |
| Answer resolved in place, your brand named, no link followed | An impression of your brand | Nothing, unless they later search your name |
| Answer resolved in place, link followed | A visit | A session, possibly with a referrer you can identify |
Only the third row shows up as traffic. The second row is where most of the argument sits, because it has real commercial value and no session attached to it. For the mechanics of catching the third row when it does happen, see how to detect AI referral traffic in GA4.
Which query types genuinely resolve without a visit
Not everything is at risk equally. The useful split is between informational resolution and commercial shortlisting.
Informational resolution is when the buyer's question has a correct, compact answer. What does a term mean. How is a metric calculated. What is the difference between two file formats. Does this integration exist. These were already low-value traffic for most businesses, and they are the queries most likely to be answered fully in the response. If your organic traffic was heavily weighted toward this kind of question, the decline you are seeing is probably concentrated there.
Commercial shortlisting is different. When someone asks an assistant for the best option in a category for their situation, the model usually produces a short list of named candidates with a sentence or two each. That answer is rarely sufficient to buy from. The buyer still needs pricing that fits their seat count, confirmation that the integration they depend on exists, a sense of whether the company will be around next year, and usually a demo or a trial.
The shortlist is not the end of the process. It is the new front of it. Being on it is the thing that changed; the click that follows is now downstream of an editorial decision you did not make.
Which ones still send people to you
Some patterns still produce visits, and it helps to be specific rather than hopeful about them:
-
Verification. A buyer who has been given three names will frequently check at least one of them directly. Assistants are known to state details that are out of date, and buyers who have been burned once develop the habit.
-
Anything requiring your account, your data, or your configuration. Pricing calculators, availability lookups, compatibility checkers, login-gated documentation.
-
Anything with a decision the buyer will not delegate. Contracts, security review, procurement paperwork, anything with a signature at the end.
-
Deep technical detail. A summary of your API is not a substitute for your API reference when someone is actually writing against it.
-
Branded intent. Once your name is in the buyer's head, a lot of the follow-up is a direct search for your name. This is the mechanism by which an unlinked mention becomes a session days later, and it is also why the session looks like it came from nowhere.
The pattern underneath all five: visits survive where the buyer needs something specific, current, personal, or accountable. They fade where the buyer needed a fact.
What to optimize when the click isn't the goal
If the shortlist forms before the click, the target moves from "capture the visit" to "be the material the answer is built from." In practice that means a few unglamorous things.
Be describable. If an assistant cannot state clearly what category you are in, who you serve, and what you do differently, it cannot place you on a shortlist for that category. This is a content and consistency problem far more often than a technical one.
Be present in the sources that get used. Models assembling a commercial answer tend to draw on third-party material: comparison articles, review platforms, documentation, community discussion, trade press. Your own site is one input among many and it is the one input the model has the most reason to discount, because every vendor's site says the vendor is good.
Be quotable in units. Answers are assembled from fragments, not from whole pages. A page where each section answers one question completely, with the specifics inside that section rather than three scroll-lengths away, gives a retriever something it can lift without distorting it.
Be current. Stale specifications, discontinued plans, and old positioning statements do not just sit there harmlessly. They become the raw material of a wrong description of you.
Nothing here lets you control what a model says. These are inputs to a system that weighs many inputs and changes without notice. Treat them as improving your odds and your accuracy, never as a lever with a predictable output.
How to measure value you can't count in sessions
This is the part that decides whether the reframe survives contact with a leadership meeting. You need at least one number that moves when your position in answers improves and does not require a session to exist.
The most practical one to adopt first is presence rate on a fixed prompt set: the share of runs, across a set of prompts you wrote in advance and do not change, in which your brand appears in the answer at all.
To make that number mean something:
- Write a prompt set that reflects how buyers actually phrase the request, including the ones where you would not expect to appear. A prompt set that only contains questions you win is a mirror, not a measurement.
- Freeze it. The moment you edit the prompt set, your trend line breaks.
- Record the model and version, the run dates, and the number of runs per prompt for every measurement.
- Report a range, not a point. Repeated runs of the same prompt against the same model will not return identical answers, so a single run tells you almost nothing about the underlying rate.
- Track presence separately from citation and from recommendation. Being named in passing and being recommended are different events, and collapsing them into one figure is the fastest way to produce a flattering, useless chart.
Secondary measures worth watching alongside it: direct and branded search volume against the periods when your presence rate moved, assisted conversions where the first touch is unattributed, and self-reported attribution on your own forms. None of these is clean. Together they are more honest than pretending the sessions chart is the whole story.
Two cautions, both important. First, how much of this matters varies enormously by category. A niche B2B product with a long procurement cycle and a consumer impulse purchase are not experiencing the same shift, and treating a figure from one as applicable to the other is a mistake. Second, this page supplies no category-wide effect size. Measure the direction and magnitude from your own analytics rather than borrowing a figure from an unlike audience. The fuller evidence boundary is in the post on whether buyers ask assistants before Google.
In Plain English
What this means: when an assistant answers a question completely, the value of being named inside that answer separates from the value of getting a visit. Informational queries are the ones most likely to resolve without a click. Commercial shortlisting still produces visits, but later in the process and often as a direct search for your name.
Who this helps: anyone who has to explain a clicks-down, impressions-flat chart, and anyone deciding whether "AI visibility" is a real line item or a fashion.
When to use it: when you are setting next period's targets and the traffic number alone will not describe what happened.
What to do next: write a frozen prompt set, measure your presence rate on it with repeated runs, and report it with a range and a run date beside the traffic numbers rather than instead of them. If you want the ground-level version first, start here.
The briefing template shows how to document changes in AI answers with links, dates, and corrections attached.
Primary-source verification
Checked July 28, 2026. The operational and factual guidance above was reviewed against the primary references below. Provider features, prices, policies, interfaces, jurisdictions, and account-specific results can change; recheck the controlling first-party document and your own account or measured data before acting.
- Google Search: AI features and your website - How Google describes eligibility, preview controls, and appearance in its AI search features.
- Google: common crawlers and special-case user agents - Current Googlebot and Google-Extended identities and controls.
- OpenAI: overview of OpenAI crawlers - Current GPTBot, OAI-SearchBot, and ChatGPT-User descriptions and publisher controls.
- Anthropic: web-crawler controls - Current ClaudeBot, Claude-SearchBot, and Claude-User descriptions and controls.
- Perplexity: crawler and user-agent documentation - Current PerplexityBot and Perplexity-User descriptions and controls.
- OWASP: LLM prompt-injection prevention - Threat categories and layered mitigation practices.
- Apache HTTP Server: mod_log_config - Authoritative Apache access-log fields and formats.
- nginx: HTTP log module - Authoritative nginx access-log configuration and variables.
- Google Analytics: traffic-source dimensions - Current GA4 source, medium, campaign, and default-channel definitions.
- FTC: Endorsement Guides Q&A - Current U.S. regulator guidance on endorsements, disclosures, and reviews.
- FTC: Consumer Reviews and Testimonials Rule Q&A - Current U.S. rule guidance on deceptive review practices.