Google's Search Console still has no report for this, so most teams will not notice it happened. In August 2025, Google launched Preferred Sources: a way for readers to pick the news sites they trust and see more from them in Top Stories. Fifteen months later, Google quietly extended the same badge into AI Mode and AI Overviews, per its own developer documentation. A reader who has picked your site can now see a "preferred" marker next to your content inside an AI-generated answer, not just in the news carousel.
That is a specific, low-effort lever for AI visibility that almost nobody has set up, because almost nobody has heard it reached AI Mode. Here is what the feature actually does, who qualifies, exactly how to add the button, and why it will not fix a site that AI Overviews already ignores.
Key takeaways
- Google's Preferred Sources feature, originally limited to the Top Stories carousel, now also shows a "preferred" badge inside AI Mode and AI Overviews.
- Qualifying needs two things: your domain or subdomain listed in Google's source preferences tool, and your Search Console "Search generative AI" control left on include.
- Setup for readers is a two-line HTML snippet (a script tag plus a button), or a plain link for sites that cannot run JavaScript.
- The badge is not a ranking factor and not a guarantee. Google's own wording is "more likely to appear," never "will appear."
- Subdirectories do not qualify. Only full domains and subdomains do.
What is Google's Preferred Sources feature?
Preferred Sources is a Google Search setting that lets a reader pick specific publishers they want to see more of, then follows through on that choice across Search surfaces. Google's own developer documentation describes it plainly: 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, and the same badge can now appear in AI Mode and AI Overviews for users who picked you. Readers choose sources through Google's source preferences tool, and there is no cap on how many they can pick. For a publisher, this is the first mechanism Google has shipped that lets an individual reader's standing preference, not just that day's query, shape whether your content gets surfaced again. It sits next to your existing SEO work rather than replacing it: a site still has to earn inclusion in AI Overviews on the merits before a badge has anything to attach to.
How did a Top Stories feature end up inside AI Mode?
Google built Preferred Sources for one surface and then carried the same mechanic into a second one as AI Mode and AI Overviews matured. The original 2025 launch was scoped to Top Stories: pick a source, see more of it in that carousel. Google's current developer guide confirms the feature now spans both products, stating the preferred badge is available "in all languages and locales" where AI Mode and AI Overviews themselves are offered, with one added condition specific to those surfaces: your site also has to be included in what Google calls Search generative AI features inside Search Console, a separate switch covered below.
Practically, this means a feature teams filed away in 2025 as "a Top Stories thing, not my problem" is now a live input into how AI-generated answers credit sources. Nothing changed about how to apply; what changed is the surface area the same application now reaches. A reader who picked your site for news is, without doing anything else, now a reader who may see your preferred badge inside an AI answer too.
| Where the badge appears | Launched | Reader action required |
|---|---|---|
| Top Stories | August 2025 | Selects your site in source preferences |
| AI Mode | Extended, per current Google documentation | Same selection, plus your site included in Search generative AI features |
| AI Overviews | Extended, per current Google documentation | Same selection, plus your site included in Search generative AI features |
Source: developers.google.com, Guide to Preferred Sources in Google Search for Web Publishers.
Does your site qualify as a preferred source?
You qualify if your domain or subdomain appears in Google's source preferences tool and your Search Console AI control is set to include your content; a subdirectory never qualifies on its own. Google's guide is specific that eligibility sits at the domain or subdomain level: www.example.com and code.example.com both work, but www.example.com/blog does not, no matter how much traffic that one folder gets. Check eligibility by typing your own domain into Google's source preferences tool, linked from the official Preferred Sources guide, and confirming it returns a result.
The second requirement is specific to AI Mode and AI Overviews and is easy to miss because it lives in a different settings screen. Google's own Search Console help page on the Search generative AI control describes a per-property setting, rolled out to every property worldwide by the end of August 2026. It defaults to "include my site's links and content in Search generative AI features," which is what you want here; the alternative is "exclude," which also pulls your content out of AI Overviews and AI Mode entirely and costs you the impressions and traffic that come with it. Open Search Console, go to Settings, and look for the Search generative AI entry to confirm which option is active on your property.
| Requirement | Where to check | What disqualifies you |
|---|---|---|
| Domain or subdomain listing | Google's source preferences tool | Only a subdirectory is indexed under a shared domain |
| Search generative AI control set to include | Search Console > Settings > Search generative AI | Control set to exclude, or inherited from a parent property that excludes |
| Readers actually select you | Not visible in Search Console yet | No readers have added you as a preferred source |
How do you add the "preferred source" button to your site?
The standard setup is two lines of HTML: a script tag in your page head and a button element wherever you want the prompt to appear. Google's documentation gives the exact markup: an async script loaded from news.google.com/swg/js/v1/publisher.js, plus a div carrying a google-add-preferred-source-btn attribute at the spot in your layout where the button should render. The async attribute matters here; per the MDN script element reference, an async script fetches and executes without blocking the rest of the page from parsing, so the button loads without slowing down your page's render. You can set data-theme to light or dark and data-lang to match your audience's language; by default the button follows the reader's browser language.
Two other paths exist for teams that need something different. Sites with more design control can skip the pre-built button and call preferredSource.init() and preferredSource.addPreferredSource() directly through an ES module import, wiring the prompt to a custom element or trigger. Sites that cannot run JavaScript at all, including some email newsletters and legacy CMS templates, can instead link straight to google.com/preferences/source?q=YourSiteURL as a plain text link or clickable badge image; Google provides the badge assets for this specifically so the feature does not require a script to work at all.
| Method | Best for | Effort |
|---|---|---|
| Standard button snippet | Most sites on a modern CMS or framework | Two lines of HTML, minutes |
| Advanced JS module | Sites with custom design systems or non-standard triggers | Developer time, same day |
| Plain deeplink or badge image | Sites that cannot run JavaScript, including some newsletters | One link, minutes |
If you are running an AI visibility audit anyway, this is a good moment to check whether your site is set up to be found by AI agents and crawlers in the first place; Faro's AI visibility checker flags that alongside dozens of other agent-readiness checks in one pass.
Does the badge guarantee you show up in AI Overviews?
No. Google's own documentation never promises inclusion; it says a preferred source is "more likely to appear," and it states explicitly that the promotional button and deeplink methods are not required for appearing as a preferred source in the first place. Nothing in Google's guide describes Preferred Sources as a ranking factor, and the company has not published any claim that it influences which pages AI Overviews chooses to cite. What it changes is emphasis among sources Google has already decided are eligible to cite, not the eligibility decision itself.
That distinction matters because of what Faro has written about AI visibility before: citation and traffic are not the same thing, and a badge is not revenue. If your content is not getting picked up by AI Overviews or AI Mode at all today, a preferred badge has nothing to attach to, and proving that AI visibility actually drives revenue still requires tracking clicks and conversions, not just impressions of a badge.
Why this matters even if you already appear in AI Overviews
Showing up in an AI answer once says nothing about whether you will show up the next time the same question gets asked, and Preferred Sources is one of the few levers that pushes toward consistency instead of a single lucky citation. Readers who pick you as a preferred source are telling Google, on a standing basis, that your domain belongs in their results; that is a different signal than ranking well for one query on one day. It is also a signal Search Console still will not show you directly. Google Search Console's AI report covers impressions and clicks from AI features, but nothing in it currently breaks out preferred-source selections, so you are checking the source preferences tool and the generative AI control manually, not reading it off a dashboard.
It is also worth tracking separately from citation monitoring generally, because the two measure different things. Tracking how ChatGPT, Claude, and Perplexity cite you tells you whether AI engines mention your brand at all; Preferred Sources is Google-specific and tells you whether readers who already found you are choosing to keep seeing you. A brand can be well cited and still have zero readers who bothered to add it as a preferred source, which is its own kind of gap if you are trying to track which companies AI recommends instead of you over time.
What should you actually do this week?
Confirm eligibility before building anything: search your domain in Google's source preferences tool, then check the Search generative AI control in Search Console and make sure it is set to include, not inherited from a parent property that excludes you. Once both are confirmed, add the two-line button snippet to your highest-traffic pages first, pick the deeplink option if your platform cannot run the script, and set a reminder to recheck the generative AI control after any site migration, since inherited settings on new subdomains default to following the parent property and can silently flip you out.
None of this replaces the work of actually being citable. A badge only matters on content Google already considers worth citing, which is the same bar Faro's audits measure directly: whether your site is structured, crawlable, and readable enough for an AI agent to use it as a source at all.
Run Faro's AI citation monitor to see whether your brand is actually showing up across AI engines today, then come back and add the preferred source button once you know the citations are there to reinforce.
FAQ
What is a Google preferred source?
It is a site a reader has explicitly picked to see more of, using Google's source preferences tool. Once picked, that site is more likely to appear with a "preferred" badge in Top Stories, AI Mode, and AI Overviews for that reader specifically.
How do I become a Google preferred source?
Confirm your domain or subdomain appears in Google's source preferences tool, keep your Search Console "Search generative AI" control set to include, and add the two-line button snippet (or a plain deeplink) so readers can select you. Readers do the actual picking; you cannot opt yourself in directly.
Does the preferred badge work for ChatGPT or Perplexity too?
No. Preferred Sources is a Google-specific feature tied to Google Search, AI Mode, and AI Overviews. It has no equivalent inside ChatGPT, Claude, or Perplexity, which select and credit sources through their own separate mechanisms.
Is the preferred source badge a Google ranking factor?
Google's own documentation does not describe it as one. It affects whether a badge appears next to content a reader has already chosen to see more of; it is not described as changing whether that content ranks or gets selected for Search in the first place.
Can a blog subdirectory qualify as a preferred source?
No. Eligibility is set at the domain or subdomain level only. A subdirectory such as example.com/blog is not eligible on its own, even if that section is the part readers actually want to follow.
I already show up in AI Overviews. Do I need to do anything here?
Appearing in AI Overviews and appearing as a preferred source are separate things. Being cited does not add you to any reader's preferred list automatically; readers still have to actively select your domain, so the button or deeplink is worth adding even on a site that already gets cited regularly.
In short
Google's Preferred Sources feature started in Top Stories in 2025 and now also shows a "preferred" badge inside AI Mode and AI Overviews, per Google's current developer documentation. Qualifying takes a domain-level listing in the source preferences tool and an "include" setting on the Search generative AI control in Search Console; adding the button itself is two lines of HTML or a plain link. None of it is a ranking factor or a guarantee, and it only matters on content that was already citable in the first place. Treat it as a small, specific addition to an AI visibility checklist, not a replacement for the underlying work of being findable and citable.