Publishers do not control every surface where readers discover reporting. Google’s Preferred Sources feature gives readers a way to choose publications they want to see more often in supported Search experiences. For publishers, the practical opportunity is to make that choice easy to find without presenting it as a ranking shortcut or a promise of traffic.

How the preference works

A reader selects a publication as a preferred source through Google’s interface. Google says selected content may be more likely to appear in Top Stories and can receive a preferred label in AI Mode and AI Overviews where those features are available. The preference belongs to the reader. A publisher cannot select itself on a reader’s behalf, and the feature does not guarantee that a particular article will appear.

Availability depends on the search feature and locale. Google’s current documentation says Preferred Sources is available globally for Top Stories in supported Search languages, and can appear in AI Mode and AI Overviews where those experiences are available. A site must also be included in Search generative AI features to be eligible in those AI surfaces.

Check eligibility before adding a button

Google’s source-selection tool accepts domain-level and subdomain-level sites, such as example.com or news.example.com. A subdirectory such as example.com/news is not a separate eligible source. Search for your publication in the source selector before adding a call to action, and confirm the site’s canonical host and Search Console property are the ones you intend to promote.

If readers cannot find the publication in the selector, first verify the site and eligibility requirements. Adding a button does not itself make a site eligible or cause Google to list it.

Choose an implementation that fits your site

Google documents three approaches:

  • Standard interactive button: add Google’s publisher script and the documented button element. Google handles localization and the selection flow.
  • Custom implementation: use the JavaScript SDK when the site needs to control where and how the action is triggered.
  • Deeplink: use a direct link when the CMS cannot load the interactive button, or when you want to include the action in an email or social post.

Use the standard option unless your technical or design needs require more control. Review Google’s current implementation instructions before deploying; provider scripts and attributes can change.

Place the prompt where it helps readers

Explain what the choice does in plain language, then offer it near a publication’s newsletter prompt, article footer, or “follow this publication” area. Keep the action optional and separate from subscription, account creation, or consent. Do not imply that a reader must select the site to keep reading.

Measure button visibility and clicks using your own privacy-respecting analytics if appropriate. These measures show interaction with your prompt; they do not establish that a reader selected the source or that the selection led to an impression or visit.

What publishers should not promise

  • A preferred-source selection does not guarantee a ranking, Top Stories placement, AI citation, or click.
  • A button does not replace clear author identity, accurate reporting, technical crawl access, or useful original content.
  • Preferred-source interactions are not equivalent to newsletter subscriptions or consent to marketing.
  • A rise in Search traffic after adding the feature does not prove the feature caused the change; compare like-for-like periods and note other releases.

Use the feature as an audience choice, not as a substitute for reporting quality or distribution strategy. Keep the publication accessible to readers who do not use the preference tool.

A measured rollout checklist

  1. Confirm the eligible domain or subdomain appears in Google’s selector.
  2. Check Search Console settings for inclusion in Search generative AI features if you plan to support those surfaces.
  3. Select the standard button, SDK, or deeplink implementation from Google’s current documentation.
  4. Test the control on mobile and desktop, and confirm it does not block reading or create layout shifts.
  5. Record deployment date and the exact pages where the control appears.
  6. Review subsequent Search Console data as an observation; avoid attributing changes without a comparison design.

Readers decide whether to mark a source as preferred. Publishers can explain and enable the choice; Google determines whether and where the content appears.

Primary source: Google Search Central: Guide to Preferred Sources in Google Search for Web Publishers. See the Search Central documentation update history for current feature changes.