Google Preferred Sources: the complete publisher guide (2026)

What are Google Preferred Sources?

Preferred Sources is a user-controlled personalization feature. From Google's source preferences tool, a person ticks the sites whose content they want to see more often. Google then applies that preference to their results.

Google's documentation puts it this way: "When a user selects your site as a preferred source, your content is more likely to appear in 'Top Stories', highlighted with a 'preferred' badge." The same principle now extends to AI-generated answers.

Two facts shape everything else in this guide. First, the reader decides, not the algorithm, no technical optimization triggers the addition on their behalf. Second, the effect is per-person: your site surfaces more for the people who added you, and for nobody else. This is not a global signal that shifts your position for everyone.

Timeline: what has changed since August 2025

The feature has moved a lot in a year, and much of what's published online still describes its 2025 state. Here are the verifiable dates:

The step that matters most is May 27, 2026: that's what turned Preferred Sources from a news-publisher topic into a generative-search visibility topic.

Which surfaces Preferred Sources affect

The publisher documentation names two families of surfaces, precisely:

• Top Stories, available "in all languages where Google Search operates." This is the original surface from the 2025 launch. Selected sources appear more frequently in the carousel, or in a dedicated "From your sources" section.
• AI Overviews and AI Mode, available "in all languages and locales where those features are available." When a site you've added is cited in a generated answer, a "preferred" badge appears next to the link.

The two settings are linked: Google's help pages note that selecting preferred sources from AI Mode also tailors your Top Stories experience, and vice versa. Users maintain one list, not two.

Google Discover is not listed in the Preferred Sources documentation. The August 20, 2026 announcement does include a Discover change, the ability to describe in your own words which topics you want more or less of, but that's a separate mechanism. Don't merge the two when advising a client.

Google's "2x more clicks" claim, read honestly

This is the number everyone repeats. Google stated it on April 30, 2026 ("Readers are twice as likely to click through to a site after marking it as a Preferred Source") and repeated it on May 27, 2026. It's real, it comes from Google, and it's worth citing, but it is not a promised traffic gain.

Three caveats to state every time, before it reaches a client deck:

• No methodology has been published. Google disclosed no sample size, no time window, and no precise comparison group. This is a product statement, not a reproducible study.
• Causality isn't established. People overwhelmingly add sites they already like and already read. Some meaningful share of that "2x" is pre-existing affinity showing up in the numbers, not an effect the feature created.
• It's a multiplier on a base, not a volume. Twice as many clicks from the people who added you says nothing about how many people that is. If three hundred readers added you, the doubling applies to three hundred readers.

The defensible framing in a meeting: "Google says readers click through roughly twice as often to a source they chose themselves. That's a multiplier on an audience you already have, not an acquisition channel."

Who is eligible for Preferred Sources?

Eligibility is broader than most people assume, this isn't a news-publisher-only feature. Google states that any site publishing fresh content is eligible, and the 2026 announcement explicitly names everything "from niche local blogs to global news desks."

There are two documented constraints, though:

• Domain and subdomain level only. The documentation is explicit: "Only domain-level and subdomain-level sites are eligible to appear in the source preferences tool." https://www.example.com/ and https://code.example.com/ qualify; the subdirectory https://www.example.com/blog does not. If your publication lives in a folder on a corporate site, it can't be added as a source in its own right.
• Regular publishing. Google's help pages note that "sources that aren't updated regularly may not be available." Google has not documented a minimum frequency.

The decisive test takes ten seconds: search for your domain in Google's source preferences tool. If it appears, you're eligible and you can install the button. If it doesn't, fix that first, the documented implementation methods all assume your site already shows up in the tool.

How a user adds a preferred source

There are three paths, all on the user's side. Knowing them lets you write accurate instructions instead of approximate ones.

From settings, on desktop:

1. Go to google.com and click your profile picture in the top right.
2. Open "Search personalization," then "Source preferences."
3. Search for the site and tick its checkbox.

From Top Stories: run a news-related search, click the star icon to the right of the "Top stories" header, search for and tick your sources, then click "Reload results."

From a direct link: the URL https://www.google.com/preferences/source?q=example.com opens the tool straight to the domain you specify. That's the format Google documents for text links and image buttons.

