Google Preferred Sources Button: Setup and the Catch

Google has released an embeddable Preferred Sources button, so a reader can mark your site as a source they want to see more of without leaving your page. It is two lines of HTML. Google's announcement on 20 August 2026 says people have already selected more than 600,000 unique sources, and that readers are roughly twice as likely to click through to a site once they have marked it as preferred.

There is a catch that most of the coverage skipped, and it decides whether this is useful to you at all: the button only works for whole domains and subdomains. If your content lives at example.com/blog, you are not eligible.

What the button does

Preferred Sources launched inside Google's AI experiences in May 2026, letting people pick publications they want surfaced more often. Until now, marking a source meant going to Google's source preferences page and searching for the site by name or URL. The August change moves that action onto the publisher's own page, where the reader already is and already likes what they are reading.

Once a source is marked, Google's documentation says its content shows for relevant queries in Top Stories, and gets a preferred source badge in AI Mode and AI Overviews.

The framing in TechCrunch's coverage is that this is Google's answer to publishers losing clicks to AI summaries. That is fair as far as it goes. It is also a personalisation feature that only helps sites people already know they want, which is a different thing from a discovery feature. The same test you would apply to any platform announcement applies here: separate what shipped from what it was framed as solving.

The code

Script tag in the head:

<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>

Button element wherever you want it to appear:

<div google-add-preferred-source-btn></div>

That is the whole standard implementation. The button renders itself, translates itself based on the reader's browser language, and returns the reader to where they were on your page after they add you.

Two optional attributes are documented. A dark theme:

<div google-add-preferred-source-btn data-theme="dark"></div>

And a language override, if you would rather pin the label than follow the browser:

<div google-add-preferred-source-btn data-lang="en"></div>

Anything more elaborate, like triggering the flow from your own custom control, needs the advanced JavaScript path rather than the auto-rendering div.

The eligibility rule that decides this for you

Google's docs are explicit: only domain-level and subdomain-level sites are eligible. Their examples:

This is not a footnote. A very large share of small-business and startup content sits in a subfolder of the main marketing site, because that is what every SEO guide has recommended for a decade in order to consolidate domain authority. Those sites can embed the button, but the source a reader would be marking is the whole domain, not the blog.

For some businesses that is fine or even preferable. For a company whose product pages and blog serve completely different audiences, it is a real mismatch, and it is worth knowing before you spend a sprint on it. It sits alongside the other question publishers keep hitting this year, which is whether AI-generated content needs a label at all.

If your blog lives on a subdomain, you are eligible as a distinct source. That is a rare point in favour of the subdomain layout, and not one that justifies migrating on its own.

Whether it is worth adding

The honest read: it is a five-minute change with a small, uncertain, and entirely one-directional upside. Nobody has downside data on this, and the button does not affect ranking. It affects whether the readers you already have see you more often.

Which makes the placement question the only interesting one. A button that asks for a commitment works where the reader has just got value, not where they have just arrived. End of article, after the conclusion, near wherever your existing subscribe control lives. Putting it in a sticky header alongside four other asks is how it gets ignored.

Worth being clear about what this does not do. It is not a ranking signal, it does not opt you out of AI Overviews, and it does nothing for a reader who has never heard of you. If falling clicks are the problem you are actually trying to solve, the underlying question of whether Google penalises AI-generated content and how AI search changes referral traffic is the larger one, and this button is a small hedge inside it.

What to measure

There is no public dashboard for preferred-source counts, so you are inferring. Two things you can watch:

1. Direct and Discover traffic over an eight to twelve week window after adding the button, compared to the same window before. Google's own claim is a doubled click-through rate for preferred sources, so if the mechanism works for you at all, returning-visitor behaviour is where it shows.

2. Click events on the button itself, if you wire one up. That tells you the placement is working even before the traffic effect is legible.

Both of these are slow signals on small sites. Do not expect to read anything from two weeks of data. The same discipline applies here as anywhere else in search: keeping up with what Google actually shipped beats reacting to the commentary about it, and most changes need a full quarter before the numbers say anything.

FAQ

How do I add the Google Preferred Sources button to my site?

Add <script async src="https://news.google.com/swg/js/v1/publisher.js"></script> to your head, then place <div google-add-preferred-source-btn></div> where you want the button. It renders and translates automatically.

Can I use the Preferred Sources button if my blog is in a subfolder?

You can embed the button, but only domain-level and subdomain-level sites are eligible as preferred sources. A reader on example.com/blog would be marking example.com, not the blog specifically.

Does being a preferred source improve my rankings?

No. It changes what shows for the people who have specifically chosen you, in Top Stories, AI Mode and AI Overviews. It is a personalisation signal, not a ranking one.

Do I have to add the button to appear as a preferred source?

No. Google's documentation says implementation is optional. Readers can already add sources through Google's source preferences page. The button just removes the steps in between.

Is there a dark mode version?

Yes, add data-theme="dark" to the button div. The default is light.