Search visibility is no longer only about asking, “Where does this page rank?” On August 20, 2026, Google announced a new interactive Preferred Sources button that publishers can embed on their own sites. When a reader selects a site as a preferred source, that publication may appear more often in Top Stories and can be highlighted with a preferred badge in AI Overviews and AI Mode.
The direction matters for brands: technical SEO still creates the foundation for discovery, while being deliberately chosen by the reader is becoming an additional distribution advantage. This guide explains how the feature works, who is eligible, the two-line implementation and a practical 30-day plan.
Short answer: Preferred Sources does not replace conventional SEO and does not guarantee rankings. It adds a personalized visibility layer that connects crawlable, trustworthy, original content with audience loyalty.
What is Google Preferred Sources?
Preferred Sources is a personalization feature that lets people explicitly tell Google which publications they want to follow. According to Google's official documentation, content from a selected source is more likely to appear in Top Stories and may receive a preferred badge. Preferred badges can also appear in AI Mode and AI Overviews where those experiences are available.
In its August 20 announcement, Google said people had already selected more than 600,000 unique sources. The new button lets a publisher start that preference flow from its own page and return the reader to where they left off after the selection.
Three important limitations
- It is user-specific: A person's choice affects that person's experience; it is not a universal ranking boost.
- Eligibility must be checked: Before adding the button, confirm that your site appears in Google's source preferences tool.
- It works at domain level:
example.comornews.example.commay be eligible, butexample.com/blogcannot be selected as a separate source.
Why does it matter now?
AI-powered search is moving beyond a page of ranked links toward systems that explore sub-questions, combine sources and produce conversational answers. Visibility in that environment develops across three layers:
- Accessibility: Can the search engine crawl, understand and index the page?
- Selectability: Is the content original, credible and clear enough to answer a specific question?
- Preference: Does the reader recognize the source, trust it and want to see it again?
Traditional SEO is strongest in the first two layers. The third connects brand demand, community and retention more directly with search. Preferred Sources is therefore better understood not as a small technical widget, but as a bridge between SEO and audience relationship management.
Google's current generative AI search guide recommends focusing on valuable, non-commodity content, a clear technical structure and established SEO fundamentals instead of looking for a separate GEO trick. For the broader shift in search behaviour, read our Google AI Mode and SEO guide.
How do you add the Preferred Sources button?
Google's recommended standard implementation has two parts. First, load the publisher library, preferably in the page <head>:
<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>
Then add the following container wherever the button should appear:
<div google-add-preferred-source-btn data-theme="dark"></div>
The standard button automatically localizes to the browser language and supports light or dark themes. If your CMS cannot load the JavaScript, Google also documents a deeplink alternative that opens the source preferences page. Before implementation, verify that your site can be found in the source preferences tool.
A seven-step strategy for AI search visibility
1. Fix indexability and technical structure first
A preference button cannot surface a page Google cannot access. Canonical URLs, XML sitemaps, correct status codes, mobile usability, secure HTTPS, Core Web Vitals and clean internal links remain essential. Important content should not exist only after an interaction; the title, author, date and primary copy should be clear in the HTML.
2. Publish first-hand experience instead of commodity content
AI systems can already synthesize common knowledge. A defensible content advantage comes from project data, original tests, recurring customer questions, proprietary comparisons, useful screenshots and named expert analysis. If an article offers no decision support that readers cannot find elsewhere, adding more words alone will not create durable visibility.
3. Answer questions clearly with a natural hierarchy
Each main section should resolve a specific reader question. Use descriptive H2 and H3 headings, concise definitions, lists or tables when they genuinely clarify the topic, and links that support factual claims. Do not split copy into artificial fragments simply to make every paragraph look “citation-ready.” Good user experience remains the priority.
4. Make the source identity visible
Show the author and relevant expertise, publication and update dates, clear contact details, an about page and an editorial policy. On the technical side, Article or BlogPosting and Organization structured data, a consistent site name, a correct og:image and descriptive image alt text clarify context. Structured data is not a ranking guarantee; it makes real page information easier for machines to interpret.
5. Ask for preference at the right moment
Instead of hiding the button only in the footer, place it after the reader has received value: at the end of an article, after newsletter confirmation or on a topic-series page. The surrounding copy should explain the outcome honestly: “See more from this source on Google.” Avoid implying that a click directly boosts your universal ranking.
6. Build topic clusters, not isolated posts
Support a flagship guide with case studies, Q&A pages, comparisons and timely updates. Connect them with descriptive internal links. This helps both the audience and search systems understand where the brand has real depth. Updating a proven resource with new evidence is often more valuable than publishing another shallow post from scratch.
7. Measure AI visibility separately
In June 2026, Google began testing dedicated Search Console performance reports for AI Overviews, AI Mode and generative AI features in Discover with a subset of sites. According to the official announcement, these reports include impressions, visible pages, countries, devices and dates.
If the report is not available in your account yet, monitor a combined set of indicators: branded searches, returning visitors, newsletter sign-ups, organic landing pages, impressions for relevant queries and content-assisted conversions. You may not receive a direct count of every source preference, so measuring button clicks as an event in your own analytics setup is also useful.
Common mistakes
- Treating the button as a ranking hack: User preference personalizes an experience; it does not automatically make weak content authoritative.
- Integrating before checking eligibility: If the domain is absent from the source preferences tool, the flow may not work as expected.
- Treating a subdirectory as a separate publication: A
/blogfolder alone is not an eligible source; a domain or subdomain is required. - Overinvesting in GEO/AEO shortcuts: Google does not position artificial mentions, unnecessary content chunking or AI-only text files as substitutes for SEO fundamentals.
- Ignoring visual quality: Original, high-quality images improve clarity and selection across Search, Discover and social previews.
- Skipping measurement: Without event tracking, Search Console review and baseline metrics, you cannot separate the effect of the change.
A 30-day implementation plan
- Days 1–7: Audit indexation, canonicals, sitemap coverage, mobile performance, Article schema, authorship and dates. Check source preference eligibility.
- Days 8–14: Choose the three topics where your brand has the strongest expertise. Plan one flagship guide and two supporting assets for each, using original evidence or experience.
- Days 15–21: Add the Preferred Sources button to eligible pages. Align the message across newsletters, social channels and end-of-article calls to action.
- Days 22–30: Record baseline values for button clicks, branded queries, organic impressions, returning visitors and conversions. Establish a monthly content-update rhythm.
Conclusion: a new layer from SEO to brand preference
Google Preferred Sources does not mean SEO is over. It makes indexability, page experience, original expertise and a trustworthy source identity more valuable. The new element is that a loyal reader can turn preference into a visible signal within Search and AI answers.
The practical approach is to run three workstreams together: build a technically accessible website, publish content worth citing and give readers a clear way to choose the brand again. If you want to audit your website for AI search or build this system around your brand, explore WebWizz services or start your project.