Google just gave publishers a new way into AI answers
Preferred Sources now extends into AI Overviews and AI Mode. Publishers can place an interactive button on their own sites, turning audience loyalty into…
The publisher\'s relationship with the human has become part of the machine-mediated information environment.
Author: Anton Sopov
Published: August 21, 2026
Category: Platform News
For most of the short history of Answer Engine Optimisation, the central question around citations has been straightforward: how does an AI system decide which sources to trust and use? The assumed answers have involved some combination of relevance, authority, freshness, content quality, retrievability and the mechanics of the underlying search system. Google is now making another factor increasingly explicit: what sources does the user prefer?
Google has expanded its Preferred Sources functionality across Search, AI Overviews and AI Mode. On August 20, it announced a new mechanism that makes the feature substantially easier for publishers to promote. Publishers can place an interactive Preferred Sources button directly on their own websites, allowing readers to add the publication to their Google source preferences without navigating away from the publisher\'s page. For publishers, that creates a new call to action: do not just subscribe to us, tell Google you prefer us. For AEO, that is potentially significant.
<h2>Preferred Sources is not entirely new</h2>
There is an important timeline distinction. Google did not suddenly introduce Preferred Sources into AI search on August 20. Google\'s Search documentation shows that Preferred Sources has been evolving throughout 2026. Google added publisher documentation in January, expanded Preferred Sources globally across supported Search languages in April, and on May 27 explicitly updated its documentation to say Preferred Sources was beginning to roll out to AI Overviews and AI Mode.
The August 20 development is different. Publishers can now make selecting them substantially easier by putting the Preferred Sources interaction on their own sites. The AI integration began earlier. The new development gives publishers a more practical mechanism for actively recruiting preferred-source status from their audiences.
<h2>What does selecting a Preferred Source actually do?</h2>
This needs careful wording because it would be easy to overstate Google\'s claim. For Top Stories, Google\'s publisher documentation says that when a user selects a publication as a Preferred Source, content from that site is more likely to appear, highlighted with a preferred badge.
For AI Mode and AI Overviews, Google describes the effect somewhat differently. Its documentation says content from a selected source can be highlighted with a preferred badge for users who have chosen that publication. Google\'s consumer help documentation similarly says users can tailor AI Mode and AI Overviews to highlight content from sources they value most.
The defensible conclusion is narrower than some coverage has suggested. Google now explicitly incorporates user-selected source preferences into how sources are highlighted within its AI-search experiences. Google has not disclosed a conventional ranking weight, and its own language around AI Mode and AI Overviews focuses on highlighting preferred sources rather than guaranteeing their selection as underlying evidence.
<h2>The user can now influence the evidence environment</h2>
Consider the normal model of AI retrieval. A user asks a question. Google\'s systems determine which information is relevant. They retrieve sources. The model synthesises those sources. The user receives an answer. Preferred Sources introduces another signal into that system: Google knows which sources this user has explicitly said they value, and preferred sources can be highlighted in the AI experience.
Google\'s own help documentation makes the personalisation explicit: selecting sources tailors the user\'s experience across Top Stories, AI Mode and AI Overviews, and those preferences persist across browsers when the user is signed into the same Google account. That means source preference is not merely inferred from behaviour. It can now be declared by the user.
<h2>A new kind of off-engine AEO</h2>
For publishers, this creates an interesting optimisation opportunity. Historically, publishers have asked readers to subscribe, follow, bookmark, join the newsletter, enable notifications and follow on social media. Now there is potentially another call to action: make us one of your Preferred Sources on Google.
Google explicitly encourages this behaviour. Its Search Central documentation tells publishers they can promote a direct link to Google\'s source-preference tool through social posts and promotions, or add a Preferred Sources button alongside their existing social calls to action. Google even provides button assets in multiple languages. That turns audience development into something that may also affect the publisher\'s visibility within Google\'s AI-search ecosystem. A publisher\'s human audience relationship can now potentially influence its machine-mediated visibility for those same users.
<h2>Audience loyalty becomes an AI-search asset</h2>
Much of AEO has focused on optimising the content asset: making articles clearer, adding original information, improving citations, establishing authorship, using structured data, creating stronger entity relationships and keeping information current. Those things remain important. Google\'s broader guidance for AI Search continues to emphasise unique, useful, non-commodity content and says established Search best practices remain relevant to AI Overviews and AI Mode.
But Preferred Sources introduces another potential asset: the relationship between the publisher and its audience. A publisher with a loyal readership may now be able to convert some of that loyalty into an explicit Google preference signal. That is fundamentally different from optimising a webpage. It is closer to optimising the publisher-user relationship.
<h2>This could particularly matter for specialist publishers</h2>
Imagine two publications. Publisher A has huge domain authority, a massive general audience and little direct relationship with individual readers. Publisher B is a smaller specialist publication with a highly engaged audience whose readers actively subscribe, return frequently and consider it authoritative within a particular field. Traditional search economics strongly favour Publisher A in many circumstances. Preferred Sources potentially gives Publisher B another mechanism. Its most engaged readers can explicitly tell Google they value this source.
That does not mean the smaller publisher suddenly outranks the larger one. Google has made no such claim. But it introduces a mechanism through which niche authority and audience loyalty can become visible to the AI-search interface. For specialist publishers, that is worth paying attention to.
<h2>It also complicates AI visibility measurement</h2>
There is another implication that may ultimately matter just as much. The industry has become accustomed to talking about AI visibility as though a brand has one objective level of visibility. But Preferred Sources illustrates why that model is increasingly incomplete. Two users can ask the same question. One has explicitly selected Publisher A. The other has selected Publisher B. Their source environments may no longer be identical.
AI visibility can increasingly become conditional on query, location, language, model, search context and now, explicitly, user source preferences. That makes statements such as "this is what Google AI Mode says" increasingly problematic. A better formulation may eventually be: "this is what we observed under these specific conditions." For serious AEO measurement, context matters.
<h2>This is another reason API-only measurement can be incomplete</h2>
Preferred Sources also highlights a broader methodological problem for AI-visibility platforms. If an AEO measurement system repeatedly executes prompts through an API or a clean, standardised environment, it may accurately measure that environment. But real users increasingly encounter personalised environments. Google\'s consumer documentation explicitly describes Preferred Sources as a way to customise Top Stories, AI Mode and AI Overviews.
That does not invalidate standardised tracking. Controlled environments remain essential for comparable longitudinal measurements. But it does mean controlled measurement and actual user experience are different constructs. AEO increasingly needs both: controlled visibility, measuring what the engine returns when context is standardised, and experienced visibility, measuring what real people encounter given their actual preferences and context. That distinction will become increasingly important as AI-search personalisation develops.
<h2>There is an interesting publisher-economics connection</h2>
The timing is notable. A newly released randomised field experiment involving 1,100 Google users found that reducing exposure to Google\'s AI-search features increased external publisher clicking, while an AI Mode-only experience substantially reduced external click-through and also lowered several measured aspects of user experience and trust. That research reinforces the economic tension between publishers and AI-search platforms: AI systems need publisher information, but AI-generated answers can reduce the need to visit the publisher.
Preferred Sources does not solve that problem. A preferred publisher can still influence an AI experience without necessarily receiving the traffic it would have received from traditional Search. But Google is creating another mechanism through which publishers can compete for prominence inside the AI interface itself. That may become increasingly important if AI search continues to absorb more of the user\'s information journey.
<h2>A larger strategic shift</h2>
The first generation of AEO has largely treated machine visibility as a technical and content problem. Can the machine access you? Can it understand you? Does it trust your evidence? Does it retrieve you? Does it cite you? Preferred Sources suggests that AI visibility may eventually depend on a broader set of signals. Some may be machine-derived: authority, relevance, freshness, retrievability, source quality and entity understanding. Others may increasingly be human-derived: source preference, audience loyalty, user behaviour, personal context and previous interactions.
That creates a much richer model of AI visibility. The answer engine is not simply determining what is the best source. It may increasingly be determining what is the best source for this question, for this user, in this context. That is a fundamentally more personalised information environment.
<h2>Do not call Preferred Sources an AI ranking factor yet</h2>
It would be tempting for the AEO industry to turn Google\'s announcement into a claim that Preferred Sources is Google\'s newest AI ranking factor. The evidence does not support that framing. Google has not disclosed a conventional ranking weight, and its own language around AI Mode and AI Overviews focuses on highlighting preferred sources rather than guaranteeing their selection as underlying evidence. The better conclusion is that Preferred Sources is an explicit personalisation signal that affects source presentation within Google\'s AI-search experiences. Whether, and under what conditions, it materially affects retrieval, citation frequency or generated-answer composition requires measurement. That is now an empirical AEO question.
<h2>What publishers should do now</h2>
The immediate action is unusually straightforward. If a publication is eligible for Preferred Sources, Google itself recommends making it easier for readers to select the publication. Publishers can check whether their domain appears in Google\'s source-preference tool, add Google\'s Preferred Sources CTA to their website, include a direct source-preference link in newsletters, social channels and other audience communications, and measure whether preferred-source adoption appears to correlate with changes in AI Overview, AI Mode or Top Stories visibility.
One technical limitation is worth noting: Google says Preferred Sources eligibility operates at the domain or subdomain level, not the subdirectory level. A domain such as example.com or subdomain such as news.example.com can qualify, while a path such as example.com/blog cannot independently qualify. For publishers building an AEO strategy, this is therefore one of the rare new tactics that can be implemented immediately.
<h2>AEO Updates Takeaway</h2>
The button is not the important part. The important part is what it represents. For years, search engines largely inferred what sources users valued through behaviour. Google now gives users a mechanism to explicitly declare source preference, and those preferences extend into its generative-search experiences. That creates an intriguing new loop: a publisher creates valuable information, a reader develops trust, the reader explicitly designates the publisher as preferred, and Google carries that preference into AI Mode and AI Overviews. The publisher\'s relationship with the human has become part of the machine-mediated information environment. The emerging optimisation question is no longer simply how to convince the machine that a source is good. It may increasingly include how to build enough trust that humans explicitly tell the machine it is a good source. Those are very different strategies. The strongest publishers may ultimately need to do both.
<h3>References</h3>
[1] Google Search Central. "Help your readers find your site through preferred sources in Google Search." https://developers.google.com/search/docs/appearance/preferred-sources
[2] Google Search Help. "Preferred Sources in Google Search." https://support.google.com/websearch/answer/15523498
[3] Google Search Central. Documentation changelog. May 27, 2026 entry. https://developers.google.com/search/updates
[4] The Verge. "Google now lets publishers add a Preferred Sources button to their sites." August 20, 2026.
[5] Google Search Central. "Get started with AI Overviews and your website." https://developers.google.com/search/docs/appearance/ai-overviews