Google now offers an embeddable Preferred Source button that lets readers star a publication from the article page and return immediately to the content they were reading. The change removes a redirect that previously interrupted sessions and gives publishers a simpler path to coax search users into a visibility signal Google uses in Top Stories.
What changed
Until now, adding a publisher as a Preferred Source required a navigation away from the publisher’s site. The new embedable button runs Google’s selection flow in-place and then returns the user to the same article on the publisher’s site. Google publishes the embed code in its help documentation for developers and publishers to add to article pages, newsletters or membership areas.
Why publishers should pay attention
Preferred Sources is a personalization signal Google uses in the Top Stories carousel: users who star a publication see more stories from that outlet. Google reports that people who select Preferred Sources are roughly twice as likely to click through to articles from those outlets, which translates directly to higher search-driven engagement for opted-in readers.
The feature’s rollout moved quickly: it entered beta in June 2025, launched in the U.S. and India in August 2025, and completed a global rollout in December 2025. Google has also enabled the capability for all languages. In May 2026 Google reported 200,000 unique sources had been selected; more recently it said users have selected more than 600,000 unique sources — about a 200% increase since May.
Practical implications and next steps
The immediate operational gains are twofold: a lower-friction opt-in for readers, and fewer lost sessions because the embed returns users to the article instead of redirecting them away. Publishers can place the button on article pages, newsletters and membership pages without interrupting reading or subscription flows.
Implementation is straightforward: add the embed code from Google’s documentation and monitor outcomes. Key metrics to track include Top Stories impressions and organic CTR from Search Console, time on page and repeat search-driven visits for users who have starred the site versus those who haven’t.
Google’s aggregate adoption numbers indicate user interest, but they don’t reveal how visibility changes for individual publishers. Expect results to vary by audience size, topical fit and how prominently you present the button. Treat the embed as a testable experiment: A/B test placement and messaging, measure incremental clicks and iterate.
What publishers should watch next
Measure competitor adoption in your vertical, track CTR changes in Search Console, and look for additional technical options or documentation from Google that clarify attribution or distribution effects. If you see measurable lift from opted-in users, consider expanding placement to newsletters and membership touchpoints where search-origin readers may engage.
Action checklist: embed the button, tag and segment opted-in users in your analytics, run a short experiment on placement and copy, and report results to editorial and product teams. The change is small to implement but gives you a controlled way to convert search readers into a sustained visibility signal inside Google’s Top Stories network.
