Skip to content

Google Preferred Sources: the button, deep link and AI Mode

How Google Preferred Sources works in Top Stories, AI Overviews and AI Mode, who is eligible, and how to add Google's button or deep link to your site.

By Crawlito · 8 min read

In short

  • Preferred Sources lets a Google user pick sites they want to see more of; those sites can appear more often in Top Stories and carry a preferred badge there and in AI Mode and AI Overviews.
  • Only domain-level and subdomain-level sites are eligible, so www.example.com and code.example.com qualify but a subdirectory such as example.com/blog does not.
  • To be shown as a preferred source in AI Mode and AI Overviews, Google says the site must be included in Search generative AI features in Search Console.
  • Google offers a two-line JavaScript button and a deep link in the form google.com/preferences/source?q=example.com, and says neither is required to appear as a preferred source.
  • Google reports that people click through to a preferred source about twice as often, but it does not document Preferred Sources as a way to get into AI answers that would not otherwise include you.
On this page

Google Preferred Sources is a setting that lets each Google user choose the sites they want to see more of. When a reader picks your site, Google says your content is more likely to appear in Top Stories with a "preferred" badge, and in AI Mode and AI Overviews your links can carry the same badge for that reader. You can't opt your site in yourself. What you can do is make sure the site is eligible, then ask readers to choose you with Google's button or a deep link.

This post covers the parts Google documents for site owners: where the label appears, which sites are eligible, the button and deep link code, and the one Search Console setting that decides whether the badge can show in AI features. For how AI Mode and AI Overviews differ in general, see Google AI Mode vs AI Overviews.

What Google Preferred Sources does

The feature has grown in three steps, each announced on Google's blog:

DateWhat changedSource
12 August 2025Preferred Sources launched for Top Stories in the US and IndiaGoogle blog
10 December 2025Rollout to English-language users worldwide, with other languages to followGoogle blog
27 May 2026Preferred Sources brought to AI Overviews and AI ModeGoogle blog

At the time of writing, Google's Preferred Sources documentation says the Top Stories feature is available globally in all languages where Google Search is available, and that preferred sources can appear in AI Mode and AI Overviews in all languages and locales where those features are offered.

The effect differs by surface:

SurfaceWhat Google says happens for a reader who picked your site
Top StoriesYour content is more likely to appear, highlighted with a "preferred" badge. The launch post also mentions a "From your sources" section.
AI Overviews and AI ModeYour content can be highlighted with a "preferred" badge, so the reader can spot links from sources they chose
Link carousel on some developing-topic searchesThe May 2026 post says this new carousel in AI responses also highlights preferred sources

Note the wording for AI features. Google describes labelling links from preferred sources when they appear in a response. Its documentation does not say that choosing a source makes an AI Overview or AI Mode answer link to it when it otherwise would not, so don't plan around that.

Which sites are eligible

Google sets out three conditions.

The site must be a domain or a subdomain. Google's documentation says only domain-level and subdomain-level sites can appear in the source preferences tool. Its examples:

SiteEligible
https://www.example.com/Yes
https://code.example.com/Yes
https://www.example.com/blogNo, it is a subdirectory

If your news or blog content lives in a subdirectory, readers can only add the whole host. That's one more thing to weigh when you choose a structure; subdomain vs subdirectory for a blog covers the rest.

The site must publish fresh content. Google's May 2026 post says any website that publishes fresh content is eligible, and the Search Help page warns that sources that aren't updated regularly may not be available. Google publishes no frequency threshold.

For AI features, the site must be included in Search generative AI features. The documentation says that to be eligible for display as a preferred source in AI Mode and AI Overviews, your site must be included in Search generative AI features in Search Console. That points to the site-level control under Settings > Search generative AI. If a property is set to Exclude, or inherits Exclude from a parent property, the badge can't appear in AI features, because your links aren't shown there at all. The Search generative AI control explains the setting and how inheritance works. Top Stories is a separate surface, and Google lists no such condition for it.

How to check whether your site is listed

Google's instruction is simple: open the source preferences tool and type your site into its search box. If it shows up, readers can select it. If it doesn't, check the three conditions above. Google documents no form to request inclusion.

How readers add your site

You should know the reader's path, because it is what your button or link sends them into. The Search Help page describes two routes:

  1. From Search settings. On google.com or in the Google app, select the profile picture or initial, then Search personalization, then Source preferences. Search for a source and tick its checkbox. Chosen sites are listed under "Your sources".
  2. From Top Stories. On a computer, search for something that happened recently. When Top Stories appears, select the star icon to the right of its heading, search for sources, tick the checkbox and select Reload results.

The Help page notes that a choice made in either place applies to both Top Stories and AI Mode and AI Overviews. It also says that if the reader is signed in when they save, the setting stays the same in every browser they sign in to. The launch post says readers can choose as many sources as they like and change them at any time.

The Add to preferred sources button

