Google Preferred Sources A Publisher Implementation Guide

When a user selects a domain or subdomain as a preferred source, Google says its content is more likely to appear in Top Stories for that user and may receive a preferred badge in AI Mode and AI Overviews. The effect is personalized to the chooser. It is not documentation of a sitewide authority boost for people who never selected the source.

That distinction changes the strategy. This is closer to asking a loyal reader to subscribe than adding hidden metadata for a crawler. A publication needs recognizable identity, recurring value, and an audience with a reason to make the choice. The implementation can reduce friction, but it cannot manufacture preference for an interchangeable source.

Google’s tool supports domain-level and subdomain-level sources, not a subdirectory such as /blog. Search the source preference tool for the exact publication host first. Decide whether the root domain or a dedicated publication subdomain carries the identity readers recognize, then keep that host stable.

A missing source should be logged as an availability state, not worked around with deceptive redirects or a button that promises a result the tool cannot produce. The feature’s global language availability does not guarantee that every site is present or that every generative feature is available in every locale.

Google documents the format https://google.com/preferences/source?q=example.com. Encode the host as a URL parameter, label the destination clearly, and use an ordinary anchor so the action works with a keyboard and without client-side routing. If a supplied button asset conflicts with the publication’s design system, Google also permits a custom design.

Place the control where a reader has encountered enough evidence to understand the request: an article footer, subscription area, or source-following panel. Do not interrupt the first paragraph or disguise the external action as site navigation. Include accessible text that explains that the choice is managed by Google and affects that reader’s results.

Track impressions of the call to action and outbound clicks with a first-party event name such as preferred_source_opened. Google’s documentation does not provide a publisher count of completed preferences, so an outbound click is not a confirmed selection. Avoid labeling it as a subscriber, conversion, or ranking signal.

In Search Console, annotate the CTA launch and compare the same content families over time. Changes can have many causes: news demand, indexing, Top Stories eligibility, broader AI feature rollout, or ordinary ranking movement. A useful result is that engaged readers use the preference path and continue returning—not a claim that one button mechanically lifted every URL.

A topical publication, newsroom, or durable research archive has a coherent case: readers may want more from the same source. A miscellaneous collection of one-off pages has a weaker case because the preference promises future consistency. Before adding the control, review whether the host has a clear editorial focus, author identity, update practice, and enough recurring material to reward the choice.

Preferred Sources can support an owned-audience strategy, but it does not replace crawlability, indexability, useful reporting, or high-quality articles. Treat it as one transparent distribution control within a larger publishing system. If the site cannot explain why a reader should prefer it, improve the publication before optimizing the prompt.