Google Preferred Sources in AI Overviews & AI Mode: Complete Publisher Guide (2026)

For the first time in the history of Google Search, a human being can override the algorithm — one reader at a time.

That’s the plain-language version of Preferred Sources, and if you publish anything online, it’s probably the most actionable lever you’ve been handed in years. Every other Google ranking factor asks you to optimize toward an algorithm and hope it rewards you. Preferred Sources flips that: your reader picks you, by name, and Google prioritizes you for that person specifically — in Top Stories, and now inside AI Overviews and AI Mode as well.

Here’s everything a publisher, SEO, or content team needs to know to actually use it.

What Preferred Sources Actually Is

Preferred Sources lets a signed-in Google user build a personal shortlist of publications they trust. Once a reader adds a site to that list, Google is more likely to surface that site’s content for them — and, on surfaces that support it, marks it with a visible “Preferred” label so the reader can spot it at a glance.

Crucially, it’s a personalization layer, not a ranking factor. Adding your site doesn’t make you outrank anyone in general search results, and it doesn’t help you show up for queries your content doesn’t actually match. It only changes what one specific reader sees, and only when your content is already relevant to what they searched for. Think of it less as SEO and more as a subscription button that Google itself operates on your behalf.

The Timeline: How We Got Here

• Roughly August 2025: Google quietly begins testing Preferred Sources. By the time it goes public, close to 90,000 unique sources had already been selected during the trial.
• Spring 2026: The feature rolls out globally in English for any query that triggers Top Stories.
• May 27, 2026: Google Product Manager Duncan Osborn announces the big expansion — Preferred Sources now extends into AI Overviews and AI Mode, alongside two companion features: a “perspectives” carousel surfacing firsthand takes from forums and discussions, and expanded “highly cited” labels elsewhere in results. Google reports 345,000 unique sources selected at this point — roughly four times the figure from December 2025 — and says preferred sources get clicked about twice as often as non-preferred ones.
• August 20, 2026: Google ships the piece publishers had been asking for — an embeddable Preferred Sources button that lives directly on your own pages, rather than sending readers off to a Google settings screen. Announced by Mrinalini Loew, General Manager of the Google Search Ecosystem, the update also reports the selection count has climbed past 600,000 unique sources.

In under a year, this went from a quiet experiment to a feature Google is actively asking publishers to install on their own sites.

Why AI Overviews and AI Mode Change the Math

Before May 2026, Preferred Sources only affected the Top Stories carousel — useful, but a limited surface with a finite, news-cycle-shaped audience. Once the feature extended into AI Overviews and AI Mode, the addressable audience changed by orders of magnitude, since both products now sit above or instead of the traditional results list for a large and growing share of queries.

That matters more than it might first appear. When a reader has marked your domain as preferred, your links can carry the same “Preferred” badge inside an AI-generated answer — and the badge persists across an entire AI Mode research session, not just a single query. If a reader spends ten minutes going back and forth with AI Mode researching a purchase or a topic, your brand’s preferred status follows them through that whole conversation, not just the first result.

Who’s Actually Eligible

The bar is lower than most publishers assume, and it’s worth checking before you build anything around this.

You qualify if:

• Your site publishes fresh content on a reasonably regular basis. Google has been explicit that this isn’t limited to news outlets — blogs, documentation sites, product hubs, and magazine-style content all qualify.
• Your site sits at the domain or subdomain level. example.com and blog.example.com are both eligible.

You don’t qualify if:

• Your content lives only in a subdirectory. example.com/blog is explicitly called out by Google as ineligible — only the root domain or a true subdomain can appear in the source preferences tool.
• Your site has gone stale. Google has indicated that sources which aren’t updated with any regularity can become unavailable for selection, so publishing cadence isn’t a one-time eligibility check — it’s ongoing.

The quickest way to check: search your own domain at google.com/preferences/source. If it shows up, you’re eligible today.

This subdirectory rule is a bigger deal than it sounds for larger publishers. Media groups that consolidated multiple verticals into folders on one domain — a very common SEO pattern over the last decade — can only be selected as a single, undifferentiated brand. A reader who wants your food coverage but not your politics coverage has no way to express that preference at the source level. Publishers that kept verticals on separate subdomains kept a granularity that consolidated competitors gave up.

How Readers Actually Add You

There are three paths, and they differ sharply in friction — which matters, because friction is the entire game here.

Before August 2026, the only self-service option was the deeplink — functional, but it dumped readers onto an unfamiliar Google settings page and left them there, with no path back to your content. The embeddable button fixes exactly that friction point: click, confirm, and you’re returned to the article you were reading.

Implementation: The Three Technical Options