Google calls this the recommended method. It is two lines of HTML that render a Google-styled, automatically translated button, which takes the reader through the flow and back to your page.

html
<!-- In the <head>: loads the preferred sources library -->
<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>

<!-- In the body, wherever the button should appear -->
<div google-add-preferred-source-btn></div>

Two optional attributes go on the div:

html
<!-- Dark theme (the default is light) -->
<div google-add-preferred-source-btn data-theme="dark"></div>

<!-- Force the button language instead of using the browser's -->
<div google-add-preferred-source-btn data-lang="en"></div>

Google publishes the list of supported language codes as a download on the same page.

Using your own button design

If you want the flow triggered by your own element, the advanced method loads the library without auto-rendering and gives you a preferredSource object. With a plain script tag, add preferred-sources-control="manual" and use the PREFERRED_SOURCE callback queue:

html
<script async preferred-sources-control="manual"
  src="https://news.google.com/swg/js/v1/publisher.js"></script>

<button id="myButton">Add us on Google</button>

<script>
  (self.PREFERRED_SOURCE = self.PREFERRED_SOURCE || []).push(
    function (preferredSource) {
      preferredSource.init({ theme: 'light', lang: 'en' });
      document.querySelector('#myButton').addEventListener('click', () => {
        preferredSource.addPreferredSource();
      });
    });
</script>

Google says that without the manual attribute, the library scans the page and renders a button in every element that has the google-add-preferred-source-btn attribute. For module-based builds, the same object can be imported from https://news.google.com/swg/js/v1/publisher.mjs. Google says both versions expose the same methods.

Practical checks before you ship the button

These checks aren't from Google's page. They're the usual checks for any third-party script:

  • Content Security Policy. If your site sends a Content-Security-Policy header, https://news.google.com must at least be allowed in script-src, or the script won't load. Google doesn't list the other origins the flow uses, so load the page with the browser console open to catch any other blocked requests.
  • Consent and privacy notices. The script loads from a Google domain, so check whether your consent banner or privacy policy has to mention it.
  • Placement. Put the button where a returning reader will see it, such as after an article or on the homepage. Avoid places that interrupt reading.

If your CMS won't take the script, Google documents a link straight to your entry in the source preferences tool. Replace example.com with your domain:

https://www.google.com/preferences/source?q=example.com
html
<a href="https://www.google.com/preferences/source?q=example.com">
  Add as Preferred Source
</a>

You can wrap an image in the same link. Google offers translated official button graphics as a download, or you can design your own badge. Because it is a plain URL, the deep link also works in places where a script can't run: newsletters, social posts and app screens. Google's examples use a bare domain. If your eligible site is a subdomain, open the link yourself first and check that it lands on the right entry.

What Google does and does not say about the effect

Google gives the same kind of figure in both posts. In December 2025 it said that when someone picks a preferred source, they click to that site twice as much on average; in May 2026 it said people are twice as likely to click through to a preferred source. In May 2026 it also said users had selected more than 345,000 unique sources, up from nearly 90,000 in December 2025. These are Google's own aggregate numbers. They are not a forecast for any one site.

What the documentation does not say, at the time of writing:

  • That being a preferred source changes ranking for people who have not chosen you.
  • That Search Console reports how many readers picked your site, or splits out clicks from preferred-source badges. No such report is documented.
  • That the button or deep link is needed. Google says they are optional ways to build your audience, not requirements.

So treat Preferred Sources as a way to keep loyal readers, not a way to get into AI answers. It rewards a site people already want to come back to. The groundwork for being shown at all is unchanged: the page must be indexed and eligible for a snippet, as covered in AI Overviews technical requirements. If you publish news, Google News inclusion and Publisher Center covers the related surfaces.

Frequently asked questions

Can I add my own site as a preferred source for everyone?

No. Each reader chooses their own sources. Site owners can only encourage readers with the button, a deep link or their own promotion.

Why can't I find my site in the source preferences tool?

Google says only domain-level and subdomain-level sites are eligible, and sources that aren't updated regularly may not be available. A subdirectory such as /blog can't be added on its own.

Does excluding my site from Search generative AI features affect Preferred Sources?

It affects the AI part of it. Google says a site must be included in Search generative AI features for the preferred badge to show in AI Mode and AI Overviews. Google lists no such condition for Top Stories.

Is the JavaScript button required?

No. Google says the button, the advanced implementation and the deep link are optional, and your site can appear as a preferred source without any of them.

Does Preferred Sources improve my rankings?

Google does not document any ranking effect for people who haven't chosen your site. Its published figure is that readers click through to their preferred sources about twice as often.

Make sure the basics are in place first

A reader who picks your site still only sees your links if Google can crawl and index the pages behind them. Run the free check on an important article to confirm crawlers can fetch it and that no noindex or snippet rule gets in the way. Then add the button.

Filed under Strategy and audits. Topics: google, ai-overviews, ai-search, content