How to Add Google’s Preferred Sources Button to Your Website

 

Google’s Preferred Sources Button

Google’s Preferred Sources feature gives readers more control over which publishers they want to see in their search experience. For publishers and news websites, it provides an opportunity to encourage loyal readers to select their publication as a preferred source.

Google has also introduced an easier way for publishers to add this functionality directly to their websites through an embeddable Preferred Sources button.

Instead of sending visitors to Google’s general source-preferences page, the embedded button can provide a more direct experience. This guide explains how Google Preferred Sources works, how to check eligibility, how to add the button, and how to implement it on WordPress.

What Is Google Preferred Sources?

Google Preferred Sources allows individual users to indicate that they want to see content from a particular publication more prominently in relevant Google Search experiences.

It is important to understand what the feature does and does not do.

Adding a publication as a Preferred Source does not automatically improve that website’s rankings for everyone. It also does not guarantee that every article will appear in Top Stories.

Instead, the preference applies to the individual Google user who selects the publication.

Preferred Sources is available globally for Top Stories in supported languages and may also influence source visibility in Google AI experiences, including AI Overviews and AI Mode where those features are available.

Check Your Website’s Eligibility First

Before adding the button, confirm that your publication appears in Google's source-preferences system.

If your publication isn't eligible or doesn't appear there, simply placing the button on your website won't resolve the underlying eligibility issue.

Google supports domains and subdomains as source targets.

For example:

Valid:

  • example.com
  • news.example.com

Not supported as a separate source:

  • example.com/blog

If your publication operates from a subdomain, use the actual subdomain rather than assuming the main domain will work in the same way.

Embedded Button vs. Google Preferred Sources Link

There are two practical ways to direct readers toward the Preferred Sources feature.

1. Embedded Preferred Sources Button

The embedded button can be placed directly on your website. Google handles the interface and localization, while the visitor can add the publication and return to the article.

This generally creates a smoother experience because the reader doesn't have to navigate through Google's broader source-preferences interface.

2. Preferred Sources Deeplink

The second option is a standard Google URL that takes users to the source-preferences page with the publication pre-filled.

The reader still needs to select the publication and confirm the preference.

This option can be particularly useful when you cannot add JavaScript to your website, such as in certain email campaigns, social posts, CMS environments, or promotional content.

For a website where you can install Google's script, the embedded button is generally the more convenient option.

How to Add Google’s Preferred Sources Button

Google provides a JavaScript library that automatically creates the interface.

Add the following script to your site's <head> section or load it through your theme or site plugin:

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

Then place the button wherever you want it to appear:

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

The library recognizes the google-add-preferred-source-btn attribute and renders the appropriate interface.

You don't need to manually add your publication's domain to the standard button.

Use a Dark Theme

The default button uses a light theme. If your website uses a dark background, you can specify the dark theme using the data-theme attribute:

<div google-add-preferred-source-btn data-theme="dark"></div>

This makes it easier to integrate the button into different website designs without creating your own version of Google's interface.

Set a Specific Language

Google normally determines the language automatically based on the reader's browser environment.

If you need to explicitly specify a supported language, you can use the data-lang attribute.

For example:

<div google-add-preferred-source-btn data-lang="en"></div>

Use this only when there is a specific reason to override the automatic language selection.

Use the Deeplink Without JavaScript

If your CMS doesn't allow custom JavaScript, you can use Google's source-preferences URL instead.

Replace example.com with your publication's eligible domain:

https://www.google.com/preferences/source?q=example.com

You can then add it as a normal HTML link:

<p>

  <a href="https://www.google.com/preferences/source?q=example.com">

    Add Example as a Preferred Source

  </a>

</p>

Because it is an ordinary link, this approach can also be used in email newsletters, social media promotions, or other places where JavaScript isn't available.

Add the Preferred Sources Button to WordPress

WordPress publishers can create a reusable widget for the Preferred Sources button.

A custom widget can allow website administrators to choose the button's appearance and alignment without editing the page every time.

The widget can support:

  • Light and dark themes
  • Left, center, or right alignment
  • Automatic loading of Google's JavaScript library
  • Optional GA4/GTM click tracking
  • Multiple widget placements

For implementation, place the widget code in a small custom plugin or a child theme's functions.php file rather than modifying WordPress core files.

The key element rendered by the widget is:

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

For the dark theme:

<div google-add-preferred-source-btn data-theme="dark"></div>

Once the widget is registered, it can be added through the WordPress widget management interface and placed in areas such as an article sidebar or footer.

Track Button Clicks With GA4

Adding the button is useful, but measuring engagement can make the implementation much more valuable.

You can track when visitors begin the Preferred Sources process using Google Tag Manager or Google Analytics.