Two useful details: preferences carry across browsers when the user is signed in to a Google Account, and removing a source works exactly like adding one, untick the box. Google hasn't documented a maximum number of sources; the launch announcement said "you can select as many sources as you like."

The August 20, 2026 publisher button: standard and advanced implementations

This is the change that matters most to publishers. Previously you had to send readers off to a Google preferences page and hope they came back. Since August 20, 2026, Google provides an official button that, per the announcement, "adds the site as a Preferred Source on Google and immediately directs them back to where they left off on the publisher's page." Almost all the friction disappears.

The standard implementation Google recommends is literally two lines of HTML:

• In the <head>: <script async src="https://news.google.com/swg/js/v1/publisher.js"></script>
• Wherever the button should render: <div google-add-preferred-source-btn></div>

The rendered button is Google-styled, device-aware, and automatically localized into the user's language, worth knowing if you run a multilingual site, because there's nothing to translate yourself.

Two attributes are documented for adjusting the rendering:

• data-theme takes light (the default) or dark: <div google-add-preferred-source-btn data-theme="dark"></div>
• data-lang forces a specific language and overrides automatic detection: <div google-add-preferred-source-btn data-lang="en"></div>. Google supplies the accepted language codes in a CSV file alongside the documentation.

Three advanced variants are documented for the cases where the standard button doesn't fit.

ES module import (ESM). For a modern application managing its own imports, Google exposes preferredSource from https://news.google.com/swg/js/v1/publisher.mjs. You call preferredSource.init({ theme: 'light', lang: 'en' }) at setup, then preferredSource.addPreferredSource() inside your own button's click handler. Your design assets stay entirely yours.

Callback queue (IIFE). For a conventional site built on global scripts, load the same library with automatic rendering switched off, <script async preferred-sources-control="manual" src="https://news.google.com/swg/js/v1/publisher.js"></script>, then push your initialization onto self.PREFERRED_SOURCE, which receives the preferredSource object once the library is ready. Same pattern as most ad tag queues.

Deeplink. The no-JavaScript option: a plain link to https://www.google.com/preferences/source?q=example.com, either as text or wrapped around an image. Google documents both forms. It's the least smooth, there's no automatic return to your page, but it's also the only one that loads no third-party script. For a European site with strict consent management, that difference isn't trivial: loading Google's library is a third-party script, and it needs handling in your consent platform like any other. Google has published no specific guidance on this point.

Encouraging readers without stepping outside Google's guidance

An important point to state precisely: Google has published no rules specific to promoting Preferred Sources. The documentation lists no prohibited practices, no restriction on incentives, and no associated penalty. It only says these methods "are examples of how you can build your audience and help people find your site as a preferred source" and that "it's not required to do them in order to appear as a preferred source."

That absence of written rules isn't a blank cheque. Google Search's general spam policies still apply, and the right frame is risk rather than formal prohibition. What's clearly safe:

• Placing the official button where a reader has already shown interest: end of article, about page, the thank-you page after a newsletter signup, the subscriber area.
• Explaining in one sentence what the click actually does, "see our articles more often in your Google results", rather than promising a vague benefit.
• Mentioning it through channels your audience already opted into: newsletter, social, community.

What we'd advise against, given the lack of explicit guidance and out of plain caution: gating content, access, or a discount behind adding you as a preferred source; aggressive interstitials that block reading; implying the addition is required to keep receiving your content. None of these are documented as prohibited by Google, but all of them resemble patterns Google penalizes elsewhere, and none of them are necessary to earn additions.