Google’s Search Central documentation lays out three ways to add this to your site, in order of what Google itself recommends:

1. Standard embed (recommended). The simplest path — Google says two lines of HTML are enough. Google renders the button, handles localization automatically, and you can set it to a light or dark theme to match your site.

2. JavaScript SDK. For teams that want the “add as preferred source” action triggered from their own custom UI element instead of Google’s default button design, Google provides an SDK path that lets you wire the action into whatever component you build.

3. Deeplink (for CMS platforms without JavaScript support). The plain-URL fallback, in the format:

https://google.com/preferences/source?q=yourdomain.com

This works as a text link or a clickable image, requires no JavaScript, and is the only option that functions reliably in newsletters and some third-party CMS environments. Google also publishes downloadable button design assets in 16 languages — including English, German, French, Spanish, Japanese, Korean, and Hindi — for publishers who’d rather use pre-built visuals than design their own.

Where the Feature Actually Shows Up — and Where It Doesn’t Yet

Availability isn’t uniform across surfaces, which is worth knowing before you promise your team full coverage:

• Top Stories: Available globally, in every language Google Search operates in.
• AI Overviews and AI Mode: Available in all languages and locales where those two products themselves currently exist — a narrower footprint than Search overall, simply because AI Mode and AI Overviews haven’t reached full global availability yet. As those products expand geographically, Preferred Sources rides along automatically.

What Preferred Sources Won’t Do

Worth stating plainly, because it’s easy to oversell this internally:

• It won’t rank you for queries your content doesn’t match. Relevance still gates everything; the preference only breaks ties in your favor once you’re already in the running.
• It does nothing for readers who haven’t opted in. This is a per-reader signal, not a site-wide visibility boost — it compounds slowly, one reader relationship at a time.
• There’s currently no publisher-facing dashboard showing how many readers have preferred you, your resulting click-through lift, or which content drove the adds. You’re optimizing somewhat blind, using Google’s aggregate stats (twice the click-through rate, 600,000+ total sources selected) as your only public benchmark.
• It’s not a substitute for E-E-A-T, structured content, or the fundamentals that get you cited in AI answers in the first place. Preferred Sources amplifies brands that already have substance — it doesn’t manufacture authority from nothing.

A Practical Rollout Checklist

1. Check eligibility first. Search your domain at google.com/preferences/source before designing anything.
2. Fix your domain structure if needed. If your best content sits in a subdirectory, this is one more reason to consider a subdomain strategy.
3. Install the standard button on high-traffic, high-loyalty pages first — think evergreen guides and cornerstone content, not your homepage hero, where a first-time visitor has no reason yet to prefer you.
4. Add the deeplink to your newsletter footer and social bios as a zero-effort secondary channel.
5. Keep publishing on a real cadence. Eligibility isn’t a one-time badge — inactive sources can lose their standing.
6. Don’t neglect the fundamentals. Preferred Sources rewards sites that already earn citations in AI answers through clear structure, genuine expertise, and crawlable content — it doesn’t replace that work.
7. Re-check quarterly. Both the feature’s surface coverage and Google’s documentation have moved fast in 2026; treat this guide as a snapshot, not a permanent spec.

FAQ

Is Preferred Sources a ranking factor?

No. Google is explicit that it’s a personalization signal layered on top of relevance, not a replacement for it.

Can I add my own site as a preferred source to game the system?

No — the selection has to come from an actual reader’s account. There’s no mechanism for a publisher to self-select.

Does this only work for news publishers?

No. Google has stated that any site publishing fresh content is eligible, including blogs, product documentation, and magazine-style sites.

What happens to sites in a subdirectory of a bigger domain?

They’re not eligible on their own. Only the parent domain or a true subdomain can be selected — content in a folder like /blog inherits nothing separately.

Is the embeddable button free to use?

Yes — the implementation code and design assets are published in Google’s Search Central documentation at no cost.

Does being preferred help in every country and language?

Top Stories coverage is global. AI Overviews and AI Mode coverage currently matches wherever those two products themselves are live, which is narrower and still expanding.

Sources and further reading

This guide is based primarily on Google’s current first-party documentation and announcements. Google’s Preferred Sources documentation explains eligibility, AI Mode and AI Overview availability, and the standard, custom and deeplink implementations.

Google’s Search documentation changelog records the January publisher documentation, April global language expansion, May rollout into AI Overviews and AI Mode, and August 20 addition of the new custom interactive button.

For the broader AI Search context, Google’s official generative AI optimization guidance explains how existing SEO practices, Search indexing and retrieval continue to relate to AI experiences.

Google Preferred Sources documentation
Google’s AI Search optimization guide
Google Search documentation updates