WeSearch
Google gives publishers a new way to fight AI-driven traffic losses

Google gives publishers a new way to fight AI-driven traffic losses

Sarah Perez· ·3 min read · 0 reactions · 0 comments · 1 view
More from TechCrunch tech Trending Talk Blindspots Daily Sources Live wire
TL;DR · WeSearch summary

As AI continues to kill traffic to websites, Google on Thursday threw a bone to those publishers negatively impacted by the change. It’s now allowing readers to push a button on a publisher’s website to indicate it’s a “favorite source” they’d like to see highlighted more often across Google Search, Discover, and Google News. The tech giant said it’s making this new, interactive “Preferred Sources” button available to online publishers to embed on their own websites.

Key facts
About this source

TechCrunch files mainly under tech. We currently carry 763 of its stories.

Original article
TechCrunch · Sarah Perez
Read full at TechCrunch →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherTechCrunch
Canonical URLhttps://techcrunch.com/2026/08/20/google-gives-publishers-a-new-way-to-fight-ai-driven-traffic-losses/
Publication timeThu, 20 Aug 2026 19:18:21 +0000
Retrieval time2026-08-20T19:47:21.728Z
Last seen2026-08-20T19:47:21.728Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterNone
Cluster logicNot yet clustered, or no peer story found in the clustering window.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

As AI continues to kill traffic to websites, Google on Thursday threw a bone to those publishers negatively impacted by the change. It’s now allowing readers to push a button on a publisher’s website to indicate it’s a “favorite source” they’d like to see highlighted more often across Google Search, Discover, and Google News. The tech giant said it’s making this new, interactive “Preferred Sources” button available to online publishers to embed on their own websites. The launch follows Google’s rollout of Preferred Sources in May to Google’s AI experiences, including AI Mode and AI Overviews. The option was previously available in Top Stories.

Excerpt limited to ~120 words for fair-use compliance. The full article is at TechCrunch.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from TechCrunch