--- title: "Google's *Follow* button — the ranking lever B2B teams missed" canonical_url: https://webflur.com/blog/google-preferred-sources-button last_updated: 2026-09-17 author: Pankaj description: "Google" --- # Google's *Follow* button — the ranking lever B2B teams missed **Last updated:** Sep 17, 2026 **Author:** Pankaj — Founder, WebFlur **Canonical URL:** [https://webflur.com/blog/google-preferred-sources-button](https://webflur.com/blog/google-preferred-sources-button) --- [Back to Blog](../blog.html) AI Landscape # Google's *Follow* button — the ranking lever B2B teams missed Google's new Follow-style button — officially called Preferred Sources — lets a reader make you a favorite across Search, Discover, and AI Overviews. Two lines of HTML per Google's own docs. Here's exactly what Google recommends you ship, and why B2B should treat it as a share-of-model lever, not a Top Stories toy. Pankaj Raghav Founder, WebFlur Sep 17, 2026 8 min read Last updated Sep 17, 2026 QUICK ANSWER **Google's Preferred Sources button — the "Follow" button live on publisher sites since 20 August 2026 — is a one-click widget that lets a reader make you a favorite source across Google Search, Discover, and AI Overviews.** Google recommends every publisher embed it; at WebFlur we treat it as a share-of-model lever in AI answers, not a Top Stories toy. ### The Google update most B2B teams read once and skipped On 20 August 2026, Google's Search team [shipped an embeddable Preferred Sources button](https://blog.google/products-and-platforms/products/search/personalize-search-discover-news/) for publisher websites. TechCrunch [framed it as Google's answer to AI-driven traffic losses](https://techcrunch.com/2026/08/20/google-gives-publishers-a-new-way-to-fight-ai-driven-traffic-losses/). The press cycle treated it as news publisher plumbing — Wall Street Journal, CNN, Times of India were the named examples. B2B teams read the headline, filed it under "not for us", and moved on. That's the mistake this piece exists to correct. The mechanic Google shipped isn't a Top Stories nudge for news publishers. It's a per-reader visibility signal that now runs inside AI Overviews and AI Mode — the exact surfaces B2B buyers use to shortlist vendors. Two lines of HTML, no ranking algorithm change, and a lift you can measure per opted-in reader. That's the entire pitch, and Google itself is telling you to ship it. What Google recommends From Google's official launch post: *"When readers click this button, it adds the site as a Preferred Source on Google and immediately directs them back."* The button is available in Google Search Central docs, ships with a light and dark theme, supports a language override, and installs in two lines of HTML. Google's guidance is unambiguous — publishers with returning audiences should embed it prominently. ## What Google's blog post actually announced on 20 August 2026 The launch consolidated three changes into one Google Search personalization update. Watching the walkthrough is faster than reading five recaps — the embed below is lazy-loaded (no third-party script fires until you click play). ▶ Google · Preferred Sources walkthrough The three shipped changes: 1. **The Preferred Sources button** — the embeddable widget publishers put on their own site. When a reader taps it, that reader is opted in as a follower of the publisher, and Google's UI confirms and redirects them back within a second. 2. **Discover feed topic customization** — readers tap any three-dot menu in Discover and tell Google, in plain language, the topics or links they want to see more or less of. 3. **Custom audio briefings in Google News** — readers now curate briefings by choosing topics, with clear source attribution and links out to full articles. All three roll into the same signal — *who this reader wants to hear from*. What makes the button strategically distinct is that publishers get to initiate the opt-in from their own surface for the first time. Before 20 August 2026, a reader had to add a Preferred Source from inside Google's UI. Now the CTA lives on the publisher's page, one tap, done. ## Does the Preferred Sources button actually improve rankings? **Yes — for opted-in readers. No — for the universal SERP.** This is the distinction that keeps tripping up SEO practitioners reading the launch, so lock it in: Preferred Sources is a *personalization* signal, not a global ranking factor. It changes what your opted-in readers see across Search, Discover, and — crucially for B2B — AI Overviews and AI Mode. It does not lift your rankings for a searcher who's never heard of you. Which is exactly why Google recommends it. Google's core ranking system already rewards content quality; Preferred Sources rewards *audience relationships*. A reader who bookmarks your comparison guide, comes back three times, then Follows you is telling Google something the ranking algorithm can't infer from links alone. Google then honors that signal on Search, on Discover, and in the citation slots inside that reader's AI Overview and AI Mode responses. Google extended the Preferred Sources mechanic into AI Overviews and AI Mode on 27 May 2026, per the same Search Central announcements. That's the update B2B teams missed, and it's what turns this from a news-publisher story into a WebFlur-relevant one. It's the same reason we wrote [the WebFlur breakdown of how Perplexity, Claude and ChatGPT decide citations](/blog/how-perplexity-claude-chatgpt-cite) — every AI answer engine now has a distinct visibility lever, and Preferred Sources is Google's. ## How to add the Preferred Sources button — exactly what Google recommends **Two lines of HTML per Google's official docs.** The [Google Search Central page on Preferred Sources](https://developers.google.com/search/docs/appearance/preferred-sources) ships the embed code with light and dark themes plus a language override attribute. Follow the sequence below — this is Google's own recommended install order. 1. **Copy the embed snippet from Search Central.** Google supplies a single-line HTML tag plus the loader script. Do not modify the tag structure; Google's serving logic reads the attributes verbatim. 2. **Place the button near your logo, byline, or footer.** Google's recommendation, verbatim: put it where a returning reader will see it. Author bylines on evergreen guides work well for B2B; the footer of a solution page works less well. 3. **Match theme + language to your site.** Set `data-theme="light"` or `"dark"`; override language only if your default browser locale differs from your audience's. 4. **Validate with Google's Rich Results Test.** Confirm the button loads on desktop + mobile and that click handling redirects back to your page (Google's spec says redirect within 1 second). 5. **Track opt-ins server-side.** There's no first-party Preferred Sources metric in Search Console yet, but you can measure the button click as a custom event in GA4. Correlate it with returning-visitor cohorts to see the audience lifting. 6. **Refresh your `llms.txt` and sitemap** so the same signal — *this site is a canonical source for X topics* — is coherent across every crawler surface. Google's grounding pass reads both. This is a one-hour job for an engineer, or a WebFlur-style audit followed by a same-day retrofit. Either way the guidance is Google's, not ours — we've just packaged it in the sequence that catches the most upside for B2B publishers. ## Why B2B should care — Preferred Sources is a share-of-model lever, not a Top Stories toy **Here's the framing every recap missed.** If you read the launch as "Google gave publishers a Follow button", you'd correctly conclude the story is about news sites. If you read it as "Google let its most engaged readers permanently boost your visibility inside AI Overviews and AI Mode citations", the story flips — and it's now about every B2B site with a returning audience. The 27 May 2026 extension into AI Overviews and AI Mode is the load-bearing detail. Before that date, Preferred Sources influenced Top Stories placement — genuinely useful for publishers, mostly irrelevant for B2B. After that date, the same signal decides which sources get quoted inside the AI answer that a director-level buyer sees when they ask ChatGPT-competitor Gemini "which vendor should I evaluate for X". A reader who Follows you is a reader whose AI Overview will cite you first. Compound that across every returning newsletter subscriber, every repeat blog visitor, every buyer in a multi-touch evaluation cycle, and you're looking at a durable share-of-model lift. The failure mode is small: you embed the button and low-affinity readers don't click it. The upside is asymmetric: high-affinity readers click once and you get months of preferential citation inside every AI answer they see. That's why [a serious B2B AI SEO agency](/blog/best-ai-seo-agencies) should be shipping this on client sites the same week they read Google's blog post — not queueing it behind next quarter's roadmap. Key insight Preferred Sources is not a Top Stories update dressed up for publishers. Since 27 May 2026 it's been a *per-reader share-of-model lever* — the closest thing to a ranking-factor-equivalent that AI Overviews and AI Mode expose to publishers. Two lines of HTML. Ship it before your competitor does. ## The 6-item Preferred Sources launch checklist **Copy this checklist into your sprint doc.** Every item ships in one hour or less — the whole package is a half-day retrofit. If you knock off five of six, you have the button live, tracked, and integrated with your existing AI-crawler surface. - [ ] Preferred Sources embed installed near byline or logo, verified on desktop + mobile. - [ ] Theme (light/dark) matches site design system. - [ ] GA4 custom event fires on button click; audience cohort segment created for opted-in readers. - [ ] `llms.txt` updated with the same topic-authority claim the Preferred Sources signal reinforces. - [ ] Author bylines on top 10 organic-traffic pages carry the button (highest-affinity moment). - [ ] Blog post or newsletter announcing the button to your returning audience — asks them to Follow. Everything above is derived from Google's own guidance on the launch. Nothing here is speculative — we're just sequencing what Google recommends into the order that maximises B2B upside. Sources & further reading - [Google blog — Personalize what you see on Search, Discover, News (20 Aug 2026)](https://blog.google/products-and-platforms/products/search/personalize-search-discover-news/) — the canonical launch post. - [Google Search Central — Preferred Sources documentation](https://developers.google.com/search/docs/appearance/preferred-sources) — official embed docs, theme + language attributes, spec. - [TechCrunch — Google gives publishers a new way to fight AI-driven traffic losses (20 Aug 2026)](https://techcrunch.com/2026/08/20/google-gives-publishers-a-new-way-to-fight-ai-driven-traffic-losses/) — press framing of the launch. - [Semrush — Google launches Search Profiles for publishers and creators](https://www.semrush.com/blog/google-launches-search-profiles/) — context on Google's parallel Search Profiles feature for creators. - [Schema.org](https://schema.org/) — the vocabulary Google's grounding pass reads alongside the Preferred Sources signal. *Related:* for the full framework this piece plugs into, see [AI SEO strategy 2026 — the step-by-step B2B guide](/blog/ai-seo-strategy-2026) — the P2 Strategy pillar. --- *This is the machine-readable Markdown alternate of [Google's *Follow* button — the ranking lever B2B teams missed](https://webflur.com/blog/google-preferred-sources-button). Written for AI agents (ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews) that prefer markdown over HTML. For the fully-designed reading experience visit the canonical URL.*