Google Preferred Sources Button: A Two-Line Embed

🇹🇷 Türkçe: Bu yazının Türkçesini oku →

Every few years, Google hands publishers a piece of HTML and expects them to paste it. The last one that actually mattered was the rel="canonical" tag. I am old enough to have handled that rollout for print magazines that were still figuring out what “canonical” meant, and I remember the specific look on an art director’s face when I told him a two-word link attribute would fix six months of duplicate-content pain.

This week Google shipped another one. It is not as fundamental as canonical, but it is worth understanding before your marketing team asks about it on Wednesday. The embed is two lines of HTML. The mechanic is simple. The strategic point behind it — that Google is quietly building an earned-visibility track parallel to ranking — is the interesting part.

Here is what actually shipped, what to do with it on WordPress, and what I would not bother with.

What is actually new

On August 20, 2026, Google updated the Search Central documentation page for Preferred Sources and added an official embeddable button. The Latest Search Documentation Updates page timestamps the change to 2026-08-20 UTC. The reader-facing feature itself is not new — Google first launched Preferred Sources in the U.S. and India in August 2025, and then extended it into AI Mode and AI Overviews on May 27, 2026, per Duncan Osborn’s post on the Google blog. What is new is that publishers can now drop a Google-styled button onto their own pages without hand-rolling anything.

The standard implementation, per Google’s docs, is exactly two lines:

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

The button renders in the reader’s language automatically. You can override with data-lang, force data-theme="dark" or data-theme="light", and — with the advanced JavaScript path — bind your own UI element and call the SDK programmatically. If you cannot ship JavaScript at all, there is a deeplink: https://www.google.com/preferences/source?q=example.com, which you can wrap in a plain text link.

The important restriction, which Google spells out plainly: the feature is domain- and subdomain-level only. example.com qualifies. code.example.com qualifies. example.com/blog does not. If you run a network on subdirectories — a very common WordPress multisite pattern — each subsite cannot be its own preferred source. The whole apex domain is the unit of preference.

Adoption of the underlying feature is real. Duncan Osborn’s May post claimed 345,000 unique sources had been selected by users. By the August button rollout, industry trackers put the number past 600,000. Google also cites its own data that users are roughly twice as likely to click through to a site they have marked as preferred, on the surfaces where Preferred Sources appears — Top Stories, AI Mode, AI Overviews.

Why it matters for WordPress and WooCommerce people

Two reasons, one obvious and one less so.

The obvious one: if you publish news, opinion, product reviews, or any content that touches Top Stories, you now have a one-click prompt for the readers who already like you. On WordPress that lands cleanly. A block theme site can add the two-line snippet inside a footer or header template part in the Site Editor. A classic theme site can drop it into footer.php, or expose it as a shortcode from a small mu-plugin. A WooCommerce merchant with a content blog attached — which is most of them — can put it on the blog archive and single-post templates without touching the store. No plugin required, no dependency to audit, no supply-chain surface added. That is the kind of change I like: additive, removable in ten seconds, no server round-trip.

The less obvious one: this is the second time in a year Google has handed publishers a lever that sits outside the ranking algorithm. First it was the Preferred Sources user setting, which routes around the ranking model — a reader tells Google “always favor this site”, and Google does. Then it was Platform Properties in Search Console for social and video. Now it is an embeddable button that lets you convert brand loyalty in the wild into a signal Google actually consumes. Twenty years of SEO taught the industry to optimize on-page and hope. What Google is quietly building alongside that is earned visibility: readers, not crawlers, deciding you deserve to show up. If you already have a healthy newsletter, an engaged Discord, a customer base that comes back — you now have a way to convert that into search presence. That is a different game than “target this keyword cluster and pray”.

The August 20 update to the button also added something small but useful: the button now returns the reader to the page they came from after they finish selecting your site. Before, they landed in Google’s preferences UI and had to find their way back. That single fix is probably worth more to conversion than any theming option.

What I would do (or not do) about it

I would add the button. I would not add it as a modal, a full-width banner, or anything that treats a reader like a conversion event. Put it in the footer, on the About page, and at the end of long-form posts where the reader has already spent five minutes with you. That is the audience worth asking. Everyone else is noise, and Google’s own docs are quite specific that they will keep pushing back on abusive prompting patterns.

For a block theme, add the script tag once in your theme’s functions.php via wp_enqueue_script() with the news.google.com URL registered as an external source, then place the <div google-add-preferred-source-btn></div> anywhere via a small custom block or a Shortcode block. Do not lazy-load the script — the button already loads asynchronously, and interrupting that with your own defer logic just makes it flicker.

What I would not do: buy the “preferred source SEO” packages that will appear within a month. There is nothing to buy. Nobody can guarantee a click on the button — that is the whole design. The right move is exactly one line of your reader’s real intent, exposed at exactly the right moment, and then getting out of the way. WordPress is very good at exactly that when you stop trying to make it clever.

The button is small. The signal underneath it is not. Ship it where it belongs, then get back to writing something worth being preferred for.