By Greg Nowak. Updated 27 October 2026.
Yes, if you publish regularly and have readers who already value your work. Google’s Preferred Sources button gives those readers a way to ask for more of your publication in Search. For a newsroom, trade publication or active specialist blog, that deserves a small, measured test.
The business decision is whether another reader prompt earns space alongside newsletter signups, registrations and subscriptions. I would start with eligibility and a clear reader benefit, then give the experiment one placement, one owner and a review date.
What does choosing a preferred source actually change?
According to Google’s reader guidance, selected sources appear more often in Top Stories when they publish fresh content relevant to the search. Preferences also personalise AI Mode and AI Overviews. Readers who save their choices while signed in retain them across browsers using the same Google Account.
The benefit belongs to the person making the selection. Your articles still need to answer their searches, and Top Stories still depends on relevance, quality and freshness. Build your business case around helping existing readers find you again.
Google reports that people are twice as likely to click through to a Preferred Source. That is encouraging, but the announcement does not establish what adding a button will do for your publication. It provides a reason to test, rather than a reliable traffic forecast.
Check eligibility before booking development time
Search for your publication in Google’s source preferences tool. Sites without regular updates may be unavailable. Supported selections are domains and subdomains, such as example.com and news.example.com; a directory such as example.com/news is not independently eligible.
Check that the selectable site matches the publication readers recognise. If several editorial brands share a hostname, agree what the invitation means before designing it. Moving a publication to another subdomain solely to obtain this feature would need a much stronger business case.
For appearance as a preferred source in AI features, check Settings → Search generative AI in Search Console. Google’s control documentation explains that inclusion is the default, while child properties may inherit a parent’s choice. Review the effective setting with whoever owns the publishing policy. Changing it affects broader participation in Search generative AI features and deserves its own decision.
Choose an implementation your team can maintain
Google’s publisher implementation guide documents three routes. The standard button is its recommended starting point.
| Route | Use it when | Plan for |
|---|---|---|
| Standard JavaScript button | You want a straightforward website trial | Google’s presentation and external library |
| Advanced JavaScript integration | Your interface needs custom controls | Additional development and interaction testing |
| Deeplink | You use email, social posts or a restricted CMS | A hand-off to Google’s preferences tool |
The standard implementation uses this library and placeholder:
<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>
<div google-add-preferred-source-btn></div>It supports automatic localisation, a language override and light or dark themes. For a deeplink, replace the example domain in https://www.google.com/preferences/source?q=example.com.
In Drupal or WordPress, register the library through the normal asset system and put the placeholder in a reusable block, template or pattern. Load the library once. Keeping this out of individual article content makes future changes and removal easier.
Ask after the reader has received something useful
The end of a strong article is a sensible first placement. A newsletter confirmation page can also work: the reader has already shown interest, and the invitation has context.
Explain the benefit plainly. “See more of our reporting in Google” is more helpful than an unexplained badge. Keep subscriptions and newsletter signups visible, and avoid launching several placements together. Otherwise, you make both the page and the experiment harder to understand.
For a business website publishing occasional company updates, I would usually give the newsletter journey or contact experience priority. A frequently updated industry publication has a stronger reason to test this feature.
Keep the release small, but check the whole journey
Give one person responsibility for coordinating editorial wording, CMS changes and analytics. Ask the agency or developer to check mobile layouts, keyboard access, dark mode, translated labels and the return journey from Google.
Review the external library against your content security policy, consent setup and performance budget. Test with caching and optimisation enabled. When the library fails or is blocked, the article should remain readable and nearby actions should still work.
Measure what you can actually observe
Before launch, record Google referrals, engagement and the conversion rate of nearby newsletter or subscription prompts. Where your analytics and consent setup allow it, measure whether readers saw the invitation and activated it. A click should be recorded as a click; only report completed selections if you can reliably observe completion.
Use a comparable group without the prompt if your audience is large enough. Otherwise, treat before-and-after results as directional. Publishing volume, major stories, seasonality and changes in search demand can all affect referrals independently of this button.
A four-to-six-week initial review window is a practical starting point, not a Google requirement. Agree it before launch and extend it if too few readers encounter the invitation. Review whether people use it, whether it interferes with more valuable actions and whether any referral change is credible. Low participation is also a useful finding.
Give the test a clear decision at the end
Keep the button if it attracts reader interest, stays easy to maintain and fits comfortably into the page. Adjust or remove it if the prompt adds clutter without a convincing benefit. The code is only one part of the work; the value comes from making a publishing decision you can assess.
If this crosses editorial, agency and operations responsibilities, Greg can help scope and coordinate a manageable publisher test, from the eligibility check to the review.
Related on GrN.dk
- AI Search Is Eating the Click: Measure Before You Rewrite
- Google Review Link Generators: What Small Teams Actually Need
- AI Crawler Control for Business Websites: Protect Content Without Losing Search Visibility
Need help with this kind of work?
Plan a publisher test with Greg Get in touch with Greg.
