Preferred Sources in Google – How to Become a Preferred Source in AI Overviews and AI Mode?

Google Preferred Sources is a search personalization feature that lets users indicate the sites they want to see more often in Google Search. For publishers, expert brands, SaaS companies, stores, and content sites, it isn’t a classic ranking factor but a new way to build a loyal channel for returning to content. In practice, it comes down to a simple mechanism: encouraging a reader who already trusts the brand to add the domain as a preferred source in Google. As a result, that domain’s content can be more strongly highlighted for that user in Top Stories, AI Overviews, and AI Mode.

What are Preferred Sources in Google?

Preferred Sources is a feature that lets a signed-in Google user indicate the sites they consider trusted and want to see more often. After such a choice, Google may highlight content from the selected domains in selected search surfaces, including Top Stories, AI Overviews, and AI Mode, if the given feature is available for the user and the query.

The most important thing is that this is not a “reward” granted by Google to a site, nor a global promotion in the ranking. Preferred Sources works on the user’s side. It is the user who decides which sources matter to them, and Google uses that preference as a layer of results personalization.

In the context of GEO and AI Search, this feature matters for two reasons. First, AI Overviews and AI Mode increasingly shorten the path from query to answer. A user can get a summary without having to visit the page. Second, if the user previously marked a given domain as preferred, a link from that domain may be highlighted with a “Preferred” label, which increases the chance that the reader notices a source they already know.

How does Preferred Sources affect AI Overviews and AI Mode?

Google describes Preferred Sources as a feature that helps users more easily find content from their favorite sites. In AI Overviews and AI Mode, this means the ability to highlight links coming from sources the user previously added to their preferences.

This does not mean, however, that the mere presence of a button on the page guarantees a citation in an AI answer. The page still has to meet the basic conditions: be accessible to Google, indexed, compliant with the quality guidelines, matched to the query’s intent, and contain fresh, useful content. Preferred Sources can help when the user has chosen the domain and there is matching content that Google can show in a given context.

A good way to think about this feature is to treat it as a loyalty layer in the search engine. SEO is responsible for whether content can be found and understood. GEO is responsible for whether content is suitable for summarizing, citing, and use by AI systems. Preferred Sources strengthens the relationship with a reader who already knows the brand and wants to see its content more often in Google.

What can Preferred Sources give a company?

The biggest benefit isn’t about “leapfrogging the competition” with all users. It’s more about regaining part of the control over distributing content to your own community.

If someone regularly reads a company’s blog, uses its newsletter, or returns to product guides, adding the domain to preferred sources may make Google show them that content more often in personalized results. In the case of AI Overviews and AI Mode, this increases the chance that in an AI answer the reader sees a source they already know.

Google also reports that users are twice as likely to click on a site after marking it as a Preferred Source. This information should be interpreted with caution: it is Google’s data about user behavior within this feature, not a guarantee of an identical effect for every domain, industry, and query type.

Who can become a preferred source?

Preferred Sources isn’t a feature only for large news publishers. Google indicates that sites publishing fresh content qualify. In practice, these can be news services, expert blogs, company sites with a knowledge section, SaaS services, online stores with guides, industry portals, and local brands that publish regular updates.

There is an important technical limitation: the user adds a domain or subdomain, not a single directory. This means you can add, for example, example.com or blog.example.com, but not example.com/blog. If the company blog runs in a subdirectory, the user adds the entire main domain.

This has practical consequences for site architecture. If a company runs several distinctly different content projects, a subdomain can offer greater precision in communication. If, however, the whole brand operates on a single domain, promoting the main domain will be simpler.

How do you implement Preferred Sources on your site?

Google offers three approaches: a standard JavaScript implementation, a more advanced implementation with your own interface, and a deeplink. In most cases, the standard button will be best, because the user can add the source without leaving the page.

Standard JavaScript implementation

The basic variant requires adding two HTML elements. The script is best placed in the <head> section, and the button container where the CTA should appear.

<script async src=”https://news.google.com/swg/js/v1/publisher.js”></script>

<div google-add-preferred-source-btn></div>

The button can be visually matched to the site template. Google supports, among others, light and dark themes and forcing the button’s language.

<div google-add-preferred-source-btn data-theme=”dark” data-lang=”pl”></div>

In a typical implementation, it’s worth testing the button on mobile devices, in light and dark mode, and with different browser language settings. The script is loaded asynchronously, so it shouldn’t block page rendering, but after implementation it’s good to check the impact on Lighthouse, PageSpeed Insights, and real Core Web Vitals data.

Advanced JavaScript

An advanced implementation makes sense when the team wants to trigger the flow from its own button, modal, sticky bar, or app component. It’s a good option for larger sites that have their own design system and don’t want to use the button’s default look.

