GUIDE · GOOGLE PREFERRED SOURCES
Your readers can now choose you. Here is how that actually works.
Google Preferred Sources, explained end to end: the timeline, the two-line implementation, what Google's own history with reviews and AMP predicts, and the parts nobody can measure yet.
What preferred sources actually is
Preferred sources is a reader-side setting: a person marks the sites they want more of, and Google then shows those sites more often in the Top Stories module, with a "preferred" badge. The picks are made in the source preferences tool, or now from a button on your own pages. Since 27 May 2026 the same selections also carry the badge inside AI Mode and AI Overviews, and Google says preferred sources surface more often in those AI answers.
Two eligibility rules decide whether any of this applies to you. Only domain and subdomain level sites can appear: example.com and news.example.com are eligible, example.com/blog is not. And your site has to already be listed in the source preferences tool. Checking takes about thirty seconds and it is the first thing to do, before any implementation work.
The timeline, and what it tells you
The feature went from a Labs experiment to a global surface wired into AI answers in fourteen months. The selection counts are the number Google keeps publishing, and they are the clearest public signal of adoption.
| Date | What shipped | Scale Google reported |
|---|---|---|
| 26 Jun 2025 | Search Labs experiment opens in the US and India | Labs only |
| 12 Aug 2025 | Launches for Top Stories in the US and India | 2 countries |
| Dec 2025 | Expands to English worldwide | ~90,000 sources selected |
| 30 Apr 2026 | Opens in all supported languages | ~200,000 sources selected |
| 27 May 2026 | Reaches AI Mode and AI Overviews with a preferred badge | >345,000 sources selected |
| 20 Aug 2026 | Publishers get an embeddable button and a deeplink | >600,000 sources selected |
Read the last two rows together. Google moved preferred sources into AI answers first, and only then handed publishers a button to grow the selections. That ordering is the whole strategy: reader preference is being turned into an input for AI citation, and Google wants publishers doing the recruiting.
What Google's history says you should do
Every few years Google hands publishers a new lever, and the useful question is never "does it work" but "which kind of lever is it". Two decades of these splits cleanly into two categories, and they have opposite risk profiles.
Technology mandates: you rent the position
In 2016 Google made AMP a requirement for the mobile Top Stories carousel. Publishers rebuilt their front ends for it because the alternative was losing the position entirely. In June 2021 the Page Experience update removed the requirement, and the specialised investment stopped paying anything. Nobody did anything wrong: the terms of the lease simply changed, which is what happens with anything Google can revoke by policy.
Audience assets: a person decided, so it survives
Google Maps opened user reviews in June 2007. The product around them was renamed and rebuilt repeatedly (Local Business Center, then Places in 2010, then My Business in 2014, then Business Profile in 2021), and through every rename the reviews carried over, because a review is a decision a real person made about a real business. The businesses that started asking early accumulated something the redesigns could not take back.
The rule this gives you: size the investment to the category. A technology mandate deserves the minimum implementation that keeps you in the position, and a plan for the day it is withdrawn. An audience asset deserves patient, repeated asking, because the thing you accumulate outlives the interface. Preferred sources is unmistakably the second kind, and the implementation cost is two lines of HTML rather than a re-platform, which is the best risk profile Google has offered publishers in years.
Where the reviews analogy breaks
The comparison is useful for deciding how to act, and misleading if you take it further than that. Three differences matter.
- Reviews were visible, this is not. You can count your reviews, read them and respond. Google publishes no count of who has added you as a preferred source, in Search Console or anywhere else.
- Reviews influenced everyone, this influences one person. A review changed how your business ranked for every searcher. A preferred-source pick changes only what the person who made it sees. It compounds through volume of readers, not through authority.
- Reviews came from customers, this comes from repeat readers. The asset behaves like a subscription: it rewards publications people come back to, and does nothing for a site someone lands on once.
The practical translation: treat a preferred-source selection as a retention asset, roughly as valuable as a newsletter signup and asked for in the same moments, not as a discovery channel that will move next quarter's traffic.
What is honestly known, and what is not
Four numbers are worth carrying into any conversation about this feature, along with what each one is actually worth.
- "Clicked about twice as often." This is Google's headline claim for preferred-source links. It is Google's own data, published without methodology, sample size or baseline, and it has not been independently verified. Directional, not a forecast.
- More than half of Labs users picked four or more sources. This one is genuinely encouraging for smaller publishers: readers build a shortlist, they do not crown a single winner.
- Low single-digit adoption. Independent estimates put the share of US users who have set any preferred source in the low single digits. The asset is early.
- No publisher-facing metric at all. There is no Search Console dimension and no Analytics report. A head of search at a news publisher told Digiday they had seen no meaningful traffic and, more to the point, no way to track or report on it.
Anyone selling you a preferred-source "score" or a count of your selections is inventing it. The honest position is that this is a cheap, low-risk asset with a plausible upside and no measurement, and that combination is exactly why it should cost you an afternoon rather than a project.
Who should act on this now
Act now if your domain appears in the source preferences tool and you publish on a cadence: news and trade publications, destination and travel media, hotel groups and hospitality brands that run a real editorial layer, and any site that already appears in Top Stories or gets cited in AI Overviews.
Do not spend time on it yet if your domain is not listed in the tool, if your publication lives in a subdirectory of a larger site (not eligible), or if you have no repeat audience to ask. A single-property hotel site with no publishing rhythm is better served by the fundamentals: entity consistency, structured data, and the review profile AI engines actually read.
That is the live Google button, running on this page with a deeplink fallback for readers whose browser blocks the script. Everything below is how it is built.
How to implement it
Google supports three approaches, and the right one depends on how much control you need over the trigger.
1. The standard button (two lines)
Load the library, then drop the element wherever the button belongs. Google renders an official, automatically localised button and returns the reader to where they were.
<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>
<div google-add-preferred-source-btn data-theme="dark" data-lang="en"></div>data-theme takes light (the default) or dark. data-lang overrides the reader's browser language, which is what you want on a site that already knows its own locale.
2. Programmatic control
If the flow should start from your own UI, load the script with preferred-sources-control="manual" so it does not auto-render, then bind the call yourself. The same API is available as an ES module import from publisher.mjs.
<script async preferred-sources-control="manual" src="https://news.google.com/swg/js/v1/publisher.js"></script>
<script>
(self.PREFERRED_SOURCE = self.PREFERRED_SOURCE || []).push(function (preferredSource) {
preferredSource.init({ theme: 'dark', lang: 'en' });
document.querySelector('#myButton').addEventListener('click', function () {
preferredSource.addPreferredSource();
});
});
</script>3. The deeplink (no JavaScript)
If you cannot run the script, link straight into the source preferences tool with your domain prefilled. This also works in newsletters, social posts and anywhere else you can put a link.
<a href="https://www.google.com/preferences/source?q=example.com">Add as preferred source</a>What we changed for production
The two-line version works, and four adjustments make it safe on a content site that cares about Core Web Vitals.
- Load the library lazily. One loader per document, fetched through an IntersectionObserver only when a button comes within about 600px of the viewport. A reader who never scrolls to the footer never pays for the script.
- Ship a fallback that works first. The deeplink is what renders by default. The Google button is revealed only on the library's load event, so a blocked or failed script leaves a working link instead of an empty box.
- Reserve the layout. Swapping fallback for button inside a fixed-height row keeps the insertion from shifting text, which is the usual way third-party buttons damage CLS.
- Set
data-langfrom the page locale. On a multilingual site the browser language is the wrong default: a French page should ask in French.
Where to put the ask
The reviews era answered this question already: the ask converts at the moment value has just been delivered, and it fails when it interrupts. For a property that means the booking confirmation, the post-stay email and the thank-you state after an enquiry, ahead of a permanent footer slot that catches everyone and converts nobody.
What to avoid is the same list as always: interstitials, anything above the content, and any wording that implies the reader is doing you a favour they cannot undo. Say what it changes, say it takes one click, and say it can be reversed. A selection made under pressure is worth nothing, because the reader who regrets it removes it in the same tool.
Where to put the preferred sources button works through the nine placements in order, with the tenth and why it is withheld.
How to measure something Google gives you no data for
You cannot count your selections, so build a proxy stack and be explicit that it is a proxy.
- Click intent. Fire an analytics event on every click of your button or deeplink. It measures intent, not confirmed additions, and it is the only number you fully own.
- Branded query trend. Watch branded impressions and clicks in Search Console. Readers who select you are readers who already know your name, so the two tend to move together.
- Top Stories impressions. Track the news-surface impressions you can see, and read them alongside the selection campaign rather than as proof of it.
- Returning readers. If preferred sources is a retention asset, the honest KPI is retention: returning visitors and direct sessions.
Decide in advance what would make you stop. If the button gets a meaningful click volume for two quarters and branded search, Top Stories impressions and returning visits are all flat, the reasonable conclusion is that the asset has not compounded yet, not that the measurement failed. Say that out loud before you start, and this stays a cheap experiment instead of an article of faith.
Questions people are actually asking
Does being a preferred source improve my rankings for everyone?
No. A preferred-source selection only changes what the person who made it sees. It is personalisation, not a ranking signal, so it behaves like a newsletter subscription rather than like a backlink. The compounding effect comes from volume of readers who select you, not from any sitewide boost.
Can I pay Google to be a preferred source, or get selected faster?
No. There is no paid placement and no application. The only levers a publisher has are being eligible (your domain has to appear in the source preferences tool) and asking your readers to select you. Google's own documentation frames the button and the deeplink as ways to ask, and states they are not required to appear as a preferred source.
Is my hotel or small business eligible?
Check before you plan anything: enter your domain in the source preferences tool at google.com/preferences/source. Only domain and subdomain level sites are eligible, so example.com and news.example.com can appear while example.com/blog cannot. Many single-property sites are not listed, in which case the honest answer is that this is not your lever yet.
How many people actually use this?
More than 600,000 unique sources had been selected as of 20 August 2026, up from about 90,000 in December 2025. Independent estimates still put the share of US users who have set any preferred source in the low single digits, so treat it as an early asset that is growing, not as a traffic channel that is already meaningful.
How do I know if it is working?
You cannot measure it directly. Google publishes no preferred-source dimension in Search Console and no report in Analytics, so the practical approach is to track clicks on your own button as an intent proxy, watch branded query volume and Top Stories impressions in Search Console, and follow returning-visitor trends. Anyone promising you a precise count is guessing.
- Does preferred sources affect AI Overviews and AI Mode? Yes, since 27 May 2026, and the effect is personal rather than sitewide.
- Where should the button go on a hotel site? Nine placements ordered by the moment they interrupt, and the tenth we are not recommending yet.
- How do I add the button to my site? The eligibility check, the markup, the manual version and the fallback link.
- Can preferred sources be gamed? Not the way reviews and links are, because the signal is held per reader rather than pooled.
- Is it worth it for a small hotel? Worth twenty minutes if your domain is eligible, and not worth a project either way.
Sources
- Help your readers find your site through preferred sources in Google Search
- How to select your preferred sources in Top Stories in Search
- Preferred Sources in Top Stories is now available in English to all users around the world
- Google Search: Preferred Sources now available in all languages
- Google brings Preferred Sources into AI Overviews and AI Mode today
- Google Preferred Sources gains 255,000 selections since late May
- Google gives publishers a new way to fight AI-driven traffic losses
- Without transparency, publishers can't tell if Google's Preferred Sources feature benefits them
- Google Search tests Preferred Sources for Top Stories
- Google top stories carousel now showing non-AMP listings
- Google Maps adds user generated reviews
DONE FOR YOU
We set this up as part of AI search visibility work: eligibility check, button implementation with the fallback, placement, the analytics event, and the reporting that tells you whether it is compounding.
See how that works →