By Cody Wise, Founder, Wise Media. Published 16 September 2026.
Google shipped an embeddable Preferred Sources button on 20 August 2026, and every guide written since tells you how to install it. Almost none asks whether a local service business should. Short answer: install it if you publish regularly, but expect close to nothing, because the surface it actually weights is Top Stories, and “roof repair Calgary” is not a news query.
Summary
Preferred Sources lets a Google user mark sites they want to see more of. For sites they select, Google says content is “more likely to appear in Top Stories, highlighted with a preferred badge,” and “can be highlighted with a preferred badge” in AI Mode and AI Overviews. Note the asymmetry, because it decides everything: Top Stories gets a weighting effect, AI surfaces get a label. Google has never claimed that being a preferred source makes you more likely to be cited in an AI Overview.
The install is one script tag and one div. It is free, it takes five minutes, and the only real cost of adding it is the belief that it will do something it will not. This article gives the honest verdict for non-publishers, the eligibility gate that disqualifies a lot of small sites, and the correct code, because five of the nine pages currently ranking for the install query publish code that does not work.
Table of contents
- What Preferred Sources actually does, surface by surface
- The eligibility gate that disqualifies subdirectories
- The second gate nobody leads with
- Should a local service business bother? The honest verdict
- How to install it correctly, with working code
- The deeplink, and when it beats the button
- Is it a ranking signal?
- The numbers, and the growth percentage you should not publish
- Common mistakes on pages currently ranking for this
- Where to spend the hour instead
- FAQ
What Preferred Sources actually does
Preferred Sources is a personalization feature. A signed-in Google user picks sites they want to see more of, and Google adjusts what that user sees. It does nothing for anyone who has not picked you.
Google’s documentation is precise about which surfaces are affected, and the precision is worth quoting rather than paraphrasing:
When a user selects your site as a preferred source, your content is more likely to appear in “Top Stories”, highlighted with a “preferred” badge. In AI Mode and AI Overviews, your content can be highlighted with a “preferred” badge for users who have selected your site as a preferred source.
Read those two sentences against each other. Top Stories: more likely to appear. AI Mode and AI Overviews: can be highlighted with a badge. One is a retrieval effect. The other is a display treatment applied to content that was already going to be shown.
| Surface | Effect | What Google claims |
|---|---|---|
| Top Stories | Weighting | “More likely to appear,” with a preferred badge |
| AI Overviews | Labelling only | “Can be highlighted with a preferred badge” |
| AI Mode | Labelling only | “Can be highlighted with a preferred badge” |
| Discover | Not a stated surface | No claim. At least one ranking page says otherwise. |
| Google News | Not a stated surface | No claim. |
| Standard blue-link results | No stated effect | No claim. |
Every agency page conflating these into “get into AI Overviews” is overselling a badge as a citation.
Availability, including Canada
Preferred Sources launched in the United States and India on 12 August 2025, expanded to all languages globally on 30 April 2026, and extended into AI Overviews and AI Mode on 27 May 2026. The embeddable button shipped 20 August 2026.
There is no Canada-specific launch. Google’s documentation says the feature “is available globally for the Top Stories feature in all languages where Google Search is available,” and that preferred sources can appear in AI Mode and AI Overviews in all languages and locales where those features are available. So it is live for Canadian users by inclusion, not by announcement. If a page tells you Preferred Sources “launched in Canada” on a specific date, it is inventing one.
The eligibility gate: domains and subdomains only
Only domain-level and subdomain-level sites can appear in the source preferences tool. A subdirectory cannot.
Google’s wording: “Only domain-level and subdomain-level sites are eligible to appear in the source preferences tool. For example, https://www.example.com/ and https://code.example.com/ are eligible for preferred sources, but the subdirectory https://www.example.com/blog isn’t eligible.”
This catches more businesses than it sounds like it should. If your content lives on a path under a parent brand, a franchise domain, or a marketplace, you are not separately selectable. The unit of selection is the whole domain.
How to check in thirty seconds
- Open google.com/preferences/source while signed in.
- Type your domain into the tool’s search box.
- If it appears, you are selectable. If it does not, installing a button will not change that.
Do this before you touch any code. It is the whole go or no-go decision and it takes less time than reading the rest of this section.
The second gate nobody leads with
Buried in Google’s end-user help page is a single line that decides the question for most small business sites: “Sources that aren’t updated regularly may not be available.”
That is the real filter. A Calgary roofing company with three blog posts from 2023 is not a source Google’s system has any reason to surface, and it may not appear in the tool at all. The complementary line, from Google’s May 2026 announcement, is the pro-inclusion one: “Any website that publishes fresh content is eligible.”
Put them together and you get a clean rule. Preferred Sources is open to non-publishers, conditional on actually publishing. Not on being a newspaper, but on being a site that ships content on a cadence.
Should a local service business bother? The honest verdict
Yes, install it, with realistic expectations. It is free, it takes five minutes, and there is no downside. But it will almost certainly do very little, and the reason is structural rather than a matter of execution.
The one surface that gets a genuine weighting effect is Top Stories. Google’s own help documentation describes Top Stories as appearing “when a news-oriented search query is detected.” A homeowner searching “roof repair Calgary,” “emergency plumber near me,” or “Airbnb cleaning company Calgary” is not issuing a news-oriented query. No Top Stories module appears. The weighting has nothing to weight.
What remains for a service business is the badge in AI Overviews and AI Mode, which is a display treatment for people who already chose you. That is a retention mechanic, not an acquisition one. It helps a reader who already likes you recognise you faster. It does not put you in front of anyone new.
Who actually gets value from this
| Business type | Realistic value | Reasoning |
|---|---|---|
| News publisher, trade press, local news site | High | Top Stories is their native surface. This is who the feature was built for. |
| Industry blog or newsletter with a real cadence and a subscriber base | Moderate | Some news-adjacent query overlap, plus a genuine audience likely to opt in. |
| Agency or consultancy publishing several times a week | Low to moderate | Occasional news-reactive coverage can surface. Mostly a loyalty signal. |
| Local service business, trades, home services | Very low | Queries are local and transactional. Top Stories does not fire. |
| Ecommerce | Very low | Product queries are commercial, not news-oriented. |
| Site with no regular publishing | None | May not appear in the source preferences tool at all. |
The part that is genuinely worth doing
There is one non-Google benefit that is real. A reader who taps that button has performed a deliberate act of preference. That is a stronger loyalty signal than a newsletter signup, because it costs them nothing and gains them nothing except seeing you more often. If you already run an email list or a client newsletter, the deeplink version of this belongs in your footer alongside the subscribe link.
Just do not build a content strategy around it, and do not let anyone sell you an “AI visibility” package on the back of it.
How to install it correctly
Google publishes three methods. Most guides get at least one detail wrong, so here is the working version.
Method 1: the standard button, recommended
Two pieces. The script, preferably in the head:
<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>And the container, placed wherever you want the button to render:
<div google-add-preferred-source-btn></div>That second line is the one several ranking guides omit entirely, which means their readers install the script and see nothing render.
Two optional attributes on the div:
data-theme="dark"ordata-theme="light". Light is the default.data-lang="en". Defaults to the browser language. Google publishes the supported language codes as a CSV in its documentation.
The behavioural advantage of this method, in Google’s words, is that it “lets readers seamlessly add your site as a preferred source and return to where they left off on your page.” The reader never leaves.
Method 2: the advanced JavaScript path
If you need to control when the button initialises, Google supports an ESM import of publisher.mjs, or an IIFE pattern using preferred-sources-control="manual" with the self.PREFERRED_SOURCE callback queue, then calling preferredSource.init() and preferredSource.addPreferredSource(). Google’s note on this path is worth repeating: “The end-user UI flow remains the same.” You gain timing control, nothing else. Most sites do not need it.
Method 3: the deeplink
A plain URL, formatted with your domain:
https://www.google.com/preferences/source?q=example.comWrapped as a link:
<a href="https://www.google.com/preferences/source?q=example.com">Add as Preferred Source</a>This sends the user to the source preferences tool where they add your site and confirm. Google never claims it returns them to your page, and it does not. That is the trade-off.
The deeplink has one advantage the button cannot match: it works outside your website. Google explicitly sanctions using it “in your social posts, email newsletters, or promotions.” The JavaScript button cannot go in an email. For most small businesses, the deeplink in a newsletter footer will drive more adds than the button on a page nobody scrolls to the bottom of.
Badge assets
Google provides official translated badge graphics as a downloadable zip, linked from its Preferred Sources documentation, and explicitly permits you to design your own custom promotion badge instead. There are no published branding rules, no usage restrictions and no minimum sizing on that page. If a guide tells you Google mandates specific badge treatment, it is inventing rules. Notably, not one of the nine pages currently ranking for the install query links the official asset bundle at all.
The line that changes the whole calculation
At the end of its implementation section Google writes: “These methods are examples of how you can build your audience and help people find your site as a preferred source. It’s not required to do them in order to appear as a preferred source.”
The button is a promotion tool, not a registration mechanism. You are already selectable, or you are not, based on the eligibility gates above. Installing the button does not enrol you in anything. No competitor page currently states this, and it is the single most useful sentence in the documentation.
Is it a ranking signal?
No. It is per-user personalization, and there is no documented effect on anyone who has not selected you.
Google’s documentation scopes every stated benefit to “a user,” “them,” and “users who have selected your site.” There is no statement, anywhere, extending the effect beyond the selecting user.
Google’s John Mueller was asked about it publicly and declined to extend the claim past the documentation, quoting the then-current doc text and adding that he did not think it would make sense to show low-quality content to users purely on the basis of a preference, while confirming it does help a user see their preferred sources more. In other words: quality systems still apply, and the effect is a user-level preference, not a site-level boost.
Anyone selling a local business on Preferred Sources as “a new ranking factor” is wrong, and the documentation is short enough that you can verify it yourself in two minutes.
The numbers, and the one you should not publish
Google has published a source count three times:
| Date | Figure | Google’s wording |
|---|---|---|
| 30 April 2026 | 200,000 | “people have already selected over 200,000 unique sites” |
| 27 May 2026 | 345,000 | “people have already selected more than 345,000 unique sources” |
| 20 August 2026 | 600,000 | “So far, people have already selected more than 600,000 unique sources” |
Two pages currently ranking on this topic describe 200,000 as “the May 2026 figure.” It is the April figure. May was 345,000. One of them then computes a growth percentage off the wrong baseline.
Do not publish a growth percentage from these numbers at all, even with the right baseline. Every figure Google gives is an open-ended floor: “over,” “more than.” A percentage derived from two floors is arithmetically meaningless. Cite 600,000-plus as of 20 August 2026 and stop there.
The “twice as likely to click” claim
Google has stated twice that “readers are twice as likely to click through to a site after marking it as a Preferred Source.” What that measures is the behaviour of users who already chose you. It is not a site-level traffic lift, and Google publishes no methodology, sample size or timeframe alongside it. Notably, the August button announcement does not repeat the claim.
Frame it correctly: readers who opt in click twice as often. Not: adding the button doubles your traffic.
Common mistakes on pages currently ranking for this
I read the top results for the install queries before writing this. The defect rate is unusually high, so here is what to watch for if you are cross-checking elsewhere.
- Missing the div. At least one guide never publishes
<div google-add-preferred-source-btn></div>at all, so following it renders nothing. - Curly quotes. Two pages serve code with smart quotes, so nothing pastes and runs.
- Unfilled placeholders. One ships a literal bracketed placeholder in place of the actual deeplink.
- Code as a screenshot. One 3,000-word how-to publishes the embed as an image.
- Wrong launch date. One page states three times that Preferred Sources launched in May 2026. It launched August 2025 in the US and India.
- Invented surfaces. The same page lists Discover and Google News as affected. Google states Top Stories, AI Overviews and AI Mode.
- Fabricated features. One page claims Google provides built-in event tracking for the button. It does not. The same page carries an unattributed quote from “a digital marketing expert.”
- Bad tracking advice. One suggests a stock Google Tag Manager click trigger will pick up button clicks on its own. The badge is injected by Google’s script after page load, so a standard click trigger will not reliably fire. If you want click data, bind after the script initialises or use the deeplink with a tracked outbound event.
On WordPress plugins
Several third-party WordPress plugins now exist for this. Google’s documentation recommends none of them and does not use the word “plugin” anywhere on the page. Given the official install is one script tag and one div, a plugin is added attack surface and another update dependency for zero functional gain, unless you specifically want click analytics or conditional display rules.
If you are running a WordPress site, put the script in your theme’s header hook and the div in a footer widget or block. That is the whole job. If your site runs Elementor, a single HTML widget handles the div. Worth reading alongside our guide to what a WordPress maintenance plan should include, since every optional plugin is a line item on that surface.
How a user adds a preferred source themselves
Worth knowing, because it tells you how rare the behaviour is.
- Search a recent newsworthy topic so a Top Stories module appears.
- Click the cards star icon to the right of the Top Stories header.
- Search for sources, tick the checkbox, click Reload results.
Alternatively: profile picture, then Search personalization, then Source preferences. Selections made either way apply to Top Stories and to AI Mode and AI Overviews, and they persist across browsers when signed in.
There is no limit on how many sources a user can select. Google noted that over half of its early users chose four or more. Any page claiming a cap is fabricating it.
Notice that the native path requires the user to already be looking at a news query. That is precisely why the embeddable button exists, and also why a service business will not accumulate selections passively.
Where to spend the hour instead
Install the button. It costs five minutes. Then spend the rest of the hour on something with an actual return for a local service business.
- Directory profiles. AI answers to “best [service] in [city]” are assembled overwhelmingly from third-party directories, not from brand websites. An unclaimed or unreviewed profile on the directories your category actually uses is worth more than any on-site widget.
- Reviews on the profiles you already have. A live profile with zero reviews is a ranking liability, not a neutral.
- Organization and Person schema with
sameAs. If your brand name collides with other companies, entity disambiguation moves AI answers in a way a preference button never will. - Publishing on a cadence. This is the one that also unlocks Preferred Sources eligibility, since sources that are not updated regularly may not be available. It is the prerequisite, not the alternative.
Research on AI citation consistently finds that brand mentions across third-party content predict citation far more strongly than owned-media volume does. That is an uncomfortable finding for an agency that sells content, and it is still the right thing to tell a client.
Frequently asked questions
Should my small business add the Google Preferred Sources button?
Add it if you publish content regularly, because it is free and takes five minutes. Expect very little from it. The only surface that receives a genuine weighting effect is Top Stories, which appears on news-oriented queries, and local service searches are not news-oriented. For AI Overviews and AI Mode, Preferred Sources only adds a badge for users who already selected you, which is a retention effect rather than an acquisition one.
Is Preferred Sources available in Canada?
Yes. Google states the feature is available globally for Top Stories in all languages where Google Search is available, and in AI Mode and AI Overviews in all languages and locales where those features are available. There was no separate Canadian launch announcement, so any page citing a Canada launch date is inventing one.
Does adding the button register my site with Google?
No. Google’s documentation states plainly that these methods are examples of how to build your audience and that it is not required to do them in order to appear as a preferred source. Eligibility depends on being a domain or subdomain level site that publishes regularly. The button only makes it easier for readers to select you.
Is Preferred Sources a Google ranking factor?
No. It is per-user personalization. Google’s documentation scopes every stated effect to users who have selected your site, and there is no documented effect on anyone else. John Mueller declined publicly to extend the claim beyond the documentation.
Why does my site not appear in Google’s source preferences tool?
Two likely reasons. First, only domain-level and subdomain-level sites are eligible, so a subdirectory such as example.com/blog will never appear. Second, Google’s help documentation notes that sources which are not updated regularly may not be available. A site that has not published in months may simply not be listed.
Will Preferred Sources get me cited in AI Overviews?
Google has never claimed that. The documentation says your content “can be highlighted with a preferred badge” in AI Mode and AI Overviews for users who selected you. That is a label applied to content already being shown, not a mechanism for being retrieved. The “more likely to appear” language attaches only to Top Stories.
Do I need a WordPress plugin for this?
No. Google recommends no plugin and does not mention plugins in its documentation. The install is one script tag in the head and one div where you want the button. Several third-party plugins exist, but they add maintenance and attack surface for no functional gain unless you specifically need click analytics or display rules.
How many sources can a user select?
There is no limit. Google stated at launch that users can select as many sources as they like, and that over half of its early users chose four or more.
The bottom line
Preferred Sources is a good feature aimed at a specific problem: readers who want their chosen publications back in a results page that increasingly summarises away the source. For a publisher, that is meaningful. For a Calgary roofer, it is a badge on a surface their customers never see.
Check whether you appear in the source preferences tool. If you do, drop in the two lines, put the deeplink in your newsletter footer, and move on. The honest version of this recommendation is worth more than an implementation guide that pretends the upside is larger than Google says it is.
Want the version of this that actually moves the needle?
Wise Media builds search and answer-engine visibility for Canadian businesses, which mostly means entity schema, third-party presence and a publishing cadence you can sustain, rather than widgets. If you want an honest audit of where your visibility is actually leaking, we will tell you which levers matter for your category and quote the work in CAD before we start.
Request an audit here, or look at our website growth packages and website build packages.
Related reading: what Google’s AI search report will not tell you, and what Bing’s will, how to fix wrong information about your business in AI answers, which AI crawlers to allow in robots.txt, and using Search Console’s Instagram and TikTok reporting.
Sources
- Google Search Central, Preferred Sources documentation
- Google, Preferred Sources launch announcement (12 August 2025)
- Google, extension of Preferred Sources into AI Mode and AI Overviews (27 May 2026)
- Google, embeddable Preferred Sources button announcement (20 August 2026)
- Google Search Help, choose preferred sources
- Google source preferences tool