Google Preferred Sources: The One AI Visibility Lever Readers Hand You

In short: Google extended Preferred Sources into AI Overviews and AI Mode. When a reader designates a site, that site's links are labeled and stand out inside AI answers. It works in every language Google Search supports, and eligibility is not limited to news publishers — any domain or subdomain qualifies. Google reports that designating a site doubles the likelihood of a click, but that is a vendor-reported figure with no published sample or design. What matters most: in a field where almost nothing is under the site owner's control, this is a rare point where you can ask for the outcome.

---

An exception to the "you cannot control this" premise

Whether an AI answer mentions your brand is mostly outside your control. No site owner can tell a model what to search for or which document to cite. Most of what RanketAI has published operates inside that constraint — measure, isolate causes, improve the content, and wait.

Preferred Sources is an exception. A reader designates a site directly, and that site is then favored in the results and AI answers shown to that reader. Site owners can place a button on their own pages requesting exactly that designation.

How it expanded — from a news surface to AI answers

The feature existed before 2026, but its reach widened in stages.

Date	Announcement	Unique sites selected
2025-12-16	Top Stories expands to English-language users worldwide	~90,000
2026-04-30	Global rollout in all supported languages	200,000+
2026-05-27	Extended to AI Overviews and AI Mode + "Highly Cited" badge	345,000+

(Sources: Google, 2025-12-16 · 2026-04-30 · 2026-05-27)

That is roughly 90,000 to 345,000 in five months. Google described the AI-answer behavior this way:

Your Preferred Sources will be clearly labeled to stand out. — Google, New ways to find your favorite sources and original content in AI Search, 2026-05-27 (original)

The same announcement introduced a "Highly Cited" badge, which flags the primary reporting that other articles reference. Google is now separating documents that originate citations from those that relay them — the same direction that makes third-party citation coverage valuable.

Language coverage is not the constraint

The publisher documentation states the scope plainly:

The preferred sources feature is available globally for the "Top Stories" feature in all languages where Google Search is available. — Google Search Central, Guide to Preferred Sources in Google Search for Web Publishers (original)

The same document confirms AI Mode and AI Overviews support every language and region, and the April 2026 announcement covers all supported languages. Non-English sites are in scope.

Coverage and frequency are different questions, though. How often AI Overviews trigger for a given language, and how often a preferred label appears inside them, is not published — that part each brand has to measure directly.

Eligibility and setup — news publishers are not the only ones

The stated conditions are looser than most people expect.

Item	Requirement
Unit	Domain or subdomain only. example.com and blog.example.com qualify; example.com/blog does not
Industry	No news-publisher restriction appears in the documentation
Structured data	Not required — the feature works without additional markup
Installation	JavaScript button or deep link

The recommended installation is two lines:

<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>
<div google-add-preferred-source-btn></div>

(Source: Google Search Central publisher documentation)

An advanced implementation with custom styling is also supported. The subdirectory restriction is the constraint that matters most in practice — you cannot nominate one section of a site. The domain is the unit.

The click figure needs qualifying

Google published the same claim in two announcements:

Readers are twice as likely to click through to a site after marking it as a Preferred Source. — Google, Preferred Sources now available in all languages, 2026-04-30 (original)

The number is clear; the interpretation should not be. Three things were not disclosed.

1. Sample and study design — how many sites, over what period, against which comparison group.
2. Direction of causality — someone who designates a site as preferred already trusts it and likely visited it often. Whether the click increase comes from favored placement or from a self-selected audience is not separable. Correlation is not causation.
3. Independent verification — this is a vendor-reported measurement with no external audit.

So "install it and clicks double" is the wrong reading. The accurate one is narrower: this reinforces reach among readers who already trust you. It does not generate new discovery.

What to actually do

The mechanic is earned. Installing the button does nothing until a reader chooses to press it. What a site owner controls is the visibility of the request, not the outcome.

1. Confirm your unit is a domain. If your content lives in a subdirectory, it does not qualify. If your blog sits on its own subdomain, that subdomain can be nominated.
2. Place the button where people return. First-time visitors do not press it. Newsletter confirmation screens, the end of a series, and pages with high repeat traffic convert better.
3. Ask through channels you already own. Since the audience is people who already trust you, an email to existing subscribers will likely outperform a site banner.
4. Decide how you will measure first. The feature acts on personalized results, so it has no effect for readers who did not designate you. Aggregate impression metrics will not isolate it — pair brand-search traffic with return-visit metrics instead.
5. Do not let it displace the fundamentals. Preferred Sources works on an audience you already have. Reaching people who do not know you yet still depends on content that gets selected as an answer's basis and on citations in third-party documents.

Frequently asked questions

Can a regular company site apply, or is this only for news publishers?

The publisher documentation contains no industry restriction. The only stated condition is the domain or subdomain unit. That said, the feature began in Top Stories, so impressions may cluster around news-shaped queries. Expect the effect to vary by industry and query type.

Will installing it increase my AI Overviews visibility?

Only for readers who designated you. It has no effect on anyone else's AI answers. This is not a reach-expansion feature; it favors your site in the results of people who already chose you. If new discovery is the goal, you need a different instrument.

Is the button the only option?

A deep link that opens the settings surface is also documented, which is useful when you are asking through a newsletter or social post rather than on your own site. Neither path requires structured data.

If budget and time are tight, should this come first?

No. The mechanic works when you already have a returning audience. With few repeat readers, building content that gets selected as an answer's basis comes first. Installation costs almost nothing, so treat it as a low-priority item you do alongside the real work rather than instead of it.

Once designated, does it persist?

Users can remove a designation at any time. And being designated does not keep content surfacing regardless of quality — citation is an asset that decays without maintenance, the same structure described in citation decay.

How do I verify the effect?

Because it is a personalization feature, aggregate impression data will not isolate it. Google Search Console's generative AI reporting supplies some impression data but does not distinguish preferred designations. The scope and limits of that reporting are covered in the Search Console generative AI report.

---

Related reading

• One Query Becomes 12 Searches — Sub-Query Coverage for AI Search Visibility
• Where the Documents AI Cites Actually Live — Source Gap Analysis
• AI Citations Have a Shelf Life — Why Unrefreshed Pages Decay
• What Is GEO — Definitions and Optimization Methods