For example, a custom event can be sent to the site's data layer:

window.dataLayer.push({

  event: 'preferred_source_button_click'

});

In Google Tag Manager, create a Custom Event trigger using:

preferred_source_button_click

You can then send that event to GA4 through a GA4 Event tag.

If your website uses gtag.js without Google Tag Manager, an event can also be sent directly:

window.gtag('event', 'preferred_source_button_click');

Keep in mind that this event records the click that starts the process. It does not confirm that the visitor successfully completed the Preferred Sources selection inside Google.

For accurate reporting, treat the event as an engagement metric rather than a confirmed preference.

Why Preferred Sources Matters for Publishers

Preferred Sources should not be viewed as another traditional ranking tactic.

The feature doesn't give your website a universal ranking boost. Instead, it gives interested readers a way to tell Google that they prefer your publication.

That distinction is important.

A reader who regularly follows your content may be more likely to select your publication, creating an additional opportunity for your articles to appear in their Google experience.

For publishers, the strategy should therefore focus on building reader loyalty and trust, not simply adding a button and expecting an immediate SEO boost.

Best Practices for Using the Button

Before adding Preferred Sources to your website, consider these best practices:

Make the Button Easy to Find

Place it where loyal readers are likely to notice it, such as near the publication information, article header, newsletter area, or sidebar.

Explain What It Does

A simple message such as “Follow us as a Preferred Source on Google” can provide context before the user interacts with the button.

Don't Overuse It

The button should complement your website rather than dominate the user experience. Avoid placing it repeatedly throughout every section of an article.

Measure Engagement

Track button clicks through GA4 or Google Tag Manager to understand whether readers are actually interacting with it.

Continue Investing in SEO

Preferred Sources doesn't replace SEO. Publishers should continue focusing on helpful content, technical performance, credibility, topical authority, structured information, and a strong user experience.

Frequently Asked Questions

1. What is Google Preferred Sources?

Google Preferred Sources allows individual users to select publications they prefer to see in relevant Google Search experiences.

2. Does Preferred Sources improve Google rankings?

Not universally. A Preferred Source selection is associated with the individual user's experience and does not provide a general ranking boost for everyone.

3. Can any website add the Preferred Sources button?

A website should first verify that its publication is eligible and appears in Google's source-preferences system. Adding the button does not create eligibility.

4. What is the difference between the embed and deeplink?

The embedded button is integrated directly into the website and provides a more streamlined user experience. The deeplink sends users to Google's source-preferences page, where they must select and confirm the publication.

5. Can I add Google Preferred Sources to WordPress?

Yes. WordPress publishers can add Google's script and button markup through a custom plugin, child theme, or compatible site implementation. A custom widget can also make theme and alignment settings easier to manage.

6. Can the button be used with a dark website design?

Yes. Google's implementation supports a dark theme through the data-theme="dark" attribute.

7. Can I track Preferred Sources button clicks?

Yes. You can create a custom event through Google Tag Manager or send an event through gtag.js. However, the click only indicates that the visitor started the flow and does not confirm completion.

8. Does Preferred Sources guarantee placement in Top Stories or AI Overviews?

No. Being selected as a Preferred Source does not guarantee that every article will appear in Top Stories, AI Overviews, or AI Mode.

Conclusion

Google's Preferred Sources button gives publishers a straightforward way to encourage loyal readers to select their publication within Google's personalized search experience.

The embedded version generally provides the smoothest website experience, while the deeplink is useful when JavaScript cannot be added.

However, publishers should keep expectations realistic. Preferred Sources is not a shortcut to higher rankings. Its real value comes from giving engaged readers more control over the sources they want to see.

For publishers and digital marketers, the best approach is to combine the feature with strong SEO, useful original content, audience engagement, and ongoing performance measurement.

In modern search, earning a reader's preference can be just as valuable as earning a ranking.

About Alphanumeric Ideas

Alphanumeric Ideas is a digital marketing agency based in Mohali, Punjab, India, providing digital empowerment and online promotion solutions. The agency is recognized among APAC's top digital marketing agencies and is a Google Premier Partner Agency, listed among the top 3% of companies in the APAC region.

With more than nine years of experience, our team of SEO specialists, content writers, graphic designers, and web developers helps businesses strengthen their online visibility and build sustainable digital growth.

Our services include SEO, PPC, Social Media Management, content marketing, website development, and digital branding.

Contact: contact@alphanumericideas.com
Phone: 1800 890 1188
Website:
https://alphanumericideas.com/

Comments

Popular posts from this blog

Why Every Mohali Business Needs Local SEO to Get More Customers

A Range Of Services On Offer From SEO Companies To Boost Up Your Business Web Presence

Google Responds to Cross-Domain Canonical De-Indexing Report