Google on August 20, 2026 released an embeddable Preferred Sources button for publishers and disclosed that readers have now selected more than 600,000 unique sources, roughly 255,000 more than the figure the company reported at the end of May.

The announcement arrived through a post on the company blog written by Mrinalini Loew, General Manager of the Google Search Ecosystem, and was amplified the same evening through a four-post thread on the News from Google account on X, timestamped 7:59 PM on August 20 and carrying 63,100 views at the time of capture. Three separate changes were bundled into a single post: an interactive button that publishers can place on their own pages, a free-text tuning control inside the Discover feed, and topic curation for the daily audio briefings in the Google News app on Android.

Only one of the three is available immediately. The other two were described as arriving in the coming days.

What the button does

Until August 20, the mechanism for designating a preferred source lived entirely on Google's side of the transaction. A reader had to find the source preferences tool, search for a publication by name, and confirm the selection there. Publishers could point readers toward that tool with a deeplink or a downloadable badge, but the round trip took the reader off the page and did not return them.

The new implementation closes that loop. According to Google, when a reader clicks the embedded button, the site is added as a Preferred Source and the reader is sent straight back to the point on the publisher's page where the interaction began. The company frames the change as one that assists both sides of the exchange, describing the intent as "helping publishers build stronger, direct connections with their readers."

The practical consequence sits in the friction removed. A publisher promoting the feature no longer has to persuade a reader to leave, navigate an unfamiliar Google settings surface, and find their way back.

Where the designation applies

Once a site is designated, the effect shows up in three places. In Top Stories, content from that site is more likely to surface and carries a preferred badge. In AI Overviews and AI Mode, links from that site can carry the same badge for the reader who made the selection.

Availability differs between those surfaces. Google's Search Central documentation, last updated 2026-08-20 UTC, states that the preferred sources feature is available globally for Top Stories in every language where Google Search operates. For AI Mode and AI Overviews, the feature appears in all languages and locales where those two products themselves are available - a narrower footprint, since neither has reached the full geographic spread of Search.

Eligibility is set at the domain level

The documentation carries a restriction that matters for large publishers running vertical brands inside a single domain. Only domain-level and subdomain-level sites can appear in the source preferences tool. Google's own examples make the boundary explicit: a root domain and a subdomain both qualify, while a subdirectory path such as a blog folder does not.

For a media group that has consolidated its verticals into folders on one property - a common consequence of a decade of SEO consolidation advice - this means the group can be selected only as a whole. A reader who wants the food section but not the politics section has no mechanism to express that at the source level. Publishers that kept separate subdomains retain a granularity their consolidated competitors gave up.

The technical implementation

Three integration paths are documented, and Google recommends the first.

Standard JavaScript requires two lines. A script tag loads the Preferred Sources library asynchronously from news.google.com, under the /swg/js/v1/publisher.js path, and the documentation advises placing it in the head element. A div element carrying the google-add-preferred-source-btn attribute is then dropped anywhere in the body where the button should appear. The library scans the document for elements carrying that attribute and renders a Google-styled badge automatically.

Two data attributes control presentation. A data-theme attribute accepts light or dark, with light as the default. A data-lang attribute overrides the button language, which otherwise follows the reader's browser settings; Google provides a downloadable list of supported language codes.

Advanced JavaScript exists for publishers who want their own design assets or who need to fire the flow from an application milestone rather than a rendered badge. Two distribution models are offered, and the documentation states that both expose identical capabilities. Modern build environments can import the module directly from publisher.mjs, initialise it with a theme and language object, and bind the addPreferredSource method to any click handler. Standard script-tag integrations load the same library with a preferred-sources-control attribute set to manual, which suppresses automatic rendering, then push initialisation and trigger binding into a global PREFERRED_SOURCE callback queue. The documentation carries an explicit warning on this point: omit the manual attribute and the library will immediately initialise any matching element on the page.

The end-user flow is identical across both JavaScript paths. Only the trigger differs.

