Long-Tail Still Clicks: Plan by Query Shape

The click loss from AI Overviews is not distributed evenly across your keyword set, and treating it as one sitewide number is how teams cut pages that were still earning. Ahrefs' April 2025 study of 300,000 keywords found that the presence of an AI Overview correlated with a 34.5% lower average clickthrough rate for the top-ranking page on informational keywords, and a December 2025 re-run of the same study put it at 58%. That is a precise finding about one query shape, and it is getting worse. Queries carrying a buyer's constraints, a budget ceiling, an audience, a named competitor, are a different population, and no public study tells you what happened to yours.

The short version: the working hypothesis is that an AI Overview resolves a broad question more readily than a narrow one loaded with conditions. No public study measures where the surviving clicks land, which is why the instruction is to group your own queries and measure the split, not assume it. Plan around query shape, not keyword volume: group your queries by how many constraints they carry, measure clickthrough inside each group, and move effort toward the groups that still send a person to a page.

The commercial case is stronger than the traffic case. G2's research found AI chatbots are now the single largest influence on B2B shortlists, 51% of software buyers now begin research inside an AI chatbot, and Gartner predicted in February 2024 that traditional search volume would fall 25% by 2026. The constrained queries are where the remaining clicks and the actual buying decisions overlap.

Which of your queries are most exposed?

The queries most exposed are the ones a single paragraph can finish. A definitional question has one settled answer many pages already agree on, which is the easiest case for a summary to assemble and for a reader to accept without clicking. Add a constraint and the summary has to be right about a budget, a team size, or an existing stack, and a wrong constraint is obvious to whoever typed it.

Read the Ahrefs figures as a description of that easy case: informational keywords, the top-ranking page, and a correlation rather than a causal estimate for any one site. Applying 58% to a keyword set full of comparison and specification queries imports a condition the study never tested.

Ranking and citation also come apart on this surface, which changes what an exposed query costs you. Ahrefs found that 38% of AI Overview citations rank in the organic top 10, across 4 million overview URLs from 863,000 result pages in March 2026, down from roughly 76% in July 2025. The overview increasingly reaches past the page it is summarising, which describes a surface that selects passages, not pages: a Google ranking and an AI citation are different outcomes.

Why does a narrow query resist a one-paragraph answer?

Because every added constraint is a condition the answer has to satisfy at the same time, and retrieval degrades as conditions stack. A 2026 study of 1,000 multi-condition queries found that even its strongest configuration located a document satisfying every condition for 81.1% of queries while still placing partial matches ahead of complete ones. That was long-document retrieval, not the public web, so read it as a mechanism and not a measurement of Google.

The same pressure shows up in how evidence gets indexed. An experiment across three retrieval pipelines and six datasets found question-matched indexing reached 71.5% average claim recall against 53.6% for naive retrieval, with average context precision of 63.5% against a 42.3% baseline. The same work found noise sensitivity got worse, and it tested neither public websites nor AI citations. Matching a real question's shape helps retrieval, which is a smaller claim than deciding what an engine publishes.

Buyers also add constraints gradually, which makes the narrow question the real one. A 2026 analysis of 8,133 multi-turn human-LLM conversations covered 670 English commercial multi-turn conversations alongside a separate set of 7,463 PRISM conversations from 1,389 participants. It found that a request dimension stated earlier remained only in the conversation history for 50.3% of the commercial conversations and 44.8% of the PRISM ones. It tracked where stated pieces of a request appeared across turns, and measured neither citations nor purchases.

Do narrow buyer questions matter more commercially?

Yes, and the reason has little to do with search. A constraint-heavy question states a buyer's segment, budget, and alternatives in one line, which is late-stage information you normally pay a form to collect.

The shortlist arithmetic makes those questions expensive to lose. 6sense found buyers already have prior experience with 3.8 of the roughly 5 vendors they evaluate. Read literally, that leaves roughly one vendor a buyer meets for the first time during the evaluation, an inference from the familiarity figure and not a measured shortlist slot. The constrained comparison query is where a stranger competes for that position.

AI research is what makes that position reachable. One-third of buyers reported purchasing from a vendor they had never heard of before an AI introduced them, and 58% of buyers say AI research led them to engage sellers sooner. Profound's 7.5 million-conversation sample saw the commercial share of that sample rise across a year, which is a share of a proprietary corpus, not a count of buyers.

How should this change what you write?

Write to the constrained question in the buyer's own words, and stop rewriting broad pages to sound quotable. C-SEO Bench (NeurIPS 2025) tested conversational-SEO rewrite methods across two tasks and six domains and found only 3 of 54 unilateral conditions produced statistically significant citation-rank gains. Most phrasing tactics circulating as GEO advice did not survive testing.

What did survive is evidence. The GEO study (Aggarwal et al., KDD 2024) found that adding statistics, quotations, and citations lifted citation visibility in its benchmark, while keyword stuffing did nothing in the same error-bar table. Persuasion language can cost you outright: scarcity and exclusivity framing measurably reduced how often a model recommended a product across 10 fictitious products.

