Google Preferred Sources is not a badge Google awards you

By Michael Obraitis, Managing Partner, and Michael Dale, CEO · Published August 27, 2026 · Last reviewed August 2026 · ADAM Pulse Knowledge Base

Short answer

Preferred Sources is a user-controlled Search personalization feature. It is not a Google-awarded publisher badge, not a classic ranking factor, and not a PageRank successor.

A reader signed in to a Google Account adds websites they want to see more of. Google then makes that site more likely to appear in Top Stories for that user, with a “preferred” badge, when the site has fresh, relevant content for the query. The same sources can be highlighted with a “preferred” badge inside AI Overviews and AI Mode for that user, in locales where those AI features exist.

Publishers do not apply, pay, or get nominated. There is no publisher submission form. Eligibility is automatic: the domain or subdomain must appear in Google’s source preferences tool, which Google ties to fresh content. Subdirectories cannot be preferred on their own.

A publisher’s job is not to “get listed by Google.” It is to publish fresh, crawlable content so the host appears in the picker, then ask existing readers to add the site with Google’s official button, SDK, or deeplink.

As of 27 August 2026 the product is rolled out globally for Top Stories in all languages where Google Search is available. The AI-surface badge follows AI Overviews and AI Mode availability. It is not US-only and it is no longer a Labs-only experiment. The embeddable interactive publisher button that returns the reader to the page shipped 20 August 2026.

This article does not claim that kb.adampulse.us or adampulse.us currently appears in the picker. That check has to be done live in Google’s tool.

What Preferred Sources actually is

Google’s own picture, as of 27 August 2026:

Search Central’s publisher guide is the precise wording to keep: in Top Stories, content is more likely to appear and is highlighted with a “preferred” badge. In AI Mode and AI Overviews, content can be highlighted with a “preferred” badge for users who selected the site. “Can be” is not “will always be cited as the grounding source.”

The 12 August 2025 launch blog adds that selected sources appear more frequently in Top Stories or in a dedicated “From your sources” section, that users still see content from other sites, and that the effect applies when those sources have published fresh and relevant content for the search. The 27 May 2026 Search blog says that for some developing-topic queries, a prominent article carousel also highlights Preferred Sources.

What is not documented as a Preferred Sources badge surface: classic organic “10 blue links” ranking for users who did not opt in; the Google Discover feed; Google News app audio briefings. Discover still has its own personalization language. Google announced separate Discover topic-tuning and Google News Android audio-briefing controls on 20 August 2026. Those are sibling features, not this badge.

Who chooses

There are two different jobs, and mixing them up is how the “Google awarded us a badge” story gets written.

Readers choose. Google Search Help documents the flow on google.com and in the Google app: profile → Search personalization → Source preferences. Users can also use the star/cards control next to Top Stories. Users can select as many sources as they like. The August 2025 launch blog said over half of early Labs users chose four or more. Preference is not an exclusive filter: other sites still appear. If the user is signed in when they save, settings persist across browsers they sign into.

Publishers do not apply. Google does not publish a Preferred Sources application, review, or badge-award process. What a publisher can do, only if the site already appears in the picker, is ask people who already read the site to add it: official interactive button, advanced JavaScript SDK with custom UI, or a deeplink to https://www.google.com/preferences/source?q=YOUR_DOMAIN.

The “preferred” badge then shows for users who selected the site, on the surfaces above. It is not a sitewide Google endorsement visible to all searchers.

What Google has actually claimed as a benefit

Repeat only what Google published, with the date. Do not treat any of this as an ADAM Pulse measurement.

John Mueller, via Search Engine Journal reporting of a Bluesky reply, restated the Search Central wording and added that it does not make sense to show spam to users just because of a preference, while it does help a user see preferred sources more. Treat that as spokesperson clarification, not a ranking-systems white paper. Google has not published weights.

Eligibility and the picker test

Google’s published eligibility rules are short:

1. Any website that publishes fresh content is eligible (27 May 2026 Search blog). Launch examples included a sports blog and a local news outlet, not only major newsrooms.
2. Only domain-level and subdomain-level sites can appear in the source preferences tool (Search Central). Subdirectories are ineligible as their own source.
3. Sources that aren’t updated regularly may not be available in the picker (Google Search Help).
4. Practical test Google tells publishers to use: enter the site in the source preferences tool search box. If it appears, you can promote the button or deeplink. If it does not, Google has not listed an application form to force inclusion.

Open:

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

Replace YOUR_DOMAIN with the exact host you want readers to add. Check the canonical publishing host, not a path. A knowledge-base subdomain can be a preferred source independently of the apex domain if it appears in the picker. A path such as example.com/kb/ cannot. Google has not documented cross-host inheritance, so treat www versus apex, and each subdomain, as its own check.

This page does not assert that kb.adampulse.us currently appears in that tool. If a host does not appear, do not promise a badge. Work on freshness and indexability, then re-check.

There is no published requirement that the site be in Google Publisher Center, be a Google News “publication,” use a News sitemap, use the Indexing API, use llms.txt, or use any special schema.org type for Preferred Sources. Those things may still help discovery, News, or rich results. They are not stated as Preferred Sources admission criteria. Google’s generative AI optimization guide states that Search does not use llms.txt, and that structured data is not required for generative AI Search. The Indexing API remains limited to JobPosting and BroadcastEvent-in-VideoObject pages.

How a reader adds a preferred source

From Google Search Help:

Path A — Search personalization

1. Go to google.com or open the Google app.
2. Profile picture or initial → Search personalization → Source preferences.
3. Search for sources.
4. Check the box. “Your sources” appear at the bottom.

Path B — From Top Stories