Deeplink implementation remains for publishers whose content management systems cannot execute the JavaScript. A URL under google.com/preferences/source, with the publication's domain passed as a query parameter, takes the reader directly to that site's entry in the source preferences tool. Google documents the deeplink as a text link or a clickable image and notes it can also be dropped into social posts, email newsletters and promotions. That is the same mechanism PPC Land documented on April 30, 2026, when Google refreshed the publisher guide with deeplinks and translated button assets. The assets remain: publishers can design their own promotional badge or download Google's official translated graphics.

One line in the documentation limits how much any of this should be read as a ranking instruction. The listed methods are described as examples of audience building, and are "not required to do them in order to appear as a preferred source." Implementation is a distribution decision, not an eligibility gate.

The selection number and its trajectory

The 600,000 figure is the fourth public disclosure of cumulative unique sources selected, and the series is now long enough to read.

On December 10, 2025, when the feature went global alongside a commercial AI partnership pilot, Google put the total at nearly 90,000 unique sources. On May 27, 2026, when the feature extended into AI Overviews and AI Mode, the company reported more than 345,000. The August 20 figure is more than 600,000.

That is roughly a sixfold increase across eight months, with the bulk of it arriving after the AI surface expansion in late May. The intervening period also included the completion of the rollout into all supported languages, which Google had scheduled for early 2026 and which the company confirmed as complete by the spring.

The number counts unique sources selected, not selections made and not users making them. A source picked by one reader and a source picked by a million readers each contribute one unit. The metric describes the breadth of the long tail rather than the depth of adoption, and Google has not published the second figure.

The engagement claim attached to the feature has held steady since December, when Robby Stein, VP of Product for Google Search, and Jaffer Zaidi, VP of Global News Partnerships, wrote that when someone picks a preferred source, "they click to that site twice as much on average." The same doubling was restated in May and repeated by Liz Reid, VP and head of Google Search, in a June 26, 2026 podcast appearance where she described the mechanism as a way for publishers to make an existing reader relationship legible to Search. Google has not disclosed the baseline against which the doubling is measured, nor whether the effect persists over time or decays after the initial selection.

Discover moves to free-text control

The second component extends a personalization layer that has been in beta for months. In the coming days, according to Google, tapping the three-dot menu on any card in the Discover feed inside the Google app will open a control where a reader can describe, in their own words, which topics or links should appear more or less often. The feed adjusts immediately and retains the instruction.

This is the productisation of Tailor Your Feed, the chat-style interface that surfaced in testing during the spring. PPC Land documented the accompanying transparency label, "You asked to see", which was first spotted on April 24, 2026 and which appears on cards selected through an explicit typed request rather than through inferred browsing history. The distinction is technical and consequential: it separates content Discover surfaced because a reader asked for it from content Discover surfaced because an algorithm inferred an interest.

For publishers, the free-text layer cuts in two directions. A reader can now request a topic with a level of specificity that no interest taxonomy supports - Google's own illustrations reference eco-friendly kitchen renovation ideas and weekend road trip videos that exclude camping. A reader can equally request less of something, and negative instructions attach to whatever the system parses as the offending category.

Discover has been the dominant Google referral channel for news sites since research in August 2025 put its share at two-thirds of Google traffic to news websites. It has also been the most volatile. A February 5, 2026 core update reweighted the feed toward local relevance and away from sensational material. Marfeel data published in December 2025 found AI Summaries occupying 51% of feed positions in test markets. Page views from Google Search fell 34% over the twelve months to December 2025 with Discover down 15% across the same window, figures cited most recently in coverage of Mediavine's appointment of an advocacy director.

Audio briefings get topic curation

The third component is confined to the Google News app on Android. Readers can now select specific topics for their daily audio briefings, which Google says carry source attribution and links out to full articles.

The briefing content draws on the publisher cohort in Google's news AI pilot program - the commercial partnership announced on December 10, 2025 with Der Spiegel, El País, Folha de S. Paulo, Infobae, Kompas, The Guardian, The Times of India, The Washington Examiner and The Washington Post, among others. That programme also introduced AI-powered article overviews on participating publications' Google News pages and audio briefing experiments, both described at launch as including clear attribution and links to articles.

