Google Preferred Sources: Help Readers Choose Your Site in Search and AI Overviews
Jack Amin
Digital Marketing & AI Specialist
Quick Answer
Google Preferred Sources lets signed-in users select publications they want to see more often in eligible news-oriented experiences. Google documents a source-preference button and deeplink publishers can use to help readers make that choice. Selection may highlight content in Top Stories and, where supported, AI Mode or AI Overviews. It is a reader preference, not a universal ranking boost, and eligibility or visibility is not guaranteed.
Google Is Giving Readers a Direct Preference Control
Google's Preferred Sources feature lets signed-in users choose publications they want to see more often in supported news and search experiences. Google has documented implementation options that publishers can use to open the preference flow from their own site.
This is unusual because it gives a reader an explicit influence over source selection. It is also easy to oversell.
A preferred-source selection is not a universal ranking boost. It affects eligible experiences for the person who made the choice, and Google does not guarantee that every item from the source will appear.
Where Preferred Sources Can Matter
Google's current documentation describes potential highlighting in experiences including Top Stories and, where supported, AI Mode or AI Overviews.
The feature is most relevant to organisations that publish recurring, timely and recognisable editorial content. A reader needs a reason to want more from the same source.
That may include:
- news publishers
- specialist trade publications
- research organisations
- industry analysis sites
- brands with a genuine recurring editorial product
A business that publishes one sales article every six months should improve the publishing proposition before adding a preference prompt.
Check Eligibility and the User Experience
Use Google's current documentation and source-preference flow to confirm whether the publication can be found and selected. Availability and interfaces can change by country, account and product rollout.
Test while signed in and signed out. Check mobile and desktop. Record exactly what the user sees rather than relying on a screenshot from another market.
If the source is not eligible or discoverable, do not publish a broken button.
Use the Official Implementation
Google documents a Preferred Sources button and a deeplink option. Follow the current specification rather than copying unofficial code.
Implementation checks should include:
- correct publication/domain reference
- accessible button name
- clear explanation of what the action does
- new-window behaviour where appropriate
- analytics event for the outbound action
- no interference from consent banners or overlays
- mobile touch target and keyboard access
The prompt should never claim “make us rank first” or “always see Codeble in Google”.
Ask After You Have Earned the Preference
The best moment is after a reader has found sustained value: at the end of a strong article, near an existing newsletter follow action or on a publication information page.
Avoid a full-screen prompt on first arrival. The user cannot reasonably prefer a source they have not yet evaluated.
Use plain copy such as:
“Read Codeble regularly? You can choose it as a preferred source in supported Google news and AI experiences.”
Follow with a short qualification: availability depends on the user's Google account and supported features.
Build a Publication Worth Choosing
Preferred Sources amplifies preference; it does not manufacture it. Strengthen:
- a clear editorial focus
- named authors with relevant expertise
- original reporting, analysis or practitioner evidence
- reliable publication cadence
- visible dates and material update notes
- corrections policy
- fast, accessible article pages
- high-quality original images
- useful email or RSS follow options
Google's broader generative-AI guidance prioritises unique, valuable, non-commodity content. That remains the main work.
Connect the Feature to Your Measurement Model
Track the outbound preference-button event using an explicit event name such as preferred_source_click. Record placement and article context.
Then monitor:
- button click-through rate
- repeat reader and subscriber trends
- Search Console visibility for news-oriented content
- direct and branded traffic
- article engagement and return frequency
Do not attribute later Google impressions directly to button clicks unless Google supplies evidence that supports that link. Report correlation and scope honestly.
Avoid Four Common Mistakes
1. Treating it as a ranking hack. The control represents an individual reader's preference in eligible experiences.
2. Showing it everywhere. Repeated prompts create fatigue and can weaken trust.
3. Implementing before checking eligibility. A broken or empty flow damages the experience.
4. Neglecting the editorial product. Readers choose sources because the content repeatedly earns attention.
A Practical Launch Plan
Day 1: verify eligibility, supported market behaviour and the official implementation.
Day 2: add an accessible prompt to one high-value article template placement.
Day 3: test signed-in, signed-out, mobile and desktop flows; validate analytics.
Weeks 1–4: monitor interaction without changing multiple placements.
After 30 days: decide whether to keep, revise or expand based on reader behaviour and site experience—not a promised ranking lift.
Preferred Sources is a useful retention and discovery mechanism for the right publisher. The strategic advantage still comes from being a source a person deliberately wants to hear from again.
Official Sources
Frequently Asked Questions
Let's discuss your project
Need to assess whether Preferred Sources fits your publishing and search strategy?
