Search publication update
Google Preferred Sources in 2026: what publishers and business websites should actually do
Preferred Sources is now a global Search feature and can surface preferred sites in Top Stories and supported AI experiences. The important publisher action is not to add a badge blindly: first verify that the domain appears in Google's source-preferences tool, then use the official integration if it is genuinely useful to readers.
Published 2026-09-17 · Updated 2026-09-17 · Reviewed by Shakeel Anjum, QA & Release Engineer

What changed
Google now documents Preferred Sources as globally available for Top Stories in all languages where Search is available. Google also says preferred sources can be highlighted in AI Mode and AI Overviews where those experiences are available.
For publishers, the key eligibility detail is domain-level recognition. Google instructs site owners to first confirm that their domain appears in the source-preferences tool before promoting an Add as Preferred Source control.
What a site owner should do
Treat Preferred Sources as an audience-relationship feature, not an SEO shortcut. A site still needs useful, current content that deserves repeat readership.
- Publish genuinely fresh editorial material on topics the site can credibly cover.
- Check the domain in Google's source-preferences tool before adding the official button or deeplink.
- If eligible, use Google's documented JavaScript button or deeplink rather than inventing a custom claim of preferred status.
- Do not claim that a reader preference guarantees Top Stories, AI Overview, AI Mode, ranking, impressions or traffic.
Zolesco's current implementation decision
Zolesco has established a fresh editorial lane in Phase 36, but its own Preferred Sources button remains disabled until the domain's appearance in Google's interactive source-preferences tool can be verified. The public documentation describes the eligibility check, while the current execution environment cannot truthfully confirm the interactive account/session result.
That means the correct implementation today is publication readiness without an unsupported Preferred Sources badge. The eligibility record can be updated later if the domain becomes verifiably selectable.
Sources and verification
Current platform facts are tied to dated primary documentation. Zolesco links are supporting context, not independent verification.
