Google Preferred Sources has moved from a setting that readers had to find inside Search to a control publishers can place on their own pages. On 20 August 2026, Google documented a new interactive button that lets a reader add a publication as a preferred source and then return to the page they were reading.
That change matters because it connects audience loyalty with discovery in Top Stories, AI Overviews and AI Mode. It does not create a general ranking switch, guarantee inclusion or replace the work required to publish timely, original and trustworthy material. The opportunity is narrower and more useful: an eligible publication can make an existing reader preference easier to express.
This guide explains who can use the feature, how the standard and custom implementations differ, where the control belongs, what to measure and which claims to avoid. The goal is a defensible publisher workflow, not another speculative search tactic.
What Google Preferred Sources actually changes
According to Google Search Central’s publisher documentation, content from a site selected by a user is more likely to appear in that user’s Top Stories and can carry a preferred badge. The same site can also be highlighted with a preferred badge in AI Mode and AI Overviews where those features are available.
The preference is personal. A reader chooses a domain or subdomain for their own Google experience; the publisher does not add itself globally, and one reader’s choice does not change results for everybody. This distinction should shape both the implementation and the reporting language. “Help regular readers find us again” is supportable. “Improve rankings for every query” is not.
Google’s documentation says the Top Stories version is available globally in all languages where Google Search is available. Preferred Sources can appear in AI Mode and AI Overviews in the languages and locations where those features are available. Google had previously announced the global language expansion on 30 April 2026.
The August release reduced friction. Google’s product announcement says the embedded control adds the site and takes the user back to the publisher page. Google also reported that users had selected more than 600,000 unique sources by that date. That figure describes adoption across Google’s product, not the expected audience size or traffic uplift for an individual publication.
Check eligibility before writing any code
The first gate is the source preferences tool linked from Google’s documentation. Enter the publication and confirm that it appears. Only domain-level and subdomain-level properties are eligible. Google gives examples such as www.example.com and code.example.com; a path such as example.com/blog is not a separate eligible source.
This has practical implications for companies whose editorial operation sits inside a corporate domain. The button represents the eligible host, not an individual section. Before implementation, editorial and brand leaders should agree that the whole domain or subdomain is the identity readers are being asked to prefer. A campaign landing page cannot present itself as an independent source merely because it has its own directory.
Eligibility also does not guarantee that every article will appear in news experiences. Google’s explanation of news on Search says Top Stories results are selected algorithmically using signals that include relevance, prominence and publisher authoritativeness. The preference feature personalises the reader’s experience within that wider system.
Confirm four conditions before launch:
- the intended domain or subdomain appears in the source preferences tool;
- the site publishes material that can genuinely serve recurring readers;
- the proposed placement does not obscure article content or consent choices;
- the team can explain the feature without promising rankings, inclusion or traffic.
Choose the right implementation
Google provides three routes: a standard JavaScript button, an advanced JavaScript integration and a deeplink. The best choice depends on the publishing platform and the level of interface control required.
Standard JavaScript: the safest default
Google recommends the standard implementation. It requires an asynchronous script in the page, preferably in the document head, and a custom div where the button should render:
<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>
<div google-add-preferred-source-btn></div>The component is automatically localised according to the reader’s browser settings. Publishers can choose a light or dark theme and can override the language with documented data attributes. This route reduces design and translation work while keeping the interaction aligned with Google’s supported flow.
Advanced JavaScript: use only for a real product need
The advanced option lets a team initialise the library programmatically and connect the flow to its own control. Google documents both ES module and standard script callback approaches. This is useful when a design system has strict component rules, when the trigger must appear after a meaningful reader milestone or when a modern application needs explicit lifecycle control.
Customisation creates more responsibilities. The team must preserve accessibility, keyboard behaviour, responsive layout, loading states and an honest label. A custom button should not imitate a subscription purchase, conceal its destination or appear as a required step. A search-ready web design and development review can verify the component in the actual template rather than approving it from a static mock-up.
Deeplink: a credible no-script fallback
If the CMS cannot load the library, Google supports a link to its source preferences interface using the publication domain as the query value. The deeplink can appear in an article, newsletter, social post or promotion. It sends the reader to Google to confirm the source rather than completing the same return-to-page flow as the interactive control.
Use the deeplink when it solves a platform constraint, not simply because it is faster to paste. Test the final URL, describe the destination clearly and avoid adding it automatically to every unrelated marketing message.
Place the control where reader trust already exists
A preferred-source request is a relationship prompt. It is strongest after the reader has enough evidence to judge the publication, and weakest when it interrupts an unfamiliar visitor before the article has delivered value.
Useful placements include the end of a complete article, an author or publication follow module, a newsletter confirmation page and a returning-reader area. A restrained placement near the article header can work for an established audience, but it should not compete with the headline, navigation or urgent public-interest information.
Avoid modal takeovers, repeated prompts within one visit, controls disguised as necessary actions and wording that claims the reader will always see the publisher first. Google’s documentation describes increased likelihood and highlighting for a user’s preferred sources, not exclusive distribution.
The surrounding copy can be short and literal: explain that the control lets readers identify the site as a preferred source in Google. Do not combine it with an unrelated newsletter consent or assume that a preference in Google creates a first-party subscriber record.
Build a release checklist, not a copy-and-paste task
The two-line standard implementation is simple; production readiness still deserves normal frontend controls. Load the script asynchronously, confirm that failure does not block article content, and ensure the placeholder does not cause a disruptive layout shift. Test with content blockers and slow connections so the page remains usable when the external resource is unavailable.
Run desktop and mobile checks across the publication’s supported browsers. Confirm that the button:
- renders in the intended language and theme;
- can be reached and activated with a keyboard;
- has an understandable accessible name and visible focus state;
- does not overflow narrow screens or cover article controls;
- returns the reader to the correct page in the supported flow;
- fails without hiding, delaying or breaking the article;
- is not duplicated by reusable templates or client-side navigation.
If a content security policy restricts third-party scripts, review the documented Google host through the organisation’s security process rather than weakening the policy broadly. Record why the script is loaded, where it appears and who owns future changes.
Measure adoption without inventing attribution
Measurement should separate implementation performance from search outcomes. At the component level, record where the prompt was shown, whether the user activated it and which placement or article template was involved. For a custom implementation, document whether the tracked event represents a click, the opening of Google’s flow or a confirmed selection. Do not label a click as a completed preference unless the integration provides that evidence.
For wider discovery, Search Console’s Performance report provides clicks, impressions, click-through rate and average position, with dimensions including page, query, country and device. Compare stable weekly or monthly periods, annotate the launch date and review cohorts of pages with the control. Those trends can show what happened after implementation, but they do not prove the button caused the change.
Google said in April that readers were twice as likely to click through to a site after marking it as a preferred source. Treat that as Google’s product-level observation, not a forecast for a particular publisher. Audience mix, topic demand, eligibility, publication frequency and the relevance of each story will differ.
A useful dashboard can report four layers:
- Reach: eligible page views on which the control loaded successfully.
- Interaction: activations divided by eligible control views, segmented by placement.
- Discovery: Search, News and Discover clicks and impressions for comparable article groups.
- Business value: returning readers, newsletter registrations or other first-party outcomes measured independently of Google preference status.
Content quality remains the main operating system
The feature rewards a relationship that has already been earned. A reader is unlikely to prefer a source that republishes commodity summaries, obscures authorship, changes subject without editorial logic or makes claims without evidence. The button cannot repair a weak publication proposition.
Prioritise recognisable expertise, clear bylines, accurate dates, corrections, primary evidence and a consistent subject focus. Publish on a cadence the team can maintain. Give important articles strong internal routes, usable images and technically clean canonical pages. An AI visibility and source-readiness assessment can examine whether that evidence remains accessible and understandable across search and answer experiences without treating Preferred Sources as a universal ranking factor.
Google’s own adoption figures also suggest a competitive reality: readers can choose many sources. The durable advantage is not being the only preferred publication. It is giving a defined audience a recurring reason to recognise, select and revisit the site.
A 30-day publisher action plan
Week 1: verify the foundation. Check domain eligibility, map the templates that reach returning readers, review news and search policies, and name the product, editorial and analytics owners. Decide whether the standard component, advanced implementation or deeplink is appropriate.
Week 2: implement one controlled placement. Add the component to a representative article template or reader-follow module. Keep the copy literal, load the library safely and prepare a fallback that leaves the article intact.
Week 3: test the complete journey. Validate desktop, mobile, accessibility, language, theme, performance and return behaviour. Confirm analytics names exactly what was observed. Obtain editorial approval for the surrounding copy.
Week 4: launch narrowly and establish a baseline. Roll out to one useful section, monitor component reliability and compare discovery trends over a meaningful period. Expand only if the prompt is relevant, technically stable and accepted by readers. Remove or reposition it if it creates friction without evidence of value.
Conclusion
Google Preferred Sources gives publishers a supported way to turn reader loyalty into an explicit personal preference across Top Stories and eligible AI search experiences. The August 2026 button makes that request easier to place inside the publisher journey, but it does not bypass relevance, eligibility or editorial quality.
Start by confirming the host is eligible. Use the standard component unless a real product constraint requires custom code, place it after trust has been earned, test failure and accessibility states, and report interaction separately from search outcomes. The implementation is small; the audience promise around it deserves senior editorial discipline.
Frequently asked questions
Does Google Preferred Sources improve rankings?
Google says a selected site is more likely to appear for that user in Top Stories and can be highlighted in AI Mode and AI Overviews. It does not describe the feature as a universal ranking boost or guarantee that every article will appear.
Can any business add the Preferred Sources button?
Only domain-level or subdomain-level sites that appear in Google’s source preferences tool are eligible. A directory such as example.com/blog cannot be selected independently from its host.
What is the recommended implementation?
Google recommends its standard JavaScript button. It uses an asynchronous publisher library plus a designated div, supports light and dark themes, and is automatically localised unless the publisher overrides the language.
Where should publishers place the button?
Place it where the publication has already demonstrated value, such as the end of an article, a follow module or a newsletter confirmation page. Avoid disruptive prompts and wording that promises guaranteed visibility.
How should a publisher measure success?
Track component reach and activations accurately, then review Search, News, Discover and first-party audience trends over stable periods. A before-and-after movement is useful evidence, but it does not by itself prove that the button caused the change.
Sources and references
- Google Search Central: Help readers find your site through preferred sources.
- Google Search Central: Latest documentation updates, including the 20 August 2026 button update.
- Google: Personalize the content you see on Search, Discover and News, published 20 August 2026.
- Google: Preferred Sources is available in all languages, published 30 April 2026.
- Google Publisher Center Help: What’s News on Search.
- Google Search Console Help: Performance report overview and basic setup.
