Google Preferred Sources target AI search traffic losses

Google is giving publishers a direct way to ask readers for a durable source preference as AI search changes how people reach the web. In the August 20, 2026 report from TechCrunch, Google’s new interactive Preferred Sources button lets readers add a publisher from that publisher’s own website. The practical takeaway for publishers is to make the request at a moment when a reader already trusts the publication, rather than treating the button as a substitute for useful content.

Definition: Google Preferred Sources lets readers choose websites they want Google to highlight more often in relevant Search and AI experiences.

Example: A reader can use a publisher’s on-page button to add that site, then see its links marked as preferred when Google surfaces them.

Key takeaway: The new button turns source preference into an on-site reader action instead of hiding it inside Google’s settings.

Business impact: Publishers get another way to convert reader trust into repeat visibility while AI-powered search sends fewer users directly to some websites.

Google Preferred Sources for publishers

Google’s new Preferred Sources button gives publishers an embeddable way to start the source-selection flow from their own pages. The August 20 update gives publishers a direct on-page path into source selection, while TechCrunch reported that more than 345,000 unique sources had already been selected as of Google’s May launch. Publishers should use the official implementation when they want the action to sit beside an article, newsletter prompt, or other reader moment.

Google’s Preferred Sources feature already existed in Top Stories before Google expanded it into AI Overviews and AI Mode in May. Google said people were twice as likely to click a Preferred Source when one was available in earlier studies, but that figure describes Google’s reported comparison, not a guaranteed result for every site. The useful distinction for publishers is that the preference is reader-selected: the button can make the choice easier, but the reader still decides whether to add the publication.

Distribution surfaces for preferred publishers

Google says a selected Preferred Source can be highlighted in Top Stories, AI Overviews, and AI Mode when the source is relevant to what the person is searching for. Google’s Search Central guide explains that eligible sites are selected at the domain or subdomain level, so a root domain or a subdomain can qualify while a separate blog subdirectory cannot. Publishers should check the source-preferences tool before promoting the feature and avoid promising visibility that Google’s documentation does not promise.

The publisher implementation has three practical forms. Google recommends a standard JavaScript button that localizes the interface and returns readers to the page. Publishers that need their own trigger can use Google’s advanced JavaScript implementation, while publishers without a suitable JavaScript integration can use a deeplink to the source-preferences page. The choice changes the interface, not the underlying reader action: the reader must explicitly select the site.

Google Preferred Sources and AI search

Google’s Preferred Sources rollout responds to a distribution problem created by the same search surfaces that increasingly summarize information for users. AI Overviews and AI Mode can answer a question before a reader opens a publisher’s page, so the new control gives readers a way to tell Google which sources they want to notice inside those answers. That makes source preference a relationship signal rather than a technical setting a publisher can activate for everyone.

Google’s Preferred Sources update is a reader-controlled distribution feature. For related Yowox context, see Google Ads AI tools speeding up marketing analysis and AI authorship across new webpages.

Google Discover and Google News controls

Google says Discover users will soon be able to describe the topics they want to see more or less often in natural language. The Google app will accept those requests from a feed item’s three-dot menu and adjust the feed in real time. For readers, the benefit is a faster correction when the feed misses an interest; for publishers, the implication is that relevance and reader preference will increasingly shape distribution together.

Google also says Android users will be able to customize audio daily briefings in the Google News app by choosing topics. Google describes the briefings as including source attribution and links to full articles, which gives readers a path from a generated listening experience back to the publisher. Publishers should therefore treat attribution and the destination article as part of the product experience, not as details that disappear once a summary is generated.

Publisher next steps for Preferred Sources

Publishers should first verify that their domain appears in Google’s source-preferences tool, then choose the implementation that fits the page and the publication’s reader journey. Google’s Preferred Sources documentation provides the standard script, the custom JavaScript flow, and the deeplink format. The immediate action is simple: place the request where a reader has just received value, explain what the preference changes, and avoid claiming that selection guarantees ranking or traffic.

The larger lesson is that Google is giving publishers a distribution prompt, not a recovery plan for every AI-search loss. A Preferred Source can be surfaced more clearly for a reader who selected it, while the publisher still needs fresh, relevant reporting to be eligible for the query. Publishers should measure the button as a reader-choice experiment and keep the editorial work that makes a reader want to choose the site in the first place.