The pilot sits inside a larger licensing footprint. Google stated in December 2025 that it had partnered with over 3,000 publications, platforms and content providers in more than 50 countries, paying for extended display rights and content delivery methods such as APIs. Separate arrangements with Estadão, Antara, Yonhap and The Associated Press supply real-time information to the Gemini app.

The August 20 announcement therefore does two things at once for the audio product: it hands readers a topic filter, and it routes the depth of the briefing through a publisher cohort that Google selected and pays.

Why this matters for marketers and publishers

Preferred Sources is the only Google surface control that a publisher can ask for directly and a reader can grant directly. Everything else in the stack - ranking, feed placement, AI citation - is mediated by systems the publisher cannot address. That singularity explains the volume of attention the feature attracts relative to its measured effect.

The effect, though, is distributional. As PPC Land observed in an analysis published on May 30, 2026, the tool rewards publishers who already command a loyal audience and offers comparatively little to newer or smaller sites whose discoverability has been eroding. A reader has to know a publication exists before designating it. Selection is an act of confirmation, not discovery, and the button released on August 20 makes that act cheaper without changing its precondition.

The advertising consequence follows the traffic. Sessions that arrive through a preferred-source click land on a publisher page with the full inventory that page carries. Sessions absorbed into an AI Overview or an AI Summary in Discover do not. For media buyers, the open web supply that programmatic depends on is a function of how many of those sessions reach a publisher at all, and the badge is one of the few levers pointing in that direction. Its ceiling is set by how many readers will click a button on a page they were already reading.

There is also a measurement gap. Google reports unique sources selected and a doubling of click-through. It does not report how many readers have made a selection, how many selections the median reader holds, how often a preferred badge appears per thousand queries, or what share of a designated publisher's Google traffic the mechanism accounts for. Search Console exposes no preferred-source dimension. A publisher that embeds the button on August 20 can count clicks on the button through its own analytics, and can observe nothing downstream of it.

The pattern is familiar from the surrounding product line. Search profiles, launched on June 4, 2026 after a pilot restricted to 54 publishers, came with documentation stating that changes to a profile do not affect content ranking in Search or Discover. The five outbound link features added to AI Mode and AI Overviews on May 6, 2026 were similarly framed around user benefit, with traffic impact left unquantified.

What the August 20 release changes is cost, not architecture. Two lines of markup replace a promotional campaign to push readers into a Google settings page. Whether 600,000 unique sources becomes a number that shows up in publisher revenue, rather than in Google announcements, is not something the disclosed figures answer.

Timeline

Summary

Who - Google, through a blog post authored by Mrinalini Loew, General Manager of the Google Search Ecosystem, and a thread on the News from Google account on X. The changes affect web publishers, news organisations, SEO teams and the media buyers who depend on publisher inventory.

What - Three personalization changes. An embeddable Preferred Sources button that publishers can place on their own pages, available through standard JavaScript, an advanced JavaScript path with custom design assets, or a deeplink. A free-text control in the Discover feed that lets readers describe topics to see more or less of. Topic curation for daily audio briefings in the Google News app on Android. Google also disclosed that readers have selected more than 600,000 unique sources, up from more than 345,000 on May 27, 2026 and nearly 90,000 on December 10, 2025.

When - August 20, 2026. The button and its Search Central documentation are live, with the documentation carrying a 2026-08-20 UTC timestamp. The Discover control and the audio briefing curation were described as arriving in the coming days.

Where - Preferred Sources operates globally in Top Stories in every language where Google Search is available, and in AI Overviews and AI Mode wherever those features exist. The Discover control applies in the Google app. The audio briefing curation is limited to the Google News app on Android.

Why - Google presents the package as returning control to readers while giving publishers a direct route to audience relationships. The disclosed figures cover breadth of selection and a claimed doubling of click-through, and stop short of the depth metrics that would establish what the mechanism contributes to publisher traffic.