In practice that means one page per constraint set, not one per head term, with the constraint in the heading and answered in the first two sentences. Put the price band, the integration name, the capacity limit, and the honest exclusion into liftable text. A cluster of narrow pages is easier to justify on those two results than one wide page is: what moved citation was the presence of concrete statistics and named sources, and a page written for a single buyer situation can carry those at full strength without spreading them thin across several situations at once.

Then confirm the page is readable at all. Vercel's crawler research with MERJ documented that GPTBot and its peers read raw HTML without running JavaScript, so a specification table injected client-side is an empty shell. The sequencing for an existing search program is covered separately in adding GEO to an SEO program.

Why does a sitewide traffic average hide the split?

Because the average mixes two populations moving in opposite directions. If broad-query clicks fall while constrained-query clicks hold, one organic line drops and tells you nothing about which pages to keep. The decision you need is per query shape; the reporting default is per property.

Analytics makes that harder. GA4 keeps AI Overviews and AI Mode inside Organic Search and names only 5 assistant examples for its separate assistant channel, so overview-influenced sessions sit beside ordinary organic ones. Segment by query group in Search Console first, then check what those sessions did, remembering that GA4 computes engagement rate as sessions with a key event divided by total sessions, which counts a visit and not a decision.

A loss's composition matters more than its size. 6sense's read on B2B sites losing traffic to LLM interfaces is that the visitors going missing are likely the professionally curious and future buyers, while in-market buyers still interact with vendors at the same rate. A decline made of the first group is a different business event from one made of the second, and the sitewide number cannot tell them apart.

Sampling answers carries its own discipline. SparkToro and Gumshoe.ai found AI recommendation lists are highly inconsistent when the same prompt is asked again, a result Search Engine Land summarised as lists that rarely repeat. A 2026 variance-components study reached the same place from the measurement side, reporting that a single answer is an unreliable estimate of where a brand ranks. Size your panel before you draw a trend from it.

How does Trovance track the split by query shape?

Trovance makes the buyer question the unit of record instead of the keyword. You define the market questions your buyers ask, at the specificity they ask them, and Trovance runs those tracked questions repeatedly across engines. Every answer run is preserved as a snapshot with its context intact: who was mentioned, who was cited, who was recommended, and which sources carried the answer.

Because each question is stored with its constraints, the record keeps the two populations in this article apart. A broad category question and a constrained comparison question are separate tracked questions with their own answer coverage over time, so you can observe the broad one resolving inside the answer while the narrow one still routes a reader to a page. That is the split a sitewide traffic average erases.

The output is meant to be worked. Your Brand Core holds the claims you are entitled to make and the proof behind each, and recommended actions name what the record shows is missing and why. A missing page in the record is a candidate for a brief, not a brief on its own: a person decides whether the gap is worth closing before anything is drafted. Drafts are produced from approved claims, a person reviews and approves before anything publishes, and the next analysis cycle reruns the same questions so you can compare new answers against the preserved ones.

What Trovance will not promise is a citation, a ranking, or a recommendation on any query. The engines are probabilistic, the published record says most rewrite tactics do not move citation rank, and one answer is a sample rather than a verdict. Trovance is building toward a tighter join between query shape and observed click behavior; today it observes and preserves answers, and click data still comes from your own analytics.

What should you do this week?

Start by grouping, because everything downstream depends on it. Export your Search Console queries, tag each by how many constraints it carries, and compute clickthrough per group, not per property.

Then act on the shape of the loss. For groups still clicking, write or sharpen one page per constraint set, with the answer in the first two sentences and the evidence in text a model can lift. For groups that have gone quiet, measure them as answers and not as traffic: run each question ten or more times and record whether you were mentioned, cited, or recommended, remembering that a repeated single-turn prompt is a lossy stand-in for a buyer who adds constraints across several turns.

Be honest about the timeline. How fast either a rendering fix or an evidence change reaches an answer depends on re-crawl cadence, and nobody has published a reliable number for that. The variance described above means no single reading settles anything. Anyone selling a guaranteed AI Overview placement is selling against the published record.

If you want that question-level view without building the harness, start a free Trovance analysis with the ten buyer questions your narrow pages are supposed to answer.

Where the click actually went

• How to get featured in Google AI Overviews - what is controllable on the surface that took the click.

• What gets cited by AI - which page traits keep showing up inside answers.

• Do AI search visitors convert? - what a surviving click is worth after it lands.

• Can likely buyer questions improve AI retrieval? - whether writing to buyer phrasing helps retrieval.

Plan and measure by query shape

• GEO vs AEO vs SEO - which program owns which part of this problem.

• GA4 AI traffic attribution - pulling assistant sessions out of the organic average.

• A visibility gap is not a content brief - deciding which missing page is worth writing.

• How to build a competitor comparison page - the narrowest query shape and the page that answers it.

FAQs