Google Quietly Added Preferred Sources for Publishers: Here's How It Works

On 20 August 2026 Google shipped a button that publishers can put on their own pages. A reader clicks it, your site becomes one of their Preferred Sources on Google, and they land straight back on the article they were reading.

Almost nobody outside the news industry noticed. Ask 10 business owners what a Preferred Source is and you will get 10 blank looks. That is the opportunity, because the feature now touches Top Stories, AI Overviews and AI Mode, and the sites that promote it early get a badge next to their links that competitors do not have.

The catch is that you cannot add yourself. This is a reader-side setting. There is no submission form, no Search Console toggle and no schema that turns it on. Your job is to be eligible, then make it easy for the people who already trust you to pick you.

This post covers exactly that in 6 steps: what the feature does, how to check eligibility, the 2 lines of code, the fallback link for places code cannot go, where to put it, and how to measure whether it did anything. I have also included an honest section on who should ignore this entirely, because for a lot of my clients the answer is "not yet."

Preferred Sources started as a Search Labs experiment in mid 2025, launched properly for English users in the US and India in August 2025, and went global in every language Google Search supports earlier this year. The reader-facing part is simple. A signed-in user opens Google's source preferences tool, searches for a publication, and ticks it. From then on, that publisher's fresh, relevant articles get shown more prominently in Top Stories for that user, marked with a small "preferred" badge.

What changed in 2026 is the reach. Google's documentation now says the same badge can appear in AI Mode and AI Overviews for users who selected your site. So a reader who prefers you does not just see you more in the news box. They see you flagged inside the AI answer itself.

Three things to be clear about before you get excited:

• It is per reader. One person selecting you changes one person's results. There is no aggregate score you can farm by getting a thousand clicks.
• It only fires where Top Stories, AI Overviews or AI Mode fire. Standard blue links, Shopping, Images and your service pages are untouched.
• It sits alongside ranking, not above it. Google's wording is that it works with its ranking systems. You still need a fresh, relevant article for the query, or there is nothing to badge.

Before you touch code, find out if readers can even select you. Only domain-level and subdomain-level sites appear in the tool. Google's own examples: example.com and code.example.com qualify, example.com/blog does not. If your news content lives in a subfolder of a brochure site, the whole domain is the unit, not the folder.

If your site is missing from the tool, it almost always comes down to one of these:

• You have never appeared in Top Stories, so Google does not treat the domain as a news source
• Your content is evergreen: guides and service pages with no dated, timely articles
• Articles have no clear byline, no visible publish date, or the date changes on every edit
• No news sitemap, or the sitemap only lists pages older than 2 days
• Bot protection or a paywall that serves Googlebot a blank page
• You are checking a subfolder or a country path, not the root domain

None of these have a shortcut. The only route into the tool is the route into Top Stories: publish original, dated, bylined reporting or analysis on a regular cadence, keep it crawlable, and give Google a reason to treat the domain as a publication rather than a brochure. Google's Discover and Top Stories guidance is the same checklist and I have linked it in the sources.

This is the part that changed on 20 August. Before, a reader who wanted to prefer you had to leave your article, find Google's tool, search for you and tick a box. Almost nobody did that unprompted. Now the whole flow happens in a small overlay and the reader is returned to your page. Google says the button is automatically translated into the reader's language and can be styled light or dark.

Put this in your <head>:

<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>

Then place this wherever you want the button to render. On a dark site like mine, set the theme, and pin the language if your readers are not all on the same browser locale:

<div google-add-preferred-source-btn data-theme="dark" data-lang="en"></div>

That is the whole standard implementation. It reads your domain from the page, so there is no publisher ID to paste and nothing to configure per article. Here it is live on this page:

Two implementation notes from putting this on client sites. First, load the script once. If your theme, a plugin and Tag Manager all inject it, you get duplicate overlays. Second, the script comes from a Google domain, so add it to your privacy and consent review the same way you would any third-party embed. If you need the button to fire from your own designed element instead of Google's, the documentation has an advanced mode with preferred-sources-control="manual" and a callback queue. Most sites do not need it.

The button only works on pages you control that can run a script. Your newsletter, your LinkedIn bio, your email signature, a Substack, a partner's site: none of those can. For those, Google provides a plain URL that opens the source tool with your site already searched:

https://www.google.com/preferences/source?q=yourdomain.com

As a text link it looks like this:

<a href="https://www.google.com/preferences/source?q=yourdomain.com">
  Add us as a Preferred Source on Google
</a>

