Google Preferred Sources Button: A Publisher Guide

Google's Preferred Sources button lets eligible publishers ask readers to select their domain as a favored source. That preference can highlight the publisher in Top Stories, AI Mode, and AI Overviews for that user, but it does not guarantee ranking, inclusion, citations, or traffic.

Google documented a new interactive implementation on August 20, 2026. It gives publishers a direct way to turn an existing reader relationship into a persistent source preference without sending the reader through a disconnected setup flow. This guide explains what changed, how to implement the button, and how to measure it without confusing preference with organic authority.

What is the Google Preferred Sources button?

The Google Preferred Sources button is an official publisher control that opens Google's source-selection flow, lets a signed-in reader choose the current domain, and returns that reader to the page. Google recommends its JavaScript implementation because the badge is automatically localized and can adapt to light or dark themes (Google Search Central publisher guide).

The underlying preference is personal. It can make fresh, relevant content from a selected source more prominent for that user; it does not change how every searcher sees the domain. Google's consumer documentation says source preferences can customize Top Stories, AI Mode, and AI Overviews, while its publisher documentation says selected sources may receive a visible "Preferred" badge in those experiences (Google Search Help).

This makes the feature useful at the intersection of SEO, audience retention, and AI visibility. It is closer to a follow or subscription signal than a new ranking factor that can be optimized at scale.

What changed on August 20, 2026?

Google added a custom interactive button workflow to its publisher guidance on August 20, 2026. The change introduced declarative and programmatic JavaScript options that can start the preference flow and then bring the user back to the page where they clicked (Google Search documentation updates).

Preferred-source eligibility does not repair a generic icon beside ordinary results. Audit that separate search-appearance signal with the Google favicon SEO guide, which follows Google's August 2026 format clarification and crawler requirements.

Preferred Sources itself is not brand new. Google expanded the feature globally across supported Search languages in April 2026. In May, Google extended preferred-source labeling into AI Mode and AI Overviews, not only Top Stories. Google reported that users were twice as likely to click through to a site after selecting it as a preferred source; that is Google's aggregate product finding, not a guaranteed uplift for any individual publisher (Google global expansion announcement).

The August update matters because it shortens the activation path. A reader no longer needs to remember a publisher's name, open Search personalization later, and find the right domain manually. The site can place the official control next to a newsletter, follow, or sharing action at a moment when trust already exists.

Where can a preferred source appear?

Google currently describes three relevant surfaces. Availability still depends on whether the feature itself is offered in the user's language, locale, and account.

Google surface	What the preference can do	What it does not prove
Top Stories	Show more fresh, relevant stories from the selected source and label them as preferred	Guaranteed placement for every news query
AI Mode	Highlight links from a selected source inside an AI response	A universal citation or ranking boost
AI Overviews	Mark links from a selected source when they are used in an overview	That every page on the domain is eligible or authoritative

Google says domain-level and subdomain-level publications are eligible for the source preferences tool, while a subdirectory such as example.com/blog is not a separate eligible source. It also warns that sources that are not updated regularly may not be available in the selector (Google Search Central publisher guide).

For a SaaS company with a blog, that creates an important operational requirement: treat the whole domain as the source. Keep the brand, editorial identity, authorship, and publishing cadence consistent across the site instead of trying to register one content folder as a standalone publication.

How do you add the standard button?

The fastest implementation uses Google's hosted publisher library and one declarative element. Add the script once, preferably in the document head, then place the button where it has editorial context:

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

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

The library scans for elements with the google-add-preferred-source-btn attribute and renders the official badge. You can set data-theme to light or dark. The badge normally follows the visitor's browser language; data-lang="en" can override it when a page requires a fixed language. These attributes and the hosted script URL come directly from Google's implementation reference (Google Search Central publisher guide).

Before deploying it everywhere, complete this checklist:

1. Confirm eligibility. Search for the exact domain in Google's source preferences tool.
2. Load the script once. Avoid adding the same external library through multiple components or tag managers.
3. Match the theme. Check contrast and focus visibility in both site themes.
4. Place it after value is delivered. An article footer, author area, or newsletter block is usually more credible than a disruptive entrance modal.
5. Test the full return flow. Use signed-in and signed-out sessions on desktop and mobile.
6. Review consent and CSP rules. The control loads code from a Google domain, so include it in the site's privacy and security review.
7. Keep a fallback link. A deeplink works when JavaScript is blocked or the CMS cannot run the interactive control.

When should you use the advanced JavaScript option?

Use the advanced implementation only when the standard badge cannot fit the interaction model. Google documents both an ES module and a callback-queue pattern. Each initializes the same preferred-source client and calls addPreferredSource() from a custom control.

