By Rahul S., founder of SearchCounselCo. Last updated August 22, 2026.

What changed on August 20, 2026?

Google released a new interactive Preferred Sources button for publishers on August 20, 2026. A reader can use it on a publisher’s site, add that site to their source preferences, and return to the page they were reading. Google said more than 600,000 unique sources had been selected by that date.

The setting can affect the signed-in reader’s experience in Top Stories, AI Overviews and AI Mode. It is best understood as an audience-retention feature inside Google, not as a replacement for relevance, freshness, quality or the technical conditions required to appear. Those fundamentals still matter, as does understanding how AI search systems choose sources.

Google previously reported that people were twice as likely to click through to a site after marking it as a Preferred Source. That is Google’s aggregate observation about users who had already expressed a preference. It does not establish that installing the button doubles a publisher’s traffic, and it does not forecast the result for any individual site.

Check eligibility before adding any code

Open Google’s source preferences tool, replace example.com with your publication’s domain, and confirm the source appears. Do this before spending development time on the button.

• Use the source-level host. Enter a domain or subdomain, without an article path, query string or fragment.
• Do not use a subdirectory. Google says example.com/blog cannot be selected separately. If editorial content lives there, the eligible source would be the domain.
• Check publishing activity. Google’s user help says sources that are not updated regularly may be unavailable.
• Confirm the correct entity. Check the displayed name and favicon so readers are not sent to a similarly named or unintended source.

How to add the Google Preferred Sources button

Option 1: Use Google’s standard JavaScript button

Google recommends the standard JavaScript implementation because the button is automatically localized and the flow returns the reader to the page. Add this library once, preferably through your theme, tag manager governance process or a controlled header-injection method:

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

Then place this container where the button should appear:

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

The code shown here is escaped for safe display in WordPress. Do not paste the library repeatedly into every article body. Load it once at template level, then add the container in the reusable location where the CTA should render.

Option 2: Set a dark theme or fixed language

The default button uses a light theme and the reader’s browser language. Google documents data-theme and data-lang overrides:

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

Override the language only when the page’s audience requires it. Automatic localization is usually the less brittle default.

Option 3: Use the deeplink fallback

If your CMS strips JavaScript or your security policy blocks the external library, use a normal link:

<a href="https://www.google.com/preferences/source?q=example.com" target="_blank" rel="noopener">Add us as a Preferred Source on Google</a>

The deeplink sends the reader to Google’s source-preferences tool to confirm the choice. Unlike the recommended interactive button, it does not provide the same documented return-to-page flow. Use Google’s downloadable assets or your own accessible visual treatment if a graphic button is preferable.

WordPress implementation checklist

1. Back up the theme or use a child theme/staging environment.
2. Load Google’s library once through a controlled header or code-injection mechanism.
3. Add the button container to a reusable post template, author box or post-footer pattern.
4. Clear page and CDN caches, then test while signed in and signed out.
5. Test keyboard focus, mobile wrapping, dark mode and common consent/security configurations.
6. Confirm that only one visible CTA appears and that it opens the intended source.

If the implementation sits within a broader visibility plan, connect it to the site’s AI SEO framework instead of treating one button as the strategy.

Where should the button go?

Place the CTA where returning readers have enough context to recognize the publication and understand the benefit. The best starting point for most editorial sites is after the article or beside existing follow and newsletter actions—not above the answer the reader came for.

• Article footer: high relevance, reusable and unlikely to interrupt reading.
• Author or publication box: useful when trust in a named expert or newsroom drives loyalty.
• Newsletter confirmation page: reaches readers who have already taken a loyalty action.
• Site footer: broad coverage, but lower context and likely lower engagement.
• Inline after a strong section: worth testing on long guides, provided it does not look like an ad or block the content.

Do not use a modal that fires before a reader can evaluate the content. Do not imply that clicking guarantees rankings, preferred badges or all future articles. A simple label such as “See more of our reporting in Google” followed by the official button is clear enough.

How to measure Preferred Sources without fooling yourself

The current Google publisher guide does not document a publisher-facing report that counts how many users selected a site. Your site can measure CTA interactions; it cannot assume that every click became a confirmed preference.

Create a GA4 event such as preferred_source_click with placement and page-template parameters. Keep the implementation aligned with your consent setup. Then compare defined cohorts and time windows rather than attributing every change in impressions to the button.

Use Search Console to monitor the pages and queries that could trigger news or AI features, and keep a dated annotation for the rollout. For AI-specific monitoring, use a stable methodology rather than spot-checking screenshots; this AI visibility tracking guide explains the baseline.

If you see a lift, test alternative explanations: a breaking-news cycle, publication volume, indexing changes, prominent internal links, seasonality, a ranking update or stronger third-party references. Preferred Sources is one possible contributor, not the default cause. This same claim discipline matters when evaluating third-party mentions and AI citations.

What the button can and cannot do

Common implementation problems

• The source does not appear: test the bare domain or correct subdomain and confirm the publication is updated regularly. Do not substitute a blog subdirectory.
• The button container stays empty: check whether the publisher library loaded, whether a content-security policy blocked it, and whether a cache or optimizer delayed initialization.
• The button renders twice: load the library once and check whether both a plugin and theme template inject the same container.
• The wrong language appears: verify the page and browser language before forcing a documented data-lang value.
• Clicks are missing in analytics: test consent states, event listeners and navigation behavior; keep click tracking separate from claims about completed preferences.

Google Preferred Sources FAQ

The one thing to do next

Check your domain in Google’s source preferences tool. If it appears, add the standard button to one reusable post-footer template, record the launch date and measure interactions for 28 days before expanding placement. If your team needs the eligibility, implementation and measurement decisions reviewed together, SEO consulting from SearchCounselCo is the relevant next step.