What is Google Preferred Sources, and can your site use it?

Preferred Sources is a Google Search setting that lets a reader mark your site as a favorite, after which your content surfaces more often for that reader in Top Stories, AI Overviews, and AI Mode. Since August 2026 you can embed a button that adds your site in one click. The button is two lines of HTML, but it only does anything if your domain is already in Google's source index.

Most of what shows up in AI Overviews is decided by systems you do not control. Preferred Sources is the exception. It is the one placement lever in Google's AI surfaces that a human being pulls on purpose, for your site specifically, and it now has an official button you can put on your own pages. That makes it the rare GEO tactic with a yes-or-no answer attached, which is also why it deserves a check before you build anything around it.

What is Preferred Sources?

It is a per-reader setting in Google Search. A reader picks the sites they want to hear from, and Google then favors those sites in that reader's results. Google's documentation states that when a user selects your site, your content is more likely to appear in Top Stories, highlighted with a "preferred" badge.

Google shipped it quietly and then kept widening it. The first publisher documentation appeared on January 30, 2026. Language coverage opened to every language Google Search runs in on April 30. The change that mattered most for anyone doing GEO landed on May 27, when Google extended the feature into AI Overviews and AI Mode, and the embeddable button arrived on August 20 (Google Search Central).

The adoption curve is worth reading, because it tells you whether readers actually use the thing. Google reported "nearly 90,000 unique sources" selected in December 2025 (Google), and over 345,000 by the following May (Google). In that same May post Google also said people are twice as likely to click through to a preferred source. That second number is the one to keep: this is not a badge, it is a click multiplier applied to a self-selected audience.

Where does a preferred source actually show up?

Three surfaces. Top Stories carries it globally in every language Google Search supports, with a visible "preferred" badge. AI Overviews and AI Mode carry it wherever those features are available, showing links from your selected sites prominently inside the generated answer.

The AI Overviews placement is the part people underrate. Ordinary GEO work is probabilistic: you improve your odds of being pulled into a fan-out query alongside everyone else competing for the same passage. Preferred Sources is deterministic for the readers who opted in. You are not competing for that slot, you were chosen for it. The catch is that the audience is only as large as the number of people who bothered to click, which is exactly why Google built a button instead of leaving the setting buried in preferences.

How do you add the button?

Two lines. Load Google's publisher script, then drop a div carrying the google-add-preferred-source-btn attribute wherever the button should sit. Google renders a localized, correctly styled button, and a reader who clicks it is returned to the page they were reading.

<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 or dark, and data-lang overrides the reader's browser language against a list of 51 supported codes. If you want your own design, load publisher.mjs as an ES module, call preferredSource.init(), and wire preferredSource.addPreferredSource() to your own click handler. If you cannot run JavaScript at all, link straight to https://www.google.com/preferences/source?q=yourdomain.com, which also works in newsletters and social posts where a script never would. All three paths are documented in Google's guide to Preferred Sources.

Why doesn't the button work for most sites?

Because the button is the last step, not the first. Your domain has to already appear in Google's source preferences tool for a reader to add it. Two conditions gate that: the entry must be a domain or subdomain, never a subdirectory, and the site has to publish fresh content on a regular cadence.

The eligibility rule is stated plainly in the documentation. example.com and news.example.com can be preferred sources; example.com/blog cannot. If your publishing lives in a subfolder of a corporate marketing site, the thing a reader would be subscribing to is the whole domain, not your content.

The cadence rule is softer in the docs and harder in practice. Google's phrasing is that any website publishing fresh content is eligible. The tool itself is blunter, carrying a footnote that sources which are not regularly updated may be unavailable. A blog that posted twelve good articles and then went quiet for a month is exactly the shape that falls out of the index, and no amount of button markup brings it back.

How do you check whether your domain is in the index?

Open Google's source preferences tool while signed in, and type the domain into its search box. There is no public API and no way to check this from a server. The autocomplete request the page fires carries an opaque, session-bound encrypted payload rather than the query string, so it cannot be replayed with a different domain substituted in.

We ran the check by hand on September 2, 2026 against a small set of domains, and the split was clean. The established news publishers we tested were all present, returned with their brand name and logo attached: Webrazzi, Hürriyet, and Hürriyet's German edition each came back as selectable sources. The marketing sites we tested were not there at all, including this one. Searching becited.co returned only unrelated domains that happen to share the name on other TLDs.

That result is not a complaint, it is the rule working as documented. This site had published twelve articles and then paused for a month before we looked. The absence and the pause are the same fact.

Two practical notes for anyone repeating this. First, opening the tool with ?q=yourdomain.com prefills the box but does not run the search, so you have to type into the field to trigger it. Second, the matching is loose, so example.co will surface example.co.uk and you have to check the exact host rather than trusting a non-empty list.

Is it worth doing?

Yes, if you publish regularly, because the button costs two lines and the payoff is a click multiplier on readers who already like you. No, if you publish sporadically, because you are not in the index yet and the button will render a control that cannot do anything.

Put in order, the work is: publish on a cadence you can hold, confirm the domain has entered the source preferences index, then install the button where readers finish an article rather than where they arrive. Reversing those steps produces a dead button and a false sense of coverage, which is worse than not shipping it.

The wider point is that Preferred Sources moves part of AI visibility from ranking to relationship. It rewards publications people would miss if they disappeared, and it hands you a measurable way to ask whether yours is one of them. Whether your domain clears that bar today, and whether the rest of your pages are eligible for the AI surfaces you care about, is the kind of thing worth measuring rather than assuming. That check is what BeCited runs against your domain, against the methodology we publish. More of what we have measured about this shift is on the blog.