Google Preferred Sources: What It Changes—and What It Cannot Guarantee
Implement Google’s Preferred Sources deep link, explain the user-level preference accurately, and measure the CTA without turning clicks into ranking claims.
Published August 9, 2026: Google now documents how publishers can help readers select a site as a Preferred Source. For a user who makes that choice, the publisher can become more likely to appear in Top Stories and can receive a preferred badge in eligible AI Mode and AI Overviews experiences.
That is useful audience infrastructure, but it is not a universal ranking switch. The selection belongs to an individual user, eligible sites are domains or subdomains rather than subdirectories, and Google does not promise an appearance for every query. The right implementation is a truthful preference call to action with a bounded measurement plan.
What a Preferred Sources selection changes
Google’s publisher guide says a selected source is more likely to appear in Top Stories for that user and can be highlighted with a preferred badge in AI Mode and AI Overviews where those features are available. The feature is available for Top Stories globally in supported Search languages; AI surfaces depend on their own availability.
The preference does not reserve a result, replace normal eligibility, or apply to every person searching. A page still needs to be discoverable, relevant, technically eligible, and suitable for the result surface. Treat the selection as a user-level preference signal, not an owned ranking.
Google allows domain-level and subdomain-level sources in the preference tool. A publication at news.example.com can be eligible as a source; example.com/news cannot be selected as a separate subdirectory source. Check the actual tool before promoting the button.
Implement the deep link without overpromising
Google documents the format https://google.com/preferences/source?q=example.com. Use the publisher’s eligible host as the query value, test the destination while signed in and signed out, and keep the CTA next to other follow options such as RSS or a newsletter.
| Element | Good implementation | Avoid |
|---|---|---|
| Label | Add us as a preferred source on Google | Guarantee our stories in Google |
| Destination | Google’s source-preference tool with the eligible host | A redirect chain or untested subdirectory |
| Context | Explain that the setting belongs to the reader | Implying a sitewide ranking benefit |
| Placement | Near follow, newsletter, or publisher-trust controls | An obstructive modal before the reader sees content |
Do not hide the destination behind misleading button copy. A reader should know that the click opens a Google preference setting and that selection can influence what that reader sees.
Measure the preference funnel at the layer you control
A publisher can measure CTA impressions, outbound clicks, placement, device, and page context. Unless Google exposes a confirmed-source event to that publisher, an outbound click is not proof that the user completed the selection. Keep those states separate.
- Save a release annotation for the CTA.
- Track eligible CTA impressions and outbound clicks.
- Separate site, page template, device, and placement.
- Do not label clicks as completed preferences.
- Observe Top Stories, Search, Discover, and AI reporting within their documented limits.
- Compare reader retention and newsletter or RSS adoption independently.
Google Search Console does not expose a dedicated Preferred Sources performance dimension in the publisher guide. Search observations remain aggregate and can be affected by news demand, publication volume, crawl state, and many other changes. The AI visibility measurement crosswalk helps keep appearances, referrals, and outcomes from collapsing into one score.
When the CTA is worth adding
Add it when the site is eligible, publishes recurring material that readers may want to follow, and can explain the setting honestly. Skip or delay it when the domain is absent from the preference tool, the CTA would compete with a more valuable reader action, or the team intends to report the click as a ranking win.
Preferred Sources is one follow mechanism among several. RSS, email, browser bookmarks, and direct visits remain publisher-controlled routes. A balanced footer or author box can present them together without turning the page into a wall of acquisition prompts. SearchEngineAnswer’s editorial policy keeps the difference between documented capability and measured outcome visible.
Ask a question or join the discussion