Google's Preferred Sources Button: What It Actually Does for Publishers

Short answer: Google's Preferred Sources button is two lines of HTML a site can embed so a reader can mark it as a preferred source without leaving the page. Once selected, that site turns up more often in Top Stories and carries a "preferred" badge in AI Overviews and AI Mode. It is the first Google lever that converts an audience you already have into search visibility — but it only works for sites already listed in Google's source preferences tool, and Google has never published a baseline for the traffic lift it claims.

Key takeaways

• Readers have selected more than 600,000 unique sources since the feature launched — up from roughly 90,000 in December 2025 and 345,000 in late May 2026.
• The button is not required. Google's own documentation states implementing it is optional for appearing as a preferred source; it is a promotion surface, not an eligibility gate.
• Google says people "click to that site twice as much on average." No baseline, sample, or methodology has ever been disclosed for that figure.
• Preferred status routes through Top Stories, AI Overviews and AI Mode — not, per Search Central, through Discover or Google News.
• The segment losing traffic fastest is the one this helps least: UK consumer and B2B publishers lost 18% of Google referrals in a single quarter versus about 5% for news publishers.

What is Google's Preferred Sources button?

Preferred Sources is a reader-side setting. Someone tells Google "I want more from this publication," and Google weights that publication up in a few specific places. The setting itself shipped in August 2025 to users in the US and India, initially surfacing selected sites more often in Top Stories and in a dedicated "From your sources" block on the results page.

What changed on 20 August 2026 is the plumbing. Instead of asking readers to go find Google's source preferences tool, type your domain and select you, a publisher can now put a button directly in the article. The reader taps it, the selection is saved, and they land back where they were reading.

That distinction matters more than the announcement coverage suggested. The feature was always available; what was missing was a conversion path with acceptable friction. Google effectively shipped a call-to-action widget.

How do you add the Preferred Sources button?

Search Central documents three implementation paths, and the right one depends on how much control your CMS gives you.

The standard path is genuinely two elements:

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

Add data-theme="dark" or data-theme="light" to match your page, and data-lang to override the auto-detected locale. The advanced path exposes preferredSource.init({ theme, lang }) and preferredSource.addPreferredSource() so you can trigger the flow from your own button, and Google supplies translated graphic assets for the deeplink route.

Implementation is the easy part. Everything interesting is upstream of it.

Is your site even eligible?

This is the question the launch coverage mostly skipped, and it disqualifies a large share of the businesses reading about it.

Google's documentation sets two conditions. First, only domain-level and subdomain-level sites qualify — https://www.example.com/ and https://code.example.com/ are eligible, but https://www.example.com/blog is not. If your content strategy lives entirely in a subdirectory of a corporate site, there is nothing to select.

Second, and more restrictive: your site has to already appear in the source preferences tool. Google's instruction is to enter your site in the tool's search box and check. If it is not there, embedding the button gives readers a control that cannot do anything.

The honest read is that this is a feature built around the Top Stories index. Google has not limited it to registered news organisations, but the surface it feeds is a news surface, and sites that never enter Top Stories get very little from being preferred there.

Before you spend a sprint on this, spend two minutes on the check. Enter your domain in the source preferences tool. If it returns nothing, the rest of this article is context, not a task.

Where does preferred status actually appear?

Coverage of the announcement widely described the effect as spanning Search, Discover and Google News. Google's technical documentation is narrower, and where the two disagree the documentation is what the ranking systems implement.

Discover and Google News did get personalisation upgrades in the same August 2026 announcement cycle — natural-language feed tuning through the three-dot menu in Discover, and customisable audio briefings in the Google News Android app. Those are separate features that happen to share a news cycle. Conflating them will lead you to expect Discover lift from a button that does not produce it.

Note also what the badge is and is not. In AI Overviews and AI Mode you get marked, not necessarily cited more. Being visually distinguished inside an answer someone may never click is a weaker outcome than the framing "fights AI-driven traffic loss" implies.

How much traffic does this actually return?

Google's stated case is that when someone selects a preferred source, "they click to that site twice as much on average." That line has been repeated by Google since December 2025 and restated at each subsequent milestone.

It is also, as PPC Land noted in tracking the announcements, a claim with no disclosed baseline or methodology. Twice as much as what? Compared with non-selecting users, with the same users before selecting, or with an unmatched control? Over what window, across how many sources, at what absolute volume? None of it has been published.

There is a strong selection-bias reading available. People who deliberately hunt down a publication and mark it as preferred are already that publication's most loyal readers. A doubling among people who were about to click anyway is a very different business case from a doubling among the marginal audience — and Google's phrasing does not let you tell them apart.

The adoption number deserves the same scepticism. 600,000 is a count of unique sources selected, not a count of readers, sessions, or clicks. One enthusiastic user selecting forty outlets moves that number by forty. Google has not published how many people have set any preference at all. The growth curve is genuinely steep — roughly 90,000 in December 2025, 345,000 in late May 2026, 600,000 in August 2026 — but it measures breadth of the catalogue, not depth of usage.

