All writing

Google's "preferred source" button, and what it's really for

, 2 min read

Adaptation to AI-first search is moving fast.

On August 20, Google rolled out an embeddable “Add as a preferred source” button. Quick context: Preferred Sources is a Google Search feature that lets people choose which sites they want to see more of in Top Stories, Discover, News, and now in AI Overviews and AI Mode. Give people a button for that, and suddenly it’s a lot easier to influence.

Three ways to add it

  1. Standard JS widget: two lines of code, and the button renders itself.
  2. Advanced integration: a callback queue for custom UI and timing.
  3. No-JS deep link.

It only works at the domain or subdomain level (example.com, blog.example.com), not on subfolders like example.com/en.

Anyone can add the button, but whether your site actually shows up as a selectable option is entirely Google’s call. No application, no verification, no published criteria.

Sounds like a black box, until you realize testing is trivial: open the preferred sources page and enter your domain. If it appears, it’s already eligible. I checked a batch of expired domains, and some were already listed as sources. Even our test domain affbulk.online showed up.

What’s really behind this?

There are plenty of reasons: calming publishers who are upset about AI Overviews eating their traffic, giving them “control”. But I think this is the first step toward explicit first-party trust signals, straight from users rather than inferred from behavior or backlink graphs.

That’s a cheaper, more reliable signal for training ranking models and choosing sources for AI Overviews and AI Mode. Users are essentially labeling for Google, for free, which sites are real and trustworthy.

Google’s documentation has cited this feature as a signal for the Discover core update since February 2026. “Explicit user preference” is quietly becoming a full ranking component. We’ll see how well it holds up against spam and AI content farms.

In AffBulk we shipped the button as a standard component, with a toggle to turn it on across a whole site portfolio. Next we’ll track deep-link clicks and branded traffic growth per site.

Are you testing this? I’d like to hear your results.