The trade-off is friction. With the deeplink the reader still has to confirm inside Google's tool and does not get sent back to you, so use the button on your own pages and save the deeplink for channels where the button cannot exist. Google also ships official badge graphics in 16 languages if you want an image instead of text.

A button nobody sees does nothing. A button in the wrong place gets ignored. Having watched how these perform, the ranking is simple: ask after the reader has received value, not before.

• End of article, above the comments and related posts. This is the recommended spot and the one I default to. The reader just finished something useful. That is when they will say yes.
• Author box. Works well for publications built around bylines, because the ask comes from a person.
• Post-subscribe or thank-you screen. Second highest intent moment on the site.
• Sticky footer on mobile, only if it is small. Test it. On some sites it costs more scroll depth than it earns.
• Not in the header, not in a popup on entry. The reader has no reason to trust you yet, and an interstitial that fires on arrival is a page experience problem on top of a wasted ask.

The copy next to the button matters as much as the placement. Readers do not know what the feature is, so one plain sentence beats a clever one:

One rule I hold clients to: never write copy that implies the click changes how everyone sees you. It does not. "Help us rank higher" is inaccurate, and the moment a reader realises that, the trust you were trying to build goes the other way.

Here is the awkward part. Google does not report how many readers have selected you. Search Console has no Preferred Sources column. What you can measure is the action on your side and the surfaces it should influence.

Track the click. Wrap the button container in a listener that fires a GA4 event, so you at least know how many readers are attempting it:

document.addEventListener('click', function(e){
  if (e.target.closest('[google-add-preferred-source-btn]')) {
    gtag('event', 'preferred_source_click', {
      page_location: location.href
    });
  }
});

Then watch the surfaces. In Search Console, filter Performance by search appearance and look at Top Stories impressions and clicks over the 60 days after launch, against the 60 before. Do the same for the Discover report. Neither will isolate Preferred Sources cleanly, and anyone who tells you their tool can is guessing. What you are looking for is direction: a rise in Top Stories click-through for the same impression volume is the signal that your preferred readers are seeing you first and clicking.

Who should ignore this (for now)

I work mostly with clinics, law firms, insurance brokers and SaaS companies. For most of them, my advice on Preferred Sources is: not yet.

A dental practice with 12 evergreen service pages and a blog post every 2 months will not appear in the source preferences tool, because it never appears in Top Stories. Adding the button changes nothing. The same is true for most local service businesses, most agencies and most product-led SaaS sites. Top Stories does not fire for "dentist near me" or "best CRM for law firms," so there is nothing to badge.

Where it does apply outside news: a law firm that publishes same-day analysis of regulatory changes in its practice area. A healthcare group with a real newsroom covering policy and research. A SaaS company that runs an industry news desk, not just a product blog. An agency like mine that covers AI search updates as they land. If your editorial calendar has a "this week" column, you are a candidate. If it does not, put the effort into answer engine readiness first, where the same hour of work moves the needle for every reader, not just the ones who clicked a button.

What I would do this month

Google has reported over 600,000 unique sources selected by readers so far, up sharply since the button shipped. Every one of those was a reader choosing a publisher over the algorithm. The feature is small, the effect is per person, and it will not save a site that has nothing fresh to say. But for a publication with a loyal audience, it is the rare Google feature where the people who already like you get to tell Google so, and Google listens.

If you want me to check your eligibility and set this up alongside your AI search work, start with a free AI SEO audit or email hello@anshulrana.in. And if you are still working out where this sits next to AEO and GEO, the plain-language version is in SEO vs AEO vs GEO: what is the difference.

Frequently Asked Questions

Sources

1. Google Search Central: Help your readers find your site through preferred sources (updated 10 September 2026)
2. Google: How to select your preferred sources in Top Stories in Search
3. Search Engine Journal: Google's Preferred Sources is now a global signal
4. Press Gazette: One-click link in articles adds publishers to users' preferred sources
5. Google Search Central: Google Discover and your website

Anshul Rana

SEO, AEO & GEO Specialist · Top Rated Plus on Upwork

I'm an SEO, AEO, and GEO specialist with 8+ years of experience helping businesses get found on Google and AI search platforms like ChatGPT, Claude, Gemini, and Perplexity. I hold the Top Rated Plus badge on Upwork (top 3% of freelancers) with a 100% Job Success Score, and I have worked with 1,000+ websites across India, Australia, the US, and the UK. I specialize in technical SEO, answer engine optimization, generative engine optimization, schema markup, and local SEO.

Website Upwork LinkedIn The Digital Geek

Related Articles