Google shipped an embeddable button on August 20, 2026 which lets readers hand-pick the publishers they want prioritized in Top Stories, AI Overviews, and AI Mode. SEObolt Pro ships full native support for it, with auto-inject on posts, a Gutenberg block, a shortcode, plus a no-JS deep-link for newsletters and social.
When your reader clicks the Preferred Sources button on your site, Google records your domain as one of their preferred sources. From that moment on, Google surfaces your content higher in their Top Stories, AI Overviews, and AI Mode results whenever they run a relevant query.
It's not a general ranking boost, so it 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's available.
AI Overviews and AI Mode are absorbing an increasing share of the clicks which used to go to publisher sites. Preferred Sources is Google's answer, so your readers can explicitly opt in to seeing your work more often. Every button click is a durable relationship signal which survives ranking-algorithm changes.
All configuration lives in SEObolt → Settings → Preferred Sources, so you can enable auto-inject, pick your post types, verify eligibility, grab the newsletter fallback URL, and see a live preview of the actual Google button, all in one place.
Auto-inject is the fastest path to shipping the button sitewide. When you want per-post control, use the Gutenberg block or the shortcode. Every method renders the same native Google button.
Check Enable Auto-Inject and every published post gets the button. Pick post types (Posts, Pages, Products, any custom type), placement (end of content or after the first paragraph), and default theme.
Add the Preferred Source Button (SEObolt) block inside the editor. Pick theme (light / dark / auto) and locale from the sidebar. Live server-side render on the frontend.
Drop [seobolt_preferred_source] into classic editor, Elementor, Divi, or Beaver Builder text widgets. Optional theme and lang attributes.
Google's script won't load in email clients or on most social platforms. SEObolt generates a plain deep-link URL you can paste anywhere, so readers who click it land on Google with your domain pre-filled.
Google's Preferred Sources tool accepts only domain-level and subdomain-level sites. Subdirectory installs (like example.com/blog) aren't eligible. SEObolt reads your home_url() and tells you immediately whether you qualify, with a link to Google's own source-preferences tool for independent verification.
| Site shape | Example | Eligible? |
|---|---|---|
| Bare domain | example.com |
✓ Yes |
| Subdomain | blog.example.com |
✓ Yes |
| Subdirectory install | example.com/blog |
× No |
| Multisite subsite (path-based) | example.com/tenant1 |
× No |
If you're on a subdirectory install and want to use Preferred Sources, the fix is a site move to the root domain, since SEObolt's plugin can't work around Google's eligibility rules.
The rendered button is Google's native UI, a white pill with the multicolored G logo and the text “Add to Preferred Sources.” It looks identical across every site because Google serves it directly via publisher.js.
Signed-in Google users see a confirmation toast; unauthenticated users get a sign-in prompt first (preference is stored per Google account).
Their preferred-sources list is updated instantly. No round-trip through your server, since it all happens between the reader's browser and Google.
The click returns them to where they were reading, so there's no context switch to google.com. Original launch behavior bounced users off-site; the September 2026 update stays in-place.
From that moment forward, your articles are prioritized in their Top Stories carousel, AI Overviews citations, and AI Mode conversational responses whenever they run a relevant query. Google's data: 2× higher click-through when a preferred source is available.
Preferred Sources is included with every SEObolt Pro license. Enable auto-inject, save, and every published post gets the button, with no code, no theme edit, no dev handoff.