Preferred Sources Button (Google)PRO

What Preferred Sources Does

Preferred Sources is a Google-side reader preference. A visitor to your site clicks the button, Google records your domain as one of their preferred sources, and from that moment forward Google surfaces your content higher in that reader’s search results across three surfaces:

• Top Stories, which is the news carousel appearing above regular results on time-sensitive queries.
• AI Overviews, which are the AI-generated summaries at the top of many Google searches. Your site is cited first when relevant.
• AI Mode, which is Google’s conversational search interface. Your content is drawn on preferentially.

It’s not a general ranking boost, so the button doesn’t change what strangers see. It changes what your loyal readers see. Google’s own data shows readers are twice as likely to click through to a preferred source when one is available.

Setting It Up

All configuration lives in a dedicated Settings tab at SEObolt → Settings → Preferred Sources. Four sections, saved with one Save Changes click:

1. Auto-Inject Button

Check Enable Auto-Inject and the button is appended to your published posts automatically, with no shortcode or block needed. Choose which post types get it (Posts, Pages, Products, custom post types), pick placement (end of content or after the first paragraph), and set a default theme (Light / Dark / Auto).

2. Eligibility Check

Google only accepts domain-level and subdomain-level sites in Preferred Sources. A subdirectory install (like example.com/blog) is not eligible, so the button won’t connect readers to your site. The Eligibility Check section reads your site’s home_url() and tells you immediately whether you qualify, with a link to Google’s own source-preferences tool for independent verification.

3. Deep-Link for Newsletters + Social

Google’s button runs on publisher.js, which won’t load in email clients or on most social platforms. The Deep-Link section gives you a plain URL you can paste into email footers, social bios, or newsletter CTAs. Readers who click it land on Google with your domain pre-filled, so one click and they’re added.

4. Live Preview

The preview panel renders the actual Google button in the admin. It connects to Google’s live service, so clicking it will genuinely add your site to your own Google Preferences, which is useful for a quick self-test before you ship the button to your readers.

Three Ways to Place the Button

Auto-inject is the easiest path, but you have full control when you want it. Every placement option renders the same button, so pick whichever matches your content workflow.

Shortcode attributes

The shortcode accepts theme (values: light, dark, auto) and lang (a two-letter locale code, e.g. en, es). Both are optional.

[seobolt_preferred_source]
[seobolt_preferred_source theme="dark"]
[seobolt_preferred_source theme="light" lang="es"]

Eligibility: Which Sites Qualify

Google’s Preferred Sources tool accepts only two site shapes:

SEObolt’s Eligibility Check reads WordPress’s home_url() and warns you if it detects a subdirectory install. If you’re on a subdirectory install and want to use Preferred Sources, the fix is a site move to the root domain, since the button itself cannot work around Google’s eligibility rules.

How Readers See It

The rendered button is Google’s native UI, a white pill with the multicolored G logo and the text “Add to Preferred Sources.” It renders exactly the same on every site because it’s served by Google’s publisher.js.

When a signed-in Google user clicks it, they see a confirmation toast and the button state updates. From that moment, they’re opted into seeing your content prioritized. If the user isn’t signed in, Google prompts them to sign in first, since the preference is stored per Google account.

The button click returns the reader to your page, so there’s no context-switch to google.com. This is a September 2026 update from Google; the original launch bounced users off-site, then back. The current behavior is a stay-on-page confirmation, which is the version SEObolt embeds.

How the Script Loads

The button pulls Google’s publisher.js asynchronously. SEObolt emits it once per page even if you have multiple buttons rendered (auto-inject + a shortcode instance, for example), so there’s no duplicate-script penalty on page weight.

Troubleshooting

Button doesn’t appear on posts after enabling auto-inject

• Confirm your license tier is Pro or higher (Preferred Sources requires the Pro tier).
• Confirm the post is one of the selected post types in Settings → Preferred Sources.
• Confirm the Eligibility Check shows a green Eligible badge. If it says Not eligible, your site is on a subdirectory install and the button will silently no-op.
• If a caching plugin is active, purge the cache after saving settings.

Button renders but clicking does nothing

Almost always a Content Security Policy issue, so see the tip above. Open your browser DevTools console; you’ll usually see a Refused to load the script ‘https://news.google.com/…’ error.

Live Preview shows a placeholder instead of the button

Same CSP or ad-blocker issue, since the preview loads from the same Google endpoint that the live button uses. If the preview works but the frontend doesn’t, that’s a theme-level CSP restricting your frontend script sources.

Privacy Notes

The button loads Google’s publisher.js, which follows Google’s standard analytics behavior, the same as embedding a YouTube video or a reCAPTCHA widget on your site. If you’re operating under GDPR or a similar cookie-consent regime, treat Preferred Sources as a Google-provided third-party embed and either (a) load it only after consent, or (b) list it under “Google integrations” in your cookie policy.

SEObolt itself doesn’t send any data to Google, since the button is a standard Google embed. Nothing is tracked or reported back to your site.