Google's Preferred Sources Button: What It Does, When It Pays Off, and How to Install It

Google's Preferred Sources Button: What It Does, When It Pays Off, and How to Install It

On 20 August 2026 Google gave site owners a button they can embed directly in their pages. A reader clicks it, your site joins their preferred sources in Google, and from then on your articles are more likely to surface for them — carrying a label that sets them apart.

The feature itself is not brand new. It already existed in Top Stories, and on 27 May 2026 Google extended it into its AI experiences: AI Overviews and AI Mode. What changed in August is where the request lives. It moved out of Google's settings and onto your page, where the reader already is and has just decided they like what they read.

We installed this button on the Origami site the day it was announced, and ran into details the documentation does not mention. Here is what we learned.

What the button actually does

When a reader clicks it and confirms in Google, three things change — for that reader specifically, not for everyone:

• In Top Stories. Your content is more likely to appear, marked with a "preferred" badge that distinguishes it from the rest of the results.
• In AI answers. When a link to you appears inside AI Overviews or AI Mode, it carries the same badge. This is the part that matters most today: you are no longer only competing for the click, but for being cited by the model at all.
• In the developing-topic carousel. Google added a prominent link carousel for some questions on developing topics, and preferred sources are highlighted inside it.

Note the limits: the choice is personal to each signed-in user, not a general ranking boost. It does not lift your site for people who never selected you, and it does not compensate for weak content.

Why now — the number that explains the timing

The stated reason is blunt: AI answers satisfy the reader inside the results page, so fewer clicks reach websites. The button is Google's attempt to give publishers a compensating channel through their loyal audience rather than passing traffic.

The figure worth noting comes from Google itself: people are twice as likely to click through to a preferred source. And as of the May launch, more than 345,000 unique sources had already been selected this way. The behaviour exists and is in use; the button just shortens the path to it.

Is it worth it for your site? When yes and when no

The official bar is low: any site that publishes fresh content is eligible. But eligibility and worthwhileness are different questions:

• Clearly worth it if you publish regularly: a technical blog, sector news, market analysis, an evolving body of educational content. A reader who comes back twice will click without hesitating.
• Moderately worth it if you have a small loyal audience even at a lower publishing rate. The effect accumulates with every reader who pins you.
• Not worth it yet if your site is a static brochure with no ongoing publishing. Visitors will not find a reason to make you "their source," and the button will sit unclicked.

A practical rule on placement: put it where the reader has just been convinced — at the end of an article they finished — not on the homepage, where they have not read anything of yours yet.

Three ways to install it, and how to choose

Google documents three approaches. The difference is not only cosmetic; each one trades something away:

1. The drop-in button, two lines of code

You add Google's script in the head, then an empty element carrying the google-add-preferred-source-btn attribute wherever you want the button. Google renders it in its official style, translates it automatically to the browser's language, and supports a light or dark theme plus a manual language override.

This is the easiest route and the cleanest looking, and it suits most conventional sites. It carries two constraints we hit in practice, covered below.

2. Manual mode with your own design

You load the same library with an attribute that stops it rendering anything, initialise it programmatically, and bind your own button to the add function. The flow the reader sees is still Google's, but the trigger is an element on your page that you fully control.

3. A plain deeplink, no JavaScript

If your platform will not let you add scripts, you place a text link or an image pointing at Google's source preferences page with your domain. It is the simplest and least smooth option, because it sends the reader to Google rather than finishing the job in place. It also works in newsletters and social posts.

Three lessons from installing it on our own site

None of these are in the documentation, and each one cost us time:

• The drop-in button disappears on modern sites. Google's library scans the page once, when it loads. Sites built on frameworks like Next.js or React move between pages without a reload, so the button's slot stays empty after the first navigation. The fix is to call the library's initialisation again on every route change — that worked for us.
• The drop-in button cannot be tracked. Google renders it inside an iframe on its own domain, and cross-origin boundaries stop your page seeing any event inside it. We tried capturing the click, focus moving in, and focus leaving the page; no signal arrived. So if counting clicks matters to you, manual mode is your only option.
• The official badge has no Arabic. Google ships an official image pack for the button, but it covers seventeen languages and Arabic is not one of them. The interactive button does support Arabic. So if you want the official look on an Arabic page, you will build the button yourself and reuse Google's own Arabic wording.

The short version: if your site is conventional pages and you do not need measurement, take option one. If your site is a modern framework build, or you want to know how many people clicked, option two fits better despite the extra work.

After installing: how do you measure the effect?

Google does not yet give you a report telling you how many readers added you as a preferred source. The measurement is on you, from three angles:

• Click count. Requires option two, and it is the closest direct indicator of how readers respond to the button.
• Return visits. Compare your returning-visitor share before installing and two months after. A preferred source should lift returns, not first visits.
• Top Stories presence. Watch impressions and clicks in Search Console for your recent articles specifically.

Do not expect a jump within a week. The button builds an audience that deliberately chose you, which accumulates slowly but is not at the mercy of an algorithm change.

The Origami view

We treat this button as part of a bigger shift we see forming: visibility inside AI answers is becoming a track of its own, separate from classic search optimisation. When the result answers the reader directly, the value moves to being cited and labelled by the model, not to your ranking alone. The button is a small tool on that track, but it is the kind that rests on your relationship with your audience rather than on the algorithm — which is exactly what we advise our clients to build: a readership that chooses you, not traffic rented from a search engine that may change its rules tomorrow.

We installed it on our blog the same day, placed it at the end of articles rather than on the homepage, and measured clicks from day one. If you want our read on the right placement for your site, or want it installed for you, it is under an hour of work.

Sources

• The official Google blog, 27 May 2026 — extending Preferred Sources into AI Overviews and AI Mode, source of the twice-as-likely figure and the count of selected sources.
• Google Search Central documentation — the Preferred Sources guide for web publishers: eligibility criteria and the three implementation methods.
• TechCrunch, 20 August 2026 — the embeddable button announcement and its context in publisher traffic decline.
• Google's source preferences page — the tool through which a site is added.