Google Preferred Sources: Add the Button, Measure It

Google will now let you ask for the follow

Since April 2026, anyone searching Google in any language can mark a site as a preferred source. And since August 20, the button you put on your own site to prompt that choice got better: a reader clicks it, picks you in an overlay, and stays on your page. No round trip to Google's settings. Google says readers are "twice as likely to click through to a site after marking it as a Preferred Source," and over 200,000 sources had been selected by the end of April.

The install is really two lines. That part of the story is true and everyone has written it. What nobody has written is how to tell whether the button earns its spot on your page, and that's the part a tracking company should probably handle. So here's both.

What it actually does (less than the hype, more than nothing)

Read Google's publisher doc instead of the coverage and the feature gets specific fast. Three surfaces, with different promises:

• Top Stories. Your content is "more likely to appear," with a "preferred" badge. This is the real inclusion effect.
• AI Mode and AI Overviews. Your content "can be highlighted with a 'preferred' badge" for the users who picked you. A badge. Google doesn't promise increased inclusion here.
• Google Discover. Not on the list. The claim that preferred sources boosts Discover is all over LinkedIn and it traces to trade press, not to Google. Google announced a separate Discover feed-refinement feature on the same day as the button update, which is probably where the confusion started.

One more correction while we're here. Search Engine Journal ran the headline "Google's Preferred Sources Is Now A Global SEO Signal" back in May. Global refers to geography, since the feature rolled out from US and India in August 2025 to every language by April 2026. It is not a ranking signal. Google's own line is that selections work alongside its ranking systems and don't override relevance. This is per-user personalization: the people who pick you see more of you. Nobody else's results change.

Honestly, that's still worth having. Your newsletter subscribers and repeat readers are exactly the people who'd click the button, and they're the ones whose Top Stories you want to live in.

The ten-minute install

Google gives you three methods. The standard button is this:

<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>
<div google-add-preferred-source-btn></div>

Script in the head, div wherever the button should render. It auto-localizes, and takes data-theme="dark" and data-lang attributes if you need them.

No JS at all? There's a deeplink: https://www.google.com/preferences/source?q=yourdomain.com. It works as a plain link anywhere Google's script can't run, which makes it the version you put in newsletters and social bios.

Two eligibility catches from the doc. Only domains and subdomains qualify, so blog.example.com can be a preferred source but example.com/blog can't be one on its own. And Google's help page warns that "sources that aren't updated regularly may not be available." Check yours by searching for it in the source preferences tool before you ship anything.

The part nobody measures

Here's where every guide stops: button installed, done. But you now have a UI element on your page whose entire payoff happens inside Google's results, where you can't see it. Selections don't show up in Search Console. The downstream lift, if it comes, lands as plain google / organic sessions you can't tell apart from everything else. We wrote about this same visibility hole with AI assistant traffic, and Google's surfaces are worse, not better.

So instrument the two things you can see.

Clicks on the button. Google's advanced integration exposes preferredSource.addPreferredSource(), which you call from your own click handler. Fire an analytics event in the same handler. Now placement A vs placement B is a question with an answer.

Deeplink placements, tagged. The deeplink is just a URL, and URLs can be tagged. Put a tracked short link on the newsletter version, another on the social-bio version, a third in the footer. Which placement actually produces clicks toward the preferences tool stops being a guess. (This is ordinary campaign tagging discipline applied to a link Google happens to own.)

That's the whole system. Two events, a few tagged links, and a note in your calendar to compare Top Stories impressions in Search Console eight weeks out. Cheap.

Most sites will sleep on this

The button costs nothing, carries no ranking risk, and speaks straight to the loyal slice of your audience. We're wiring it into attri.io's blog and footer this week, with the click event attached, and we'll report what the numbers say.

If you add it, add the measurement in the same commit. A button you can't measure isn't a growth lever. It's furniture.