Google's new button fights AI traffic loss, not the data to prove it works
A one-click embed lets readers boost a site in Google's Search, AI Overviews, and AI Mode results. Publishers still can't measure whether it recovers any traffic.
Google's new button promises publishers more AI Overviews traffic. It won't show them if it's working.
Google shipped a new "Preferred Sources" button for publishers on August 20, 2026, pitched as a way to claw back traffic that AI Overviews and AI Mode have been diverting from their sites. The button ships with one glaring gap: no analytics telling a publisher whether a single click ever turns into a recovered reader. Digiday asked publishers about that gap directly, and the on-record answer is blunter than anything in Google's own announcement.
What the button actually does
The mechanics are simple. A publisher embeds Google-supplied button code on their own site, the same place they'd put existing social-follow buttons, per Google's developer docs. A reader who clicks it marks that outlet as a preferred source, and Google says preferred sources get surfaced more often in Search's Top Stories, in AI Overviews, and in AI Mode, specifically for that reader going forward.
This extends, rather than invents, the idea. Google first built Preferred Sources directly into AI Mode and AI Overviews back in May 2026. Mrinalini Loew, general manager of Google's Search Ecosystem team, posted the August 20 update, which moves the same mechanic onto the publisher's own site and bundles it with two related changes: a natural-language way to shape the Discover feed, and customizable audio news briefings on Android.
The numbers Google is sharing
- More than 600,000 unique sources have been selected as preferred sources so far, up from the 345,000 Google cited when it launched the feature in May.
- Google says a preferred source gets clicked roughly twice as often as a non-preferred result in the same slot.
- The rollout is global and live in 16 languages, spanning Search, Discover, and the Google News Android app.
The number Google won't show you
None of that tells a publisher what they actually want to know: does a click on this button put a dent in the referral traffic AI Overviews and AI Mode are taking? Digiday put that question to publishers directly and found Google supplies no dashboard, no report, and no metric that isolates the button's effect. A publisher can watch their overall traffic move and never know whether Preferred Sources had anything to do with it.
When Google doesn't make it easy to track something, it's probably because it's not necessarily a positive for publishers.
Why a build studio cares
Our Full Audit tier includes SEO and AEO work for exactly this reason. Search visibility is no longer one channel: it is Search, AI Overviews, AI Mode, and Discover, each ranking a site by different rules, and each willing to disclose only as much as keeps publishers participating. Preferred Sources is a real lever: a link on a client's own site can change where they show up inside someone else's AI answer. But it is a lever the client cannot see the other end of.
When we run an AEO pass for a client, the deliverable is built from what we can independently verify: referral logs, branded search volume, direct traffic before and after a change. Google's own click multiplier for preferred sources is a fact about Google's aggregate data, not proof about any one client's traffic. Our advice is to adopt Preferred Sources since it costs a client nothing to embed, and to keep measuring their own numbers instead of trusting the platform's.
Next step: read Google's own announcement and TechCrunch's coverage of the rollout, then weigh both against Digiday's reporting that no analytics ship with the button. If AI Overviews traffic loss is already showing up in your numbers and you want an independent read on what is actually measurable, write to us at hello@gattyworks.com.