The most important thing is to keep a clear intent. The user should understand that clicking doesn’t mean subscribing to a newsletter, doesn’t create an account, and doesn’t change settings on the publisher’s site. It’s an action on Google’s side: adding the domain to the user’s preferred sources.

Deeplink

A deeplink is simpler because it doesn’t require JavaScript. It works well in a newsletter, on social media, in an email footer, in sponsored articles, or in CMS systems that block external scripts.

<a href=”https://www.google.com/preferences/source?q=example.com” target=”_blank” rel=”noopener”>

  Add us as a preferred source in Google

</a>

The downside of a deeplink is greater friction. The user goes to an external Google page and confirms the choice themselves. That’s why on a website it’s better to start with the JS button and leave the deeplink as an option for external channels.

Where should you place the “Add us as a preferred source” CTA?

The best place depends on the type of site, but the principle is simple: the CTA should appear where the user has just received real value. Then the request to add the domain to preferred sources is natural rather than random.

Good places on the site:

• the end of an expert article, guide, or report;
• the site footer, especially in a blog or knowledge center;
• the newsletter sign-up page and the thank-you screen after signing up;
• the “About the author” or “Stay up to date” section next to recurring content;
• the user panel in a subscription service;
• guide category pages, if the user regularly returns for new content.

In e-commerce, the CTA doesn’t have to appear on every product card. Buying guides, rankings, inspiration sections, and “how to choose” content are better places. There the user has more reason to treat the domain as a source of knowledge rather than just a store.

How should you communicate Preferred Sources to users?

The message shouldn’t promise that the user will “always” see a given page in Google. It’s better to write simply and in line with how the feature works.

Example CTAs:

• Add us as a preferred source in Google and return to our guides more easily.
• Do you read us regularly? Add the domain as a preferred source in Google.
• Want to see our analyses in Google more often? Add us to Preferred Sources.
• Save this page as a trusted source in Google Search.
• Add us to your preferred sources and find our new publications faster.

In a newsletter, you can use a shorter message:

If you want to see our content more often in Google Search, AI Overviews, and AI Mode, add us as a preferred source. This setting works on your Google account’s side, and you can change it at any time.

Such a formula is safe because it doesn’t suggest manipulating the algorithm. It shows the user the benefit and clearly states that the decision is theirs.

The most common mistakes when implementing Preferred Sources

The first mistake is treating the feature as a new ranking factor. Preferred Sources doesn’t solve problems with indexing, content quality, topical authority, or technical SEO. If a site doesn’t publish fresh, useful content, the button alone won’t create demand to add it to preferred sources.

The second mistake is a too-aggressive CTA. A popup shown right after entering the site may work worse than a calm request after reading the article. The user first has to be given a reason to trust the domain.

The third mistake is a lack of measurement. Simply implementing the button isn’t enough if the team doesn’t know how many people click the CTA, which subpages the clicks come from, and whether the share of returning users grows after the campaign.

The fourth mistake is promoting the wrong domain. If a brand has several domains, subdomains, or language versions, it’s good to decide in advance which address the user should add to Google. Otherwise the campaign may scatter the signal across different variants.

How do you measure the effectiveness of a Preferred Sources implementation?

Google doesn’t provide a full, public dashboard showing how many users added the domain to Preferred Sources. That’s why effectiveness is measured indirectly: through events in GA4, user segments, CTR, returning traffic, and visibility in AI Search.

The simplest measurement setup looks like this:

1. Give the buttons and links attributes that identify the placement, e.g. data-placement=”article-footer” or separate CSS classes.
2. Configure an event in Google Tag Manager for a click on the button or the link to google.com/preferences/source.
3. Send the event to GA4 with parameters: placement, page_type, language, content_category.
4. Compare the results across page types: blog, guide, landing page, newsletter, author page.
5. Once a month, analyze the change in CTR and returning traffic for the content that promoted Preferred Sources most strongly.

What should a company do now?

The best Preferred Sources implementation starts not with code but with choosing the content that actually gives the user a reason to trust the domain. First, select high-engagement subpages: guides, analyses, reports, evergreen articles, author pages, and newsletter sections.

Then implement the JS button in a few controlled places and set up measurement in GA4. There’s no need to start with the entire site. A pilot on 10-20 strong subpages is better than mass-adding the button without a communication strategy.

In parallel, prepare communication in the newsletter and on social media. In these channels it’s better to use a deeplink, because the user leaves the page anyway. The message should be short: “Add us as a preferred source in Google if you want to see our analyses and guides more often.”

Finally, connect Preferred Sources with content updates. If you encourage a user to add your domain as a trusted source, the site should regularly publish fresh, specific, and useful content. Without that, the button becomes an empty gesture.