1. Search for a recent significant news topic so Top Stories appears.
2. Click the cards/star control to the right of the Top Stories header.
3. Search, check sources, click Reload results.
4. Those sources then appear more often in Top Stories when they publish fresh content related to the search.

Selecting sources in one place also tailors Top Stories, AI Mode, and AI Overviews. Users still see other sites.

How a publisher asks readers to add the site

Do this only after the host appears in the picker. Canonical how-to: Guide to Preferred Sources in Google Search for Web Publishers (updated 20 August 2026 for the interactive button).

1. Official interactive button (recommended). Google recommends this path because it adds the site and returns the reader to the page.

Loader, preferably in <head>:

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

Button target, anywhere in the body:

<div google-add-preferred-source-btn></div>

Optional theme and language: data-theme="dark" or data-theme="light" (default is light); data-lang="en" overrides the browser language. Google publishes a language-code list on the same Search Central page.

The widget below is that official button on this article, as a how-to example — not a sitewide embed. It talks to the same picker. If the current host is not in the tool, the button does not create eligibility.

Advanced / custom UI: ES module at https://news.google.com/swg/js/v1/publisher.mjs with preferredSource.init({ theme, lang }) then preferredSource.addPreferredSource(). Classic script: add preferred-sources-control="manual" on the script tag so it does not auto-render, then use the PREFERRED_SOURCE callback queue. Search Central also links a live demo from that page.

If the site uses a strict Content Security Policy, allow the script from https://news.google.com (and whatever origins the library calls). Google’s docs do not publish a CSP snippet.

2. Deeplink for email, social, and no-JS CMS pages:

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

Example markup:

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

Google also allows a clickable image using your artwork or official translated graphic assets downloaded from the same Search Central page. Use the deeplink in newsletters and social posts; the JavaScript button cannot run there.

3. Ask people who already trust you. Google’s publisher framing is audience connection, not acquisition from cold SERPs. Practical placements that match that: article footer, an about or updates page, an email newsletter (deeplink). Do not claim “Google certified us” or “this boosts your Google rank.”

Google has not published a Search Console report titled “Preferred Sources.” Measure proxies: the generative AI performance report, Discover performance (Discover is a separate product), Top Stories appearance for opted-in test accounts, and on-site button or deeplink clicks. That last one is opt-in volume, not ranking.

Current status (timeline Google dated)

Google’s dated launch post is the 12 August 2025 graduation. Industry write-ups often place the Labs experiment around late June 2025; this article uses Google’s own dated post rather than freezing an unverified first Labs day.

Misconceptions

Frequently asked questions

Related articles

• What happens when your next customer asks AI who to hire? — AI Overview citation is a different problem from a user-managed preferred label.
• What does AI data governance actually require in 2026? — the governance layer around how AI systems use your public content.

References

Primary Google documentation and product blogs. Where Google has not published a claim — picker appearance for any ADAM Pulse host, ranking weights, Discover badge, or click-through methodology — this article says so rather than filling the gap.

1. Google Search Central — Guide to Preferred Sources in Google Search for Web Publishers— canonical publisher how-to. Product purpose; Top Stories “more likely” plus preferred badge; AI Mode / AI Overviews badge; global Top Stories availability in all Search languages; domain/subdomain-only eligibility; picker check; standard JS button (publisher.js, google-add-preferred-source-btn, theme/lang); advanced ESM/IIFE SDK; deeplink URL format; return-to-page UX. Updated 20 August 2026 for the interactive button. Does not document a Discover badge, Publisher Center admission, News sitemap, Indexing API, ranking weights, or organic ranking for non-opted-in users.
2. Google Search Central — Latest Google Search documentation updates— changelog dates: 30 January 2026 docs added; 30 April 2026 all-language expansion; 27 May 2026 AI Mode/AI Overviews starting to roll out; 20 August 2026 interactive button; 15 June 2026 llms.txt unused by Search; 19 November 2025 Discover Follow feature removed from Discover docs.
3. Google Search Help — Preferred Sources in Google Search— user how-to (desktop and Google app); Source preferences; Top Stories star/cards control; sources not updated regularly may not be available; signed-in settings persist; selecting sources tailors Top Stories and AI Mode / AI Overviews.
4. Google Search blog — How to select your preferred sources in Top Stories in Search (Duncan Osborn, 12 August 2025)— US and India launch; Top Stories; “From your sources”; Labs users carry over; more than half of early Labs users chose four or more sources; users still see other sites; sports blogs and local news as examples.
5. Google Search blog — New opportunities for a thriving web ecosystem (10 December 2025)— about 90,000 unique sources; twice as many clicks on average; English global expansion plan.
6. Google blog — Preferred Sources expands worldwide in English (16 December 2025)— English worldwide live; other languages early next year; same 90,000 / 2× figures.
7. Google Search blog — Preferred Sources is now available in all languages (30 April 2026)— all supported languages; 200,000+ unique sites; 2× click-through claim; star icon next to Top Stories.
8. Google Search blog — How Google Search helps you find original, quality content (Duncan Osborn, 27 May 2026)— AI Overviews and AI Mode; labeled like Top Stories; source preferences in Search personalization; any website that publishes fresh content; 2× click-through; 345,000+ unique sources; developing-topic carousel; Highly Cited is a different label.
9. Google Search blog — Personalize the content you see on Search, Discover, and News (Mrinalini Loew, 20 August 2026)— interactive publisher button; return to page; 600,000+ unique sources; Top Stories / AI Overviews / AI Mode; points publishers to Search Central. Discover free-text controls and News Android audio topics are sibling personalization features, not the same badge.
10. Google Search Central — Optimizing for generative AI features— generative AI uses core ranking; llms.txt not used by Search; structured data not required for generative AI Search; spam policies still apply.