For the last twenty years, almost every visibility discussion ran in one direction: the algorithm decides, the user consumes. With Preferred Sources, Google has reversed that direction in one specific place. Users can define in Google Search which sources they want to see preferentially, and Google aligns what it serves to exactly those users accordingly. Brands with a loyal readership can, for the first time, translate that loyalty into a documented serving signal.
What makes the feature interesting is the speed of its expansion. What began as personalization of Top Stories now reaches all the way into the generative surfaces of Search.
What Preferred Sources is — and how it has evolved
The principle is simple: a user marks a website as a preferred source. For that user, and only for that user, what gets served changes from then on. The documented evolution in three steps:
Google documents Preferred Sources, initially for Top Stories
The selection also takes effect in AI Overviews and AI Mode
Documented option of a dedicated button on your own website
For Top Stories, the feature is available globally, in every language in which Google Search is available. Only domains and subdomains are eligible — that is, example.com or code.example.com, but not subdirectories such as example.com/blog/. If you run your content in a directory of someone else's domain, you cannot offer a separate Preferred Sources selection for that section.
How it works — and how it does not
The documented effect: sources a user has marked as preferred are more likely to appear in Top Stories for that user. In addition, they are labeled there — as well as in AI Overviews and AI Mode — with a “Preferred” badge. So the brand does not just become visible more often; it is also flagged as a deliberate choice, right inside a generative answer that otherwise feels source-agnostic.
Just as important is what the feature does not do. There is no global ranking boost. One user's selection changes nothing about what other users see. Preferred Sources is personalization, not an authority metric. Anyone hoping to lift general rankings with a campaign for “more preferred markings” has misunderstood the mechanism.
“Preferred Sources is the newsletter subscription of the SERP: it wins no new readers, but it makes sure you no longer lose the ones you have — now also where the answer is written by an AI.”
On effect size, honesty is in order: Google publishes no numbers on how strong “more likely” turns out to be in practice. How often a preferred source additionally appears, and how much the badge changes click behavior, is unproven. Anyone introducing the feature should treat it as loyalty infrastructure with an open rate of return, not as a predictable traffic channel.
Implementation: two paths, one privacy trade-off
Google documents two ways to offer users the marking — the deep link and, since August 20, 2026, additionally a dedicated button. They differ less in function than in what they trigger under privacy law.
Path 1: The official button
Google provides a script that renders a ready-made button on your own website:
<!-- im <head> -->
<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>
<!-- im <body>, an der gewünschten Stelle -->
<div google-add-preferred-source-btn></div>The price: the page loads an external Google script from news.google.com. Data flows to Google the moment the page loads, regardless of whether the user ever touches the button. In most consent setups, an embed like this belongs in the category of third-party services requiring consent: load it only after consent, disclose it cleanly in the privacy policy. If you do not want to touch your consent management for this, do not choose this path.
Path 2: The deep link
The lean alternative is a normal link to the Google settings page:
https://www.google.com/preferences/source?q=ihredomain.deNo script, no third-party request on page load, no new consent category. The user clicks, lands in their own Google settings, and confirms the selection there themselves. From a GDPR perspective, this is the gentlest variant: data processing begins only through an active user decision, on Google's own interface.
Deep link first, button only with a consent setup
For most websites the order is clear: start with the deep link, because it works immediately and without legal side effects. The official button is worthwhile where well-maintained consent management exists and the visual prominence of a native button justifies the added complexity. Functionally, both paths lead to the same marking.
Who Preferred Sources pays off for
The feature rewards a specific form of relationship: returning readers who know a source by name and want to see it again. That yields an honest suitability list:
- Publishers and news outlets: the core case. Top Stories is the feature's native stage, and reader-brand loyalty is the business model.
- Specialist blogs and corporate content with frequency: if you publish regularly and have built a regular readership, you extend that bond into Search, including the generative surfaces.
- Brands with a community: newsletter subscribers, YouTube followers, and repeat customers are exactly the audience that sets such a marking without any persuasion.
- Pure service websites without content frequency: limited benefit. Where no new content appears on an ongoing basis, there is little that could be served preferentially. The implementation costs almost nothing, but you should also expect almost nothing from it.
Hands-on playbook: the link at your loyalty touchpoints
Preferred Sources only works when users actively mark. The task is therefore not a technical one but a communicative one: place the link where loyalty is already visible.
- Footer: the permanent, unobtrusive spot. A line like “Set as a preferred source on Google” is enough.
- End of article: anyone who has read to the end has proven interest. One sentence with the deep link directly before or next to the newsletter prompt.
- Newsletter: the densest loyalty audience there is. A one-time, clearly explained request reaches exactly the people who would agree anyway.
- About page: whoever visits it wants to place the brand. The link fits into the section that explains how to stay connected.
- Ask your community actively: do not just link — explain. Most users do not know the feature; a screenshot and two sentences on the effect increase the completion rate.
- Keep expectations realistic: no growth promises to your own team. The feature preserves reach among existing readers; winning new customers remains the job of other channels.
Self-application instead of theory
This website practices it: muratulusoy.de links the deep link in its footer (“Set as a preferred source on Google”) — deliberately in the script-free variant. No external Google script, no additional consent category, a normal link. Exactly the implementation this article recommends as the first step.
Context: loyalty becomes an AI signal
For the discipline of GEO, Preferred Sources is more than a personalization detail. It is one of the first features in which user loyalty directly influences AI serving: a human decision (“I want to see this source”) changes which sources a generative answer carries and how they are labeled there. Until now, AI Overviews and AI Mode ran exclusively on algorithmic source selection; now an explicit, user-driven channel exists alongside it.
Strategically, this means: brand loyalty, newsletter building, and community work no longer pay off only in direct traffic, but in generative visibility itself. And because the effect is personalized, it needs its own measurement logic. How clicks and impressions from AI Overviews and AI Mode can now be observed in Search Console is covered in the article on the new GSC report for generative AI.
FAQ
Does Preferred Sources improve rankings?
No. The effect is strictly personalized: only the user who has marked a source is more likely to see it in Top Stories and with a “Preferred” badge in Top Stories, AI Overviews, and AI Mode. For all other users and for general rankings, nothing changes.
Do I need the official button?
No. The deep link https://www.google.com/preferences/source?q=ihredomain.de leads to the same marking, without an external script and without additional consent overhead. The button is a convenience option for websites with well-maintained consent management, not a requirement.
Does this also apply to subdirectories?
No. Only domains and subdomains are eligible, such as example.com or code.example.com. A subdirectory such as example.com/magazin/ cannot be marked as a preferred source separately.
Bottom line
Preferred Sources shifts a small but fundamental part of the visibility decision from the algorithm to the audience. The effect is personalized, the effect size unquantified, the effort minimal: a link in the right places and an honest request to your own community. Brands that have built loyalty over years receive, for the first time, a documented return for it in Search — all the way into AI Overviews and AI Mode.
If you have no readership, there is nothing to win here. If you have one, do not leave it unmarked.