How to Add Google Preferred Sources Button to Your Website

Google has released an interactive "Preferred Sources" button that publishers can embed directly onto their websites to allow readers to follow their content without leaving the page [1]. This update replaces older badge designs that previously redirected users to a separate Google preferences tool, a change that aims to reduce friction for publishers looking to increase their presence in Google’s Top Stories, AI Overviews, and AI Mode [2].

Implementing the new button

The new button functions as a single-action flow; once a reader clicks the button, they confirm their choice and are immediately returned to the publisher's article [2]. This contrasts with the previous deeplink method, which required users to navigate to a separate Google preferences screen, manually select a checkbox, and then find their way back to the original site [2].

To implement the standard version, developers must load the library from Google’s publisher script and place a specific div attribute where the button should appear [2]. Google recommends this JavaScript-based approach because it automatically localizes the button language and provides a more seamless user experience [2]. For sites where JavaScript cannot be used, such as in email newsletters or social media posts, Google still supports a standard deeplink that directs users to the source preferences tool [2].

Strategic impact for publishers

While the button makes it easier for users to follow a publication, Google notes that the feature does not guarantee improved search rankings or automatic inclusion in Top Stories [2]. Instead, the tool serves as a signal for personalization, influencing what an individual user sees across Google Search, Discover, and Google News [1].

The scale of this ecosystem has grown significantly, with the number of unique sources selected by users rising to more than 600,000, up from 345,000 in May [1]. Publishers should verify their eligibility in Google’s source preferences tool before deploying the code, as the button only supports domains and subdomains; subdirectories like example.com/blog are not supported targets [2].

What to watch

• Discover Feed Updates: Monitor the rollout of new natural language controls in the Google app, which will allow users to refine their Discover feeds by typing specific requests for topics or links [1].
• AI Integration: Watch for how "preferred" badges appear in AI Overviews and AI Mode, as these placements are increasingly tied to a site's status as a preferred source [1].
• Widget Adoption: For WordPress users, check for custom plugin updates or child theme modifications that simplify the deployment of these buttons across large-scale site architectures [2].

The shift toward a more integrated, single-click follow experience suggests that Google is prioritizing user retention on publisher sites while simultaneously deepening its personalization data. Whether this leads to a measurable increase in traffic for smaller publishers remains the primary question for those adopting the new embed.