That flexibility is useful for a design system, a post-reading milestone, or a product interface where third-party automatic rendering is undesirable. It also creates more implementation responsibility. Your custom button must still be accessible, clearly labeled, and visually distinct from an internal follow action. Do not make a selection look automatic or imply that clicking guarantees better Google rankings.

When JavaScript is impractical, Google provides a simple deeplink format:

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

Replace example.com with the eligible domain. The same link can be used in newsletters and social posts, which makes it the most portable option for testing audience interest before committing engineering time.

Where should publishers place the CTA?

The best placement is where the reader has enough evidence to decide that the publication is worth following. That usually means after an original article, inside a compact newsletter module, or on an editorial hub. Avoid placing it beside a primary conversion CTA if the two controls compete for attention.

A sensible rollout has three placements:

• Article footer: captures readers who completed a useful guide.
• Blog or research hub: reaches repeat readers already exploring the topic cluster.
• Email newsletter: uses the deeplink to reconnect an owned audience with Google Search.

Keep the copy precise: "Add GEOCARA as a preferred source on Google" is clearer than "Boost our rankings." The first describes the user action; the second makes a promise the feature does not support.

This CTA complements, rather than replaces, good information architecture. Build a coherent GEO topic hub, connect relevant guides, and make every important claim verifiable. The Google AI Mode optimization guide explains how query fan-out rewards complete topic coverage, while the AI Overviews guide covers eligibility and citation fundamentals.

How should you measure the result?

Measure the button as an audience feature first and an AI-search signal second. Google's public documentation does not promise a publisher-level count of people who selected a source, so do not invent a conversion number from Search Console impressions.

Track four evidence layers instead:

1. On-site engagement: button impressions, CTA clicks, placement, page, device, and returning-reader rate. Label this event as an attempted preference action, not a confirmed selection unless Google provides confirmation.
2. Search performance: branded queries, Top Stories exposure, landing-page impressions, clicks, and CTR in Search Console.
3. Generative search exposure: pages, countries, devices, and impressions in Search Console's Generative AI performance report where available.
4. Cross-engine visibility: repeated prompts, citations, mentions, and share of voice across Google, ChatGPT, Perplexity, Claude, and Copilot.

Use an annotation on the deployment date, then compare at least four weeks before and after while controlling for publishing volume and seasonality. A lift in one surface is correlation, not proof that the button caused it. For a defensible monitoring workflow, use the guide to tracking brand mentions and citations in AI engines and establish an on-site baseline with the free AI visibility checker.

What should publishers not expect?

Preferred Sources is not a shortcut around crawling, indexing, quality, or relevance. A selected domain can still publish a page that is stale, off-topic, inaccessible, or ineligible for a snippet. Google continues to select and organize results algorithmically, and the preference only applies to the individual who chose the source.

It also does not replace email subscriptions or direct audience relationships. Search preferences remain inside a third-party platform and can change with product availability. Keep building channels you control while using the button as a useful additional path.

Finally, do not treat the feature as evidence that Google endorses a publisher. The label reflects a user's explicit choice, not an independent quality certification.

FAQ

Does the Preferred Sources button improve Google rankings?

Google does not describe it as a general ranking boost. It personalizes selected Search experiences for the user who chose the source. Fresh, relevant content from that source can appear more prominently or carry a Preferred badge, but inclusion and placement remain algorithmic.

Can the button help visibility in AI Mode and AI Overviews?

Yes, for users who selected the source and where those features are available. Google says links from preferred sources can be highlighted in AI Mode and AI Overviews. That is personalized visibility, not a universal increase in citations.

Can I register only my blog subdirectory?

No. Google's publisher guide says eligibility works at the domain or subdomain level, not at the subdirectory level. news.example.com can be treated as a source; example.com/blog cannot be selected separately from example.com.

Does the button work without JavaScript?

The interactive badge requires Google's JavaScript library. Publishers that cannot load it can use Google's source-preferences deeplink as a text link or image link instead.

How can I see who selected my site?

Google's current publisher documentation does not expose individual selectors or promise a confirmed-selection report. Track CTA interactions in aggregate, respect user privacy, and measure downstream Search and AI visibility trends separately.

Sources

• Help your readers find your site through Preferred Sources - Google Search Central, updated August 20, 2026
• Latest Google Search documentation updates - Google Search Central
• Preferred Sources in Google Search - Google Search Help
• Preferred Sources is now available in all languages - Google, April 30, 2026
• New ways to find original content in AI Search - Google, May 27, 2026