{"id":2830,"date":"2026-08-22T14:33:00","date_gmt":"2026-08-22T14:33:00","guid":{"rendered":"https:\/\/dmarketertayeeb.com\/blog\/google-preferred-sources-button-guide\/"},"modified":"2026-08-22T14:33:00","modified_gmt":"2026-08-22T14:33:00","slug":"google-preferred-sources-button-guide","status":"publish","type":"post","link":"https:\/\/dmarketertayeeb.com\/blog\/google-preferred-sources-button-guide\/","title":{"rendered":"Google Preferred Sources Button: How Publishers Can Add It Safely"},"content":{"rendered":"
\n\n\n

Short answer:<\/strong> Google has updated its Preferred Sources documentation with a custom, interactive button that publishers can place on their sites. If a publication is eligible and a reader selects it as a preferred source, that publication may be more visible in relevant Top Stories and may receive a preferred badge in AI Mode and AI Overviews. The button is not a ranking shortcut. Check eligibility first, choose the simplest implementation your site can support, and measure the reader action rather than promising more rankings or AI citations.<\/p>\n\n\n\n

Checked against Google’s documentation and status pages on 22 August 2026. Google can change the feature, availability, and implementation details after this date.<\/em><\/p>\n\n\n\n

What changed on 20 August 2026?<\/h2>\n\n\n\n

Google Search Central’s documentation changelog says the Preferred Sources guide was updated on 20 August 2026 with instructions for a new custom, interactive button. The intended journey is simple: a reader clicks a control on a publisher’s page, adds that publication as a preferred source in Google Search, and returns to the page they were reading.<\/p>\n\n\n\n

This matters because Preferred Sources now connect a publisher’s own audience-building work with more than one Search surface. Google says a selected source is more likely to appear in relevant Top Stories<\/a> with a preferred badge. The source can also be highlighted with a preferred badge in AI Mode and AI Overviews for users who selected it.<\/p>\n\n\n\n

The opportunity is therefore a reader preference signal, not a new form of on-page SEO. Your content still needs to be useful, indexable, relevant to the query, and eligible for the Search surface in which it might appear.<\/p>\n\n\n\n

What the Preferred Sources button does\u2014and does not do<\/h2>\n\n\n\n
\n\n\n
What it can do<\/th>What it cannot promise<\/th><\/tr><\/thead>\n
Guide an eligible reader into Google’s source-preferences flow.<\/td>Guarantee a ranking, Top Stories placement, AI Overview link, or AI Mode citation.<\/td><\/tr>\n
Help a selected publication stand out with a preferred badge when Google’s relevant Search or AI surfaces show it.<\/td>Replace relevance, prominence, authoritativeness, technical eligibility, or people-first content.<\/td><\/tr>\n
Give publishers a clear audience-promotion action on a page, in a newsletter, or in a social promotion when using the deeplink.<\/td>Make an ineligible subdirectory appear as an eligible domain-level source.<\/td><\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n\n\n\n

Source: DMT synthesis of Google’s Preferred Sources guide and News Publisher Help, accessed 22 August 2026.<\/em><\/p>\n\n\n\n

Google’s separate guidance for AI features says existing SEO best practices remain relevant. There are no additional technical requirements or special schema needed for AI Overviews or AI Mode, and meeting the requirements does not guarantee crawling, indexing, or serving. Treat the Preferred Sources control as an audience and discovery mechanism that sits alongside SEO\u2014not as a technical workaround for weak content.<\/p>\n\n\n\n

Check eligibility before adding the control<\/h2>\n\n\n\n

Start with Google’s source preferences tool<\/a>. Search for the publication’s site and confirm that the domain appears before promoting a button or deeplink.<\/p>\n\n\n\n

The documentation describes domain-level and subdomain-level eligibility. For example, https:\/\/www.example.com\/<\/code> and https:\/\/code.example.com\/<\/code> can be eligible, while https:\/\/www.example.com\/blog<\/code> is a subdirectory and is not eligible as its own Preferred Source. That distinction matters for publishers whose content lives in a folder on a larger corporate domain.<\/p>\n\n\n\n

Google says the feature is available globally for Top Stories in the languages where Google Search is available. Preferred Sources can also appear in AI Mode and AI Overviews in the languages and locales where those features are available. Availability of the surface is not the same as guaranteed inclusion for an individual page.<\/p>\n\n\n\n

Option 1: add Google’s standard two-line button<\/h2>\n\n\n\n

For most publishers, Google’s recommended implementation is the standard JavaScript button. Add the library, preferably in the page <head><\/code>, then place the button container where readers can understand its purpose. The library renders a localized Google-styled control and returns the reader to the page after the flow.<\/p>\n\n\n\n

<script async src=\"https:\/\/news.google.com\/swg\/js\/v1\/publisher.js\"><\/script>\n<div google-add-preferred-source-btn><\/div><\/code><\/pre>\n\n
Code attribution: these snippets are adapted from Google’s Preferred Sources guide<\/a>. The documentation page states that its code samples are licensed under Apache 2.0; retain the source link and adapt the examples to your implementation.<\/em><\/p>\n\n\n\n
Google also documents optional theme and language attributes:<\/p>\n\n\n\n
<div google-add-preferred-source-btn data-theme=\"dark\"><\/div>\n<div google-add-preferred-source-btn data-lang=\"en\"><\/div><\/code><\/pre>\n\n
Use the theme that fits the surrounding page. Let the browser determine the reader’s language unless there is a defensible reason to override it. If you use a fixed language, confirm that it does not create a confusing experience for an international audience.<\/p>\n\n\n\n
Option 2: connect a custom control with advanced JavaScript<\/h2>\n\n\n\n
The advanced implementation is for a site that needs its own design system, a custom trigger, or a framework-specific integration. Google’s module example imports the library, initializes it, and calls preferredSource.addPreferredSource()<\/code> from the site’s own click handler.<\/p>\n\n\n\n
import { preferredSource } from\n  \"https:\/\/news.google.com\/swg\/js\/v1\/publisher.mjs\";\n\npreferredSource.init({\n  theme: 'light',\n  lang: 'en'\n});\n\nconst button = document.querySelector('#myButton');\nbutton.onclick = () => {\n  preferredSource.addPreferredSource();\n};<\/code><\/pre>\n\n
Google also documents an IIFE callback-queue approach for sites that load the standard script but want to prevent automatic rendering. In that version, the script carries preferred-sources-control=\"manual\"<\/code>, and the PREFERRED_SOURCE<\/code> queue initializes the library and binds the site’s trigger.<\/p>\n\n\n\n
<script async preferred-sources-control=\"manual\"\n  src=\"https:\/\/news.google.com\/swg\/js\/v1\/publisher.js\"><\/script>\n<script>\n(self.PREFERRED_SOURCE = self.PREFERRED_SOURCE || []).push(\n  function(preferredSource) {\n    preferredSource.init({ theme: 'light', lang: 'en' });\n    document.querySelector('#myButton').addEventListener('click', () => {\n      preferredSource.addPreferredSource();\n    });\n  }\n);\n<\/script><\/code><\/pre>\n\n
Do not select the advanced path just to make a button look different. It adds a JavaScript dependency and another surface to test. Use it when the custom trigger genuinely improves the reader journey, then test loading, keyboard access, consent behavior, and the return path in the browsers and devices that matter to your audience.<\/p>\n\n\n\n
Option 3: use a deeplink when JavaScript is not practical<\/h2>\n\n\n\n
If your CMS cannot support the interactive control, Google provides a deeplink to the source-preferences tool. Replace the example domain with the eligible publication domain:<\/p>\n\n\n\n
https:\/\/www.google.com\/preferences\/source?q=example.com<\/code><\/pre>\n\n
That URL can be used as a normal text link, a button styled by your design system, or a clearly labelled image link. It can also be shared in a newsletter or social promotion. Make the label explicit\u2014\u201cAdd [Publication] as a Preferred Source\u201d\u2014so readers know that the link changes their Google Search preference, rather than subscribing to an email list.<\/p>\n\n\n\n
For a WordPress implementation, keep the link or button close to the reader action it supports, and use the exact domain that appears in Google’s source-preferences tool. A plugin or shortcode may simplify placement, but it does not change Google’s domain-level eligibility rule.<\/p>\n\n\n\n
A safe publisher rollout checklist<\/h2>\n\n\n\n
\n\n\n
Check<\/th>What to verify<\/th><\/tr><\/thead>\n
Eligibility<\/td>The publication appears in Google’s source-preferences tool and the promoted domain\/subdomain matches the reader’s page.<\/td><\/tr>\n
Placement<\/td>The control is visible after the reader understands the publication’s value, without obscuring navigation, consent, or the article.<\/td><\/tr>\n
Implementation<\/td>Use the standard button unless a custom trigger or a no-JavaScript environment justifies the advanced or deeplink path.<\/td><\/tr>\n
Performance and privacy<\/td>Review the external script, CSP, consent requirements, loading behavior, and mobile layout with the site’s normal release process.<\/td><\/tr>\n
Measurement<\/td>Track button clicks and return behavior as first-party events where permitted; do not claim that every click becomes a Search impression or visit.<\/td><\/tr>\n
Search quality<\/td>Keep pages crawlable, indexable, internally linked, and useful. The control cannot compensate for thin, misleading, or policy-violating content.<\/td><\/tr>\n<\/tbody>\n<\/table>\n<\/figure>\n\n\n\n
Source: DMT-created rollout checklist based on Google Search Central’s Preferred Sources, AI features, and News Publisher guidance.<\/em><\/p>\n\n\n\n
Place the control where a returning reader can act on a positive experience\u2014near a publication description, at the end of a high-value article, or in a clearly labelled site-support module. Avoid adding it to every surface before you know whether the placement helps or interrupts the reader journey.<\/p>\n\n\n\n
What should marketers expect after implementation?<\/h2>\n\n\n\n
Google’s 27 May 2026 product announcement<\/a> reported that users were twice as likely to click a Preferred Source and that more than 345,000 unique sources had been selected at that time. A separate 20 August 2026 product post<\/a> reported more than 600,000 unique sources selected. Both figures are Google-reported aggregate observations, not site-level causation, a forecast, or a guarantee. The practical expectation is narrower: a reader who chooses the site has told Google that the site is useful to that reader, so relevant content may be easier for that user to notice on supported surfaces.<\/p>\n\n\n\n
Do not turn that expectation into a reporting KPI such as \u201cPreferred Sources increased rankings\u201d unless your data and a controlled analysis can support the claim. A button click is an audience action. Search visibility is affected by query relevance, content quality, freshness where relevant, authority, technical eligibility, competition, and Google’s serving decisions.<\/p>\n\n\n\n
For the broader AI-search context, compare the implementation with DMT’s Google AI Overviews and SEO guide<\/a> and Google AI Mode for marketers<\/a>. For measurement, use the Google Search Console generative AI report guide<\/a>, while remembering that Search Console and Analytics cannot attribute every preference decision to a later impression.<\/p>\n\n\n\n
How this fits an SEO and content workflow<\/h2>\n\n\n\n
The control is most useful when the publication has a clear reason for readers to return. That means keeping an editorial promise, publishing original and helpful material, and making related work easy to find. DMT’s Generative Engine Optimization (GEO) guide<\/a> covers the content-side implications of AI-search discovery; the technical SEO for AEO guide<\/a> covers the crawlability and page-structure fundamentals that remain relevant.<\/p>\n\n\n\n
Keep feature news separate from algorithm-update speculation. If you are assessing traffic changes around a Google ranking release, use the Google algorithm updates running log<\/a> and compare a sensible post-rollout window rather than attributing every movement to a new button.<\/p>\n\n\n\n
Frequently asked questions<\/h2>\n\n\n\n
Does the Preferred Sources button improve rankings?<\/h3>\n\n\n\n
Not directly. Google describes it as a way to guide readers to select a preferred source. A selected site may be more visible in relevant Top Stories and may carry a preferred badge in AI Mode or AI Overviews, but Google does not promise a ranking boost, inclusion, or traffic.<\/p>\n\n\n\n
Can a blog subdirectory become a Preferred Source?<\/h3>\n\n\n\n
Google’s guide says domain-level and subdomain-level sites are eligible, while a subdirectory such as example.com\/blog<\/code> is not eligible as a separate source. Check the source-preferences tool for the exact domain or subdomain you want readers to select.<\/p>\n\n\n\n
Do I need the button to appear in Google Preferred Sources?<\/h3>\n\n\n\n
No. Google explicitly says the documented methods are ways to guide readers and are not required for a publication to appear as a preferred source. The button is an audience-promotion option, not an eligibility requirement.<\/p>\n\n\n\n
Bottom line<\/h2>\n\n\n\n
The 20 August 2026 documentation update gives publishers a concrete way to invite readers into Google’s Preferred Sources flow. Start by checking eligibility, use the standard two-line button unless you have a real reason to customise it, and use the deeplink when JavaScript is not practical. Then evaluate the reader action and the quality of the returning audience\u2014without promising rankings, AI citations, or guaranteed traffic.<\/p>\n\n\n\n
Official sources:<\/strong> Google’s Preferred Sources guide<\/a>; Google Search Central documentation updates<\/a>; AI features and your website<\/a>; News Publisher Help<\/a>; and Google’s 27 May 2026 product announcement<\/a> and 20 August 2026 product post<\/a>. Accessed 22 August 2026.<\/p>\n\n\n<\/article>","protected":false},"excerpt":{"rendered":"
Google now documents a Preferred Sources button. Learn who is eligible, how to add it, and why it is not a ranking shortcut.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[177,212,182],"tags":[260,185,273,371,363,261,214],"class_list":["post-2830","post","type-post","status-publish","format-standard","hentry","category-digital-marketing","category-google-updates","category-seo","tag-ai-mode","tag-ai-overviews","tag-ai-search","tag-google-search","tag-google-updates","tag-search-personalization","tag-seo-2026","no-featured-image"],"_links":{"self":[{"href":"https:\/\/dmarketertayeeb.com\/blog\/wp-json\/wp\/v2\/posts\/2830","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dmarketertayeeb.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dmarketertayeeb.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dmarketertayeeb.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dmarketertayeeb.com\/blog\/wp-json\/wp\/v2\/comments?post=2830"}],"version-history":[{"count":0,"href":"https:\/\/dmarketertayeeb.com\/blog\/wp-json\/wp\/v2\/posts\/2830\/revisions"}],"wp:attachment":[{"href":"https:\/\/dmarketertayeeb.com\/blog\/wp-json\/wp\/v2\/media?parent=2830"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dmarketertayeeb.com\/blog\/wp-json\/wp\/v2\/categories?post=2830"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dmarketertayeeb.com\/blog\/wp-json\/wp\/v2\/tags?post=2830"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}