Google's Preferred Sources Button: Should a B2B SaaS Site Add It?

Google's Preferred Sources button lets readers add your site as a source they want to see more of, which can raise your chances in Top Stories and add a preferred badge in AI Overviews and AI Mode for those readers. For most B2B SaaS sites, the benefit is small unless you publish frequent, news-like content.

Cekpr covers how AI answer engines and Google choose sources, and what B2B software teams can do about it. This explainer is for SaaS marketers and founders who saw the button in Google's documentation and wonder if it is worth a developer's afternoon. It covers what the feature does, who it suits, how to add it and how to judge the result.

What is the Preferred Sources feature?

Preferred Sources lets people choose the sites they want to see more often in Google Search. According to Google's Preferred Sources documentation, sites that readers select are more likely to appear in Top Stories, with a preferred badge.

The same documentation says AI Mode and AI Overviews can show the badge in every language and locale where those features exist. The badge appears only for users who selected your site. To qualify for AI badges, your site must be included in Search generative AI features in Search Console.

Google has claimed an effect on clicks. According to a report on Google's guide update, Nick Fox said people are 2X more likely to click through to a site after marking it as a Preferred Source. The report notes that the figure came from Google's internal data and has not been independently verified.

Read that number with care. People who choose a source already like it, so their higher click rate may reflect existing loyalty, not the button's effect on strangers.

Who is eligible, and who actually benefits?

Eligibility is technical, and benefit is practical. Google's page says only domain-level and subdomain-level sites are eligible to appear in the source preferences tool, so a blog on a /blog path of your main domain is not eligible on its own. A blog on blog.example.com is.

The documentation does not limit the feature to news sites. It describes the feature as a way to help readers find a publication. Even so, Top Stories is a news surface. A SaaS site rarely appears there unless it publishes timely industry news or original reporting.

The ppc.land report adds that sources that are not updated regularly may be unavailable for selection. That favors publishers with a steady output over a blog that posts once a quarter.

The table below sorts typical B2B software publishers by likely benefit.

How do you add the Preferred Sources button?

Google describes three ways. The recommended method uses a script tag, preferably in the page head, that loads Google's library, plus a div with the google-add-preferred-source-btn attribute where you want the button. Optional attributes set the theme and language, and the button returns readers to the page they were on.

Developers who want a custom design can use the advanced JavaScript method, which loads the library in manual mode and calls functions from their own interface. Sites that cannot run JavaScript can use a deeplink to the source preferences tool with their domain in the query. Text links and clickable images both work, and Google supplies translated badge assets.

Google's documentation changelog shows that instructions for a custom, interactive button were added on August 20, 2026, and the main page was last updated on September 18.

The documentation stresses that these methods are optional. Your site can appear as a preferred source without a button. That makes the button a promotion tool, not an entry ticket.

Before you ship it, check that your site appears in the source preferences tool and that you meet the Search Console requirement for AI features. Our guide to Google's Search Console AI opt-out explains that control, since an opt-out would remove the AI badge benefit.

Will it help your AI citations?

It may help only a little, and only among readers who choose you. The badge in AI Overviews and AI Mode shows for users who selected your site, so it does not change what the model cites for everyone else. It is a personalization layer, not a ranking factor for all searchers.

For a broader view of what drives AI citations on software sites, see our review of what a 96,418-URL study means for SaaS page structure. Page structure and clear answers matter more for citation than a button does.

The same goes for referral traffic. If you want to see how AI products send visitors, start with our guide to tracking Gemini referral traffic in GA4. Those numbers are easier to defend than a badge impression.

How do you judge whether it worked?

Google's documentation does not describe any way to track preferred-source selections or their results. You have to infer. Add the button, then annotate the change date in your notes and compare Search Console clicks, impressions and branded queries before and after.

Keep the test honest. Pick a window of at least six weeks on each side, avoid launching other changes at the same time and compare the same pages. If you see a lift, check whether Top Stories or AI surfaces drove it, using the Search appearance filters.

Our walkthrough on how to measure AI search visibility in Search Console covers the reports you will need. Expect small numbers, and be ready to conclude that the effect is too small to measure.

What can a SaaS team do instead to win loyal readers?

If the button is a poor fit, build the loyalty it is meant to capture. Readers choose sources they return to, so the real work is giving them reasons to return. That means a clear editorial focus, a predictable schedule and content they cannot get elsewhere.

Start with original data. A short yearly survey of your customers, a benchmark from anonymized product usage or a teardown of public pricing pages gives other sites a reason to cite you. It also gives AI answer engines a fact that only your site has.

Add a simple email list. A reader who subscribes is more loyal than one who clicked a badge, and you own the relationship. A weekly or biweekly digest of your best posts keeps your name in front of the people most likely to search for you later.

Finally, keep your pages fresh. Update stale posts with new numbers and a visible date. Google's own notes suggest that sources that are not updated regularly may drop out of selection, and the same habit helps ordinary rankings.

Common mistakes to avoid

The first mistake is adding the button on a subdirectory site and expecting results. Only domain-level and subdomain-level sites are eligible, so check the property type before you invest time.

The second is treating Google's 2X figure as your forecast. It is a Google-wide number from internal data, and it covers readers who already chose the source. Your own lift could be far smaller.

The third is changing too much at once. If you add the button, redesign the blog and launch a new series in the same month, you will never know what worked. Change one thing, annotate it and wait.

The fourth is ignoring the Search Console requirement. Without inclusion in Search generative AI features, the AI badge will not appear, no matter how many readers click the button.

A short decision rule for SaaS teams

Use a simple rule. Add the button if you publish timely, original content at least weekly on a domain or subdomain you control, and if your audience already reads you. Skip it, or give it the lowest priority, if your blog is evergreen, sits in a subdirectory or posts rarely.

If you add it, place it where loyal readers will see it, such as the end of a newsletter archive page or a news post. Do not put it in a pop-up. A button that interrupts reading costs you more trust than it gains.

Cekpr's editors would also weigh the cost. A script tag and a div take an hour of developer time. The risk is low, but the same hour might improve a page that actually earns citations.

The practical answer

For most B2B SaaS sites, the Preferred Sources button is a low-cost experiment with a low expected return. It suits sites that publish news-like content on their own domain or subdomain. Everyone else should focus on pages that earn citations for every searcher.

Your next step is a quick eligibility check. Confirm whether your content lives on a domain or subdomain, search for your site in the source preferences tool and decide from there.