Google Preferred Sources: What It Is, and Who It Actually Helps

Google has quietly shipped a feature that inverts a rule the search industry has lived under for twenty-five years. For most of that time, which sites you saw was Google's decision. Preferred Sources hands part of that decision to the reader.

The mechanic is simple. A reader marks your site as a preferred source. From then on, Google gives your content priority in their Top Stories, tags it with a "preferred" badge, and can highlight it in AI Mode and AI Overviews. It works at the domain and subdomain level — example.com or blog.example.com — but not at the subdirectory level, so you cannot register just example.com/insights. It is live globally, in every language Google Search operates in.

That is genuinely interesting. It is also, for most businesses reading this, worth far less than the headlines suggest. Both things are true, and the gap between them is the useful part.

How to add the button

Google documents three ways to promote it, and the choice matters more than it looks.

The default is a JavaScript button. You load Google's publisher script and drop in a container element, and Google renders its own officially-styled button:

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

It accepts a data-theme="dark" attribute and a data-lang override for localization. There is also an advanced JavaScript path, using ES module imports or a callback queue, if you want to drive a custom interface programmatically.

The third option is a plain deeplink, and it is the one we would recommend for most sites:

https://www.google.com/preferences/source?q=example.com

That is just a URL. It works in a text link, a button you style yourself, an image, a newsletter, or a social post — anywhere you cannot run Google's script, which includes most email clients.

We chose the deeplink for this site, and the reasoning generalizes. publisher.js is a third-party Google script. This site loads Google scripts only after a visitor accepts cookies, which leaves two bad options: load it unconditionally and contradict your own consent policy, or gate it and hide the button from everyone who has not accepted. The deeplink sidesteps the dilemma entirely. It costs no JavaScript, makes no third-party request, and cannot shift your layout while it loads. What you give up is Google's automatic localization and its official button styling — a fair trade if your site already has a design language of its own.

Who this actually helps

Here is the part the launch coverage skipped.

Preferred Sources was built for news publishers. The primary payoff is Top Stories placement, and Top Stories is a news surface — it draws from content that qualifies as news, published at news cadence. If you run a B2B services site, an e-commerce store, or a company blog that posts twice a month, you are not appearing in Top Stories with a preferred badge, because you were never appearing in Top Stories at all. That half of the feature is worth precisely nothing to you.

The AI Mode and AI Overviews half is more plausible, and it is still narrower than it sounds. Being highlighted there requires a reader to have already marked you as preferred. That makes this an amplifier for an audience you have, not a channel that builds one. Nobody discovers you through Preferred Sources. It only changes what happens after someone already decided they trust you enough to go and click a button in their Google settings — which, realistically, is a small fraction of even a loyal readership.

So the honest summary: if you are a publisher with a returning audience, this is a real retention lever and you should promote it properly. If you are most other businesses, it is a low-cost, low-return addition, and any agency pitching it to you as a growth strategy is selling you something.

Then why did we add it?

Three reasons, none of them traffic.

It costs almost nothing. One link, no script, no dependency, no maintenance.

It is honest signal. A quiet ask at the end of a post is a reasonable thing to put in front of someone who just read a thousand words of yours. Readers who want it can take it. Nobody else is interrupted, which is why ours is a single line of text rather than another button competing with the real call to action.

And we would rather run a new surface on our own site before we discuss it with a client. That has been the standing rule here for structured data and answer engine optimization generally, and it applies the same way to this.

What to do instead, if AI visibility is the goal

If the reason Preferred Sources caught your attention is that you want to show up in AI answers, that is a legitimate goal — it is just a different piece of work. The things that actually move it are unglamorous: accurate structured data, content that answers a question directly in the first paragraph, a consistent entity across the web, and a footprint on the third-party sources these systems read.

We have written that up properly elsewhere — how to get your business recommended by ChatGPT and Google AI Overviews covers the playbook, and what an AI visibility audit covers covers how to find out where you currently stand. If your foundations are the problem, SEO in 2026 is the more useful starting point.

Add the Preferred Sources link. It takes five minutes and it is the right thing to offer readers who want it. Just do not mistake it for the work.