How to measure impact (and why it's hard)

Say this plainly to clients before starting the work: Google provides no Preferred Sources reporting. As of today there is no count of how many people added you, no dedicated filter in Search Console, and no dimension in Google Analytics. The documentation mentions no tracking mechanism, no success callback, and no reporting API. Publishers quoted in the trade press have voiced their frustration on exactly this point.

Three indirect measures remain, imperfect, but usable:

• Clicks on your own button. Fire a custom GA4 event on click. Be clear about what you're measuring: this is intent, not a confirmed addition, you can't see what happens on Google's side afterwards. It's still enough to compare two placements, two wordings, or two templates against each other.
• Branded search volume. In Search Console's Performance report, track the trend for queries containing your name. Successful loyalty work shows up there, even though it will never be attributable to Preferred Sources alone.
• Click trends on your news queries. Worth watching after an add campaign, bearing in mind that news seasonality is a far stronger driver.

The methodological conclusion: treat Preferred Sources as a retention investment, not a measurable channel. Any agency promising precise reporting on this feature is selling you something Google doesn't produce. If you want a quantified picture of your visibility in generative search, that comes from a GEO audit, not from a Preferred Sources dashboard.

What Preferred Sources does not do: it is not a ranking hack

This is the most important section in the guide, because it's where most content published since May 2026 goes wrong. Let's be explicit about the limits.

• It is not a global ranking signal. The documented mechanism is per-user personalization. Google has never stated that a high number of additions improves your position for people who haven't added you. Any claim to the contrary is extrapolation, not information, and Google has not publicly commented either way.
• The badge is not public. The "preferred" badge is visible only to the user who made the choice. Competitors don't see it. Neither do prospects, unless they added you themselves.
• It does not create audience. Someone has to already know your site to add it. This retains an existing audience; it does not acquire a new one.
• It guarantees no placement. Google's wording is "more likely to appear," not "will appear." Relevance to the query and content freshness still decide.
• It does not replace the underlying work. Being chosen as a source by a model and being ticked manually by a reader are two different mechanisms. The first is Generative Engine Optimization, and it's won on content and structure.
• It is not the "Highly Cited" badge. Introduced on May 27, 2026, "Highly Cited" flags articles widely cited by other publications. The two signals are independent: you can earn either one without the other, in both directions.

The accurate way to position it: Preferred Sources is a retention lever inside search results. It amplifies a relationship that already exists. It's useful, it's cheap to implement, and it replaces nothing.

WordPress and other CMSs: where to actually put the button

Google ships no official plugin for WordPress, Webflow, Shopify or any other CMS. Implementation stays manual, but it's light.

On WordPress, the script goes into the <head> once, via a child theme's header.php, a wp_head hook in a code snippets plugin, or the "header scripts" field most premium themes provide. The <div> container then goes wherever the button should appear: in single.php after post content, in a reusable custom HTML block, or behind a small shortcode if your editors need to place it themselves.

On other CMSs, the logic is identical: one global slot for the script, one raw HTML block for the container. No CMS needs anything beyond those two insertions.

Three practical things to watch:

• Deferred rendering. The script loads async, so the button appears after initial page render. Reserve a fixed height for it in CSS to avoid a layout shift that would hurt your Core Web Vitals.
• Caching. On aggressive page caching or static HTML setups, confirm the container is present in the cached markup, it's Google's script that hydrates it in the browser, not your server.
• Consent. If your banner blocks third-party scripts before acceptance, the button won't render for visitors who haven't consented. The deeplink is your fallback there.

Don't put the button everywhere. One end-of-article placement and one in the footer is plenty: a reader who just finished an article is a credible candidate, a visitor landing on a product page is not.

Preferred Sources vs organic ranking vs AI Overview citation

Confusing these three levers explains most of the strategy mistakes we've seen since spring 2026. They don't share a trigger, a lever, or a measurement method. The table below puts each back in its place, it's the frame we use in audits to decide where effort should go.

Preferred Sources checklist

• Confirm your domain appears in Google's source preferences tool, everything else depends on it.
• Check that your content lives at the root of a domain or subdomain, not in a subdirectory: folders aren't eligible.
• Publish regularly, sources that aren't updated may not be offered.
• Install the standard button, two lines of HTML: the script in the <head>, the container where you want it.
• Set data-theme to match your design; leave language on automatic detection if your site is multilingual.
• Reserve a fixed height for the container so it doesn't cause a layout shift.
• Plan the deeplink as a fallback if your consent setup blocks third-party scripts.
• Fire a GA4 event on button click, and document that it measures intent, not a confirmed addition.
• Tell your existing audience it exists (newsletter, social) and explain in one sentence what the click does.
• Never gate content or a benefit behind adding you as a preferred source.
• Align expectations internally: this is a retention lever, not an acquisition lever, and there is no official reporting.
• In parallel, work on the substance with a GEO audit, being ticked by a reader and being chosen as a source by a model are two separate battles.
• Ready2GEO is currently building a free Preferred Source Button generator that will output paste-ready code for your domain and theme. It isn't available yet, watch for it on our GEO tools page.