Google’s preferred sources feature for Top Stories is now available in every language where Google Search operates, with new downloadable button assets for publishers.
Google’s preferred sources feature, which lets users select publications they want to see more often in Top Stories, is now available in all languages where Google Search operates. Previously limited to a smaller set of languages, the expansion brings the feature to a global audience.
The update was announced on April 30, 2026, in Google’s Search Central changelog. The corresponding preferred sources documentation has been revised to reflect the expanded availability and includes new translated button assets publishers can download.
What Google Said
Google’s update note is brief and straightforward. It confirms the language expansion and the addition of new downloadable assets for publishers.
“Added that the preferred sources feature is now available in all languages where Google Search is available, including new translated downloadable button assets.”
The stated reason is equally direct: the feature itself has been rolled out to all supported languages, and the documentation now reflects that reality.
What The Documentation Now Says
The preferred sources documentation now states that the feature is “available globally for queries that trigger the ‘Top Stories’ feature in all languages where Google Search is available.”
The page explains how the feature works: when a user selects a site as a preferred source, that site’s content is “more likely to appear for them during relevant news queries in ‘Top Stories.'” This is a per-user personalization layer, not a universal ranking change.
Eligibility remains limited to domain-level and subdomain-level sites. Subdirectories are not eligible. For example, https://www.example.com/ and https://code.example.com/ qualify, but https://www.example.com/blog does not.
The documentation outlines two main ways publishers can encourage readers to select them as a preferred source. First, publishers can share a deep link using the format https://google.com/preferences/source?q=Your_Website's_URL, which takes users directly to the source preferences tool. Second, publishers can add a button to their site alongside other social CTAs, using either a custom design or Google’s official button assets.
The button assets section has been expanded significantly. It now lists downloadable assets for 16 specific languages (including Danish, Estonian, Finnish, French, German, Hebrew, Hindi, Japanese, Korean, Portuguese (Brazil), Russian, Spanish, Swedish, Turkish, and Ukrainian) plus an “all languages” download bundle. The docs also note that the feature works in all supported languages, not just those with listed button assets.
Why This Matters For SEOs
For publishers operating in non-English markets, this is the most significant part of the update. The preferred sources feature was previously available in a limited set of languages, which meant international publishers had fewer tools to build direct audience loyalty through Google Search. That barrier is now gone.
The practical impact is on audience development, not traditional SEO. Preferred sources is a user-facing personalization feature. When someone marks your site as preferred, your content gets a visibility boost in their Top Stories results. It does not change how Google ranks your site for other users or in other search features. Think of it as a “follow” button for Google News surfaces.
This matters most for news publishers, media organizations, and any site that regularly appears in Top Stories. If your content strategy depends on recurring visibility in that carousel, encouraging your audience to set you as a preferred source is now a viable tactic in every language Google supports.
The addition of translated button assets also lowers the implementation barrier. Publishers no longer need to design their own localized CTAs. Google provides ready-made assets that match the preferred sources branding, making it easier to add the button alongside existing social follow prompts.
What To Do Now
- Check whether your site appears in the <a href=”https://developers.google.com/search/docs/appearance/preferred-sources”>source preferences tool</a> by entering your domain in the tool’s search box. Only domain-level and subdomain-level sites are eligible.
- If your site qualifies, generate your deep link using the format <code>https://google.com/preferences/source?q=yourdomain.com</code> and start sharing it in social posts, newsletters, and on-site promotions.
- Download the appropriate button assets for your audience’s language(s) from the documentation page. If you serve multiple markets, grab the “all languages” bundle.
- Add the preferred sources button to your site alongside existing social CTAs (follow on X, subscribe to RSS, etc.). Place it where returning readers will see it: article footers, sidebar widgets, or newsletter signup flows.
- If you operate a subdirectory-based publication (e.g., <code>example.com/news</code>), note that you are not currently eligible. Consider whether a subdomain migration makes strategic sense for your Top Stories visibility goals, though this is a significant architectural decision that should not be made solely for this feature.
The Bottom Line
This documentation update reflects a product rollout, not an algorithm change. Google’s preferred sources feature now works everywhere Google Search does, and the docs have been updated with translated assets to match. For publishers already appearing in Top Stories, the expansion opens a new audience-building channel in every market they serve.
Google has been steadily investing in giving users more control over their Search experience, from the “Follow” feature in Discover to the source preferences tool. This global expansion suggests the company sees preferred sources as a long-term part of its news ecosystem. Publishers who build the habit of promoting their preferred sources link now may benefit as the feature matures and potentially extends to additional search surfaces.
AI-generated first-pass scaffolding. This draft was produced by Search Engine Journal’s newsroom automation as a starting point for a writer. Rewrite before publishing.