None of that makes the feature worthless. It makes it unquantified, which is a different thing, and it means you should instrument it yourself rather than accept the headline number.

Which publishers does this actually help?

Here is the tension the announcement coverage glossed over entirely.

The Association of Online Publishers' AI Publisher Impact Study, conducted by DJB Strategies across eight UK publishing groups, 147 domains and 10.8 billion pageviews, found organic Google referrals fell 7.1% between Q1 and Q2 2025. Sustained, that trajectory halves Google-delivered pageviews by Q3 2027 — before compounding AI effects.

But the aggregate hides the real story:

The segment bleeding more than three times as fast is the consumer and B2B segment — precisely the publishers least likely to appear in Top Stories, and therefore least likely to be eligible for the feature designed to help.

That is the structural problem. Preferred Sources routes a loyalty signal through a news surface. If your traffic loss comes from evergreen how-to content being absorbed into AI Overviews, there is no Top Stories placement waiting to catch you.

The scale of that absorption is well documented. Pew Research Center found that across 68,879 searches by 900 US adults, users clicked a traditional result on 8% of searches with an AI summary versus 15% without — and clicked a link inside the summary on just 1% of visits. They were also more likely to end the session entirely: 26% with a summary against 16% without.

A preference toggle does not touch that mechanism. It changes which sources get selected when a click happens; it does not create clicks.

What should you do if you are not eligible?

Most businesses reading about this feature will fail the source-preferences check. That is not a dead end — it is a redirection toward the thing Preferred Sources is actually a symptom of.

The button is a demand-side lever. It works only if people already know your name well enough to want more of you. That is the same asset that determines whether a model names you in an answer it composes from many sources at once.

So the work is the same either way:

1. Check the tool first. Enter your domain in Google's source preferences tool. Eligible? Ship the button. Not eligible? Skip to step 2 and stop reading launch coverage aimed at newsrooms.
2. Make sure crawlers can reach you. Preference signals and citations both require access. Run your domain through the AI crawler checker to confirm you are not blocking the agents that build these answers.
3. Measure mentions, not just sessions. If clicks fall while branded search rises, you are winning a game your analytics dashboard is not scored for. Our guide to AI search KPIs covers what to track instead.
4. Earn the citation. Being quotable inside a synthesised answer is a distinct skill from ranking — see how to get cited by AI.
5. Instrument the button if you ship it. Tag the click, then watch branded search and direct sessions from selectors. Google will not give you the attribution; you have to build it.

If you do embed it, treat it like any other conversion element: it needs placement, wording and a reason. A grey button under a footer will be selected by nobody. The publishers seeing results are the ones asking readers explicitly, at the end of pieces those readers finished.

Frequently asked questions

Is the Preferred Sources button required to appear as a preferred source?

No. Google's documentation is explicit that these implementation methods "are examples of how you can build your audience" and that "it's not required to do them in order to appear as a preferred source." Readers can select any eligible site through the source preferences tool directly. The button removes friction; it does not grant eligibility.

Does the Preferred Sources button affect rankings?

Not in the general sense. It does not change how your pages rank for users who have not selected you. It changes what a selecting user sees — more of your content in Top Stories, a "preferred" badge in AI Overviews and AI Mode, and a "From your sources" block. It is a personalisation signal, not a ranking factor.

Can any website use Preferred Sources?

Only domain-level and subdomain-level sites that already appear in Google's source preferences tool. Subdirectories such as example.com/blog are not eligible. In practice the feature is built around Top Stories, so sites that do not publish fresh, news-shaped content get limited benefit even where technically eligible.

How many people have set a preferred source?

Google has not said. The published figure — more than 600,000 as of August 2026 — counts unique sources selected, not users. One reader selecting many outlets increases it many times over. Treat it as evidence of catalogue breadth rather than of audience adoption.

Will this recover traffic lost to AI Overviews?

There is no published evidence that it does at scale. Google's "twice as likely to click" claim has no disclosed baseline or methodology, and Pew's data shows the underlying click suppression is a property of the AI summary itself, not of source preference. Expect it to help retain readers you already have, not to recover an audience that stopped clicking.

Does being a preferred source help in Discover or Google News?

Search Central does not list Discover or Google News as preferred-source surfaces — only Top Stories, AI Overviews and AI Mode. Discover and Google News received separate personalisation features in the same period, including natural-language feed tuning and customisable audio briefings, but those are not driven by preferred-source selection.

What to do next

Check eligibility, ship the button if you qualify, and instrument it yourself — but do not let a two-line embed stand in for the harder work. The reason this feature exists is that Google's answers increasingly end the journey, and the businesses that keep growing through that shift are the ones people search for by name.

Start with what you can verify today: run the AI crawler checker to confirm the engines can reach you, then see what an AI visibility audit surfaces for your domain with our sample report.

And if clicks are falling while your brand is holding, read AI Search Visibility: Why Clicks Are Falling and Brand Demand Isn't — it is the same shift Preferred Sources is a response to, measured from the other side.