Google Just Shipped a “Rank Higher in AI Overviews” Button. Almost Nobody Has Installed It
On August 20, Google released an embeddable Preferred Sources button: two lines of HTML that let readers star your site across Top Stories, AI Overviews, AI Mode, Discover, and Google News. Google says users who star a source click it twice as often. The SEO industry, the people most desperate for AI-search visibility, have largely ignored it.

Here is the state of play one day after launch. Google says readers have already selected more than 600,000 unique sources, a number that has roughly tripled since May, and that people are “twice as likely to click through to a Preferred Source.” Yet as of this writing, the most connected people in search marketing have not put the button on their own sites, and not one major SEO publication has published a practitioner playbook for it.
That is a window. It is also worth understanding exactly what you are installing, because I read the JavaScript Google ships with the button, and it tells a more specific story than the announcement does: this is not a ranking trick. It is Google porting your repeat-reader signal into AI search. That distinction decides whether the button is worth anything to your site, and I will get into both.
What the button actually does
Preferred Sources is Google’s personalization layer for search: a reader marks the sites they trust, and Google surfaces those sites more prominently for that reader. The feature has existed since mid-2025, but until this week the only way for a reader to star you was to dig through Search settings or follow a plain link. The new version is an interactive, Google-styled, automatically localized button that lives on your pages.
When a reader clicks it, a Google panel opens with one Add button, the site is saved to their preferences, and the reader lands back exactly where they were. That return trip is part of this release: Google refreshed the flow during the August 20–21 launch specifically so readers stop getting stranded on Google’s settings page, which is where every earlier method sent them.
Once starred, here is what Google’s documentation promises on each surface, in Google’s own words, which matter:
| Surface | What happens for users who starred you |
|---|---|
| Top Stories | Your content is “more likely to appear,” highlighted with a “preferred” badge |
| AI Overviews | Your content “can be highlighted with a ‘preferred’ badge” |
| AI Mode | Same “preferred” badge on your links inside AI responses, plus Preferred Sources are called out in the new link carousels Google launched in May |
| Discover / Google News | Starred sites are part of the same preference set Google now uses to personalize feeds |
| Search personalization | Readers can also star you manually at google.com/preferences/source |
Swipe sideways to see the full table
Read the wording carefully. In Top Stories, being starred makes you “more likely to appear”: that is a boost. In AI Overviews and AI Mode, the documented effect is a badge and call-out for the users who already chose you. Google is not promising that starring moves you up inside the AI answer itself. The practical result is still real: when your link shows up for a starred reader, it carries a star, and Google’s internal studies say those readers click twice as often. But anyone selling this as “install button, rank higher in AI Overviews for everyone” is overselling it.
Two lines of code
The standard implementation is a script tag plus one div. Google hosts the library, styles the button, translates it, and handles the dark/light theme and language overrides:
<!-- in the <head> --> <script async src="https://news.google.com/swg/js/v1/publisher.js"></script> <!-- anywhere in the body where the button should render --> <div data-preferred-sources-button=""></div>
If your CMS cannot take custom JavaScript, the fallback is a deeplink that works as a text link, an image, a social post, or an email-newsletter line:
<a href="https://www.google.com/preferences/source?q=example.com"> Add as Preferred Source </a>
Eligibility has one trap worth flagging before anyone installs anything: only domain-level and subdomain-level sites qualify. www.example.com and blog.example.com are eligible; example.com/blog is not. Google’s docs also say your site must actually appear in the source-preferences tool, so test your domain in the search box at google.com/preferences/source before you ship the button. One reassuring data point for smaller sites: commenters in the search community have confirmed that sites outside Google News, such as personal blogs, can be added.
The numbers: a fast-growing pool of starred readers
Google has disclosed selection counts three times, and the curve is steep enough to care about:
Swipe sideways to see the full chart
Context for why Google is pushing this now. Pew Research tracked 68,879 Google searches from 900 US adults and found users clicked a traditional result in 8% of visits when an AI summary appeared, against 15% without one, and just 1% ever clicked a link inside the summary. SparkToro and Similarweb found 68% of US Google searches now end without any click, up from 60% in 2024, while Google told I/O 2026 that AI Mode has passed 1 billion monthly users with queries doubling every quarter. Clicks are scarcer, and Google is handing publishers a way to claim a protected slice of what remains. Barry Schwartz of Search Engine Roundtable said what many publishers feel: “I mean, it is nice Google is making an effort with these preferred sources but I’d prefer the Google traffic from 5 years ago versus having preferred sources.” Fair. But the old traffic is not coming back, and this is the only official, penalty-safe lever on the table.
Swipe sideways to see the full chart
So who has actually installed it?
Almost nobody in the SEO world. That is the finding, and it is easy to verify:
- The interactive button launched on August 20. Everything before it was the clunkier deeplink, which has sat in Google’s documentation since January 30, 2026. For eight months the deeplink was available, and the SEO mainstream never picked it up.
- Even the messenger hasn’t shipped it. Barry Schwartz, who has covered every Preferred Sources milestone since the test began, wrote about the new embed code on August 21 and added: “which I will add to this site soon but until then, make us a preferred source by clicking here.” The most plugged-in reporter in search marketing is still on the deeplink.
- The trade press treated it as news, not a playbook. Search Engine Land, Search Engine Roundtable, PPC Land, TechCrunch, PYMNTS, and The Next Web all ran announcement coverage on August 20–21. None has published an implementation guide for practitioners.
- The one vertical that adopted early was news media. The New York Times and Digital Trends have promoted their deeplinks on Facebook, NBC stations published “how to add us” guides as far back as September 2025, and Indian news sites (The Wire, Economic Times, Mint) shipped sitewide banners, so aggressively that uBlock Origin users began writing filter rules to remove them by November 2025. “Most News sites are littered with it,” one user complained.
- A handful of independent SEOs got there first. Suganthan Mohanadasan added the deeplink version to every post on May 27, the day the AI Overviews expansion was announced, calling it “hard to think of a higher ROI piece of front-end work right now.” Marie Haynes runs the same ask on her content.
So the accurate version of the headline is this: news publishers installed the earlier, uglier version, and everyone else in the search economy, agencies, in-house teams, affiliate publishers, SaaS blogs, has not installed anything. The interactive button is 24 hours old, which means the first-mover window for the rest of the industry is open right now, and windows like this close quietly.
I read the button’s JavaScript. It says more than the announcement.
This is the part nobody has reported yet. The script tag points to news.google.com/swg/js/v1/publisher.js. The /swg/ in that path stands for Subscribe with Google, the infrastructure Google built for publisher paywalls, subscriptions, and the Google News Initiative. I pulled the library (version 1.0.160) and read it.
What is inside:
- The Preferred Sources button runs on the same event system as subscription buttons, paywall impressions, and Showcase regwalls. In the code, adding a preferred source sits next to
IMPRESSION_SUBSCRIBE_BUTTONandIMPRESSION_SHOWCASE_REGWALL. Google did not build a new system for this feature. It bolted it onto its loyalty-and-subscriptions stack. - The library exposes a small API (
preferredSource.api.addPreferredSource()) with four statuses: unspecified, already added, ineligible, and success. The standard button auto-hides itself for readers who have already starred you, so the CTA disappears once it converts. With the advanced implementation you can fire the flow from your own design, meaning a newsletter-style “Follow us on Google” banner can use the exact same machinery. - Set the script attribute
preferred-sources-control="manual"and the button stops auto-initializing, which is how custom implementations take over.
Who this actually helps (and who should skip it)
| Your situation | Verdict | Why |
|---|---|---|
| News or media site with repeat readers | Install now | Every loyal reader you convert gets a starred version of Google. This is the segment Google built it for, and news sites proved the demand exists |
| SaaS, content brand, or blog with an email list or community | Install now | The button on pages plus one deeplink ask in the newsletter is the whole play. Cheapest audience-to-visibility conversion available |
| Agency managing client sites | Install for clients with audiences | This is a client-ready recommendation today: two lines of code, one newsletter mention, zero penalty risk. The agencies that ship it first will own the case studies |
| Affiliate or programmatic site with no repeat readers | Deeplink later, audience first | The button only converts people who already like you. Cold traffic will not click it. The strategic fix is the same one SEOs keep avoiding: build the loop that makes readers return |
| Site on a subdirectory (example.com/blog) | n/a until restructured | Subdirectories are not eligible. Only domains and subdomains can be starred |
Swipe sideways to see the full table
What the button cannot do
Three honest limits, because this industry has been burned by magic buttons before:
- The AI-surface badge is personalized to the reader who starred you. In AI Overviews and AI Mode, the “preferred” label shows to users who chose your site. It is not a global ranking boost, and other readers will never see it. The win is compounding loyalty economics, not a position change for the world.
- The 2x click figure is Google’s own. Google cites “earlier studies” without methodology, sample, or baseline. Directionally it is believable, starred sources are the whole point of the feature, but treat the magnitude as a vendor claim until independent clickstream data confirms it.
- Readers have a short list, and banner fatigue is real. The uBlock filters written against news-site banners are the cautionary tale: the sites that shouted hardest got blocked. One well-placed ask beats a sitewide takeover.
How to install it properly
The ten-minute version:
- Check eligibility. Go to
google.com/preferences/source, type your domain in the search box, and confirm it appears. If it does not, the button will show readers an ineligible state. - Choose the domain level. If your content lives on
www.example.com, use that. If a subdomain likeblog.example.comis your publication, that subdomain is the eligible unit. Subdirectory sites are out. - Add the two lines. Script in the head, button div in your article template. End-of-article and under the byline are the two placements that respect the reader; avoid above-the-fold banners.
- Put the deeplink everywhere JavaScript does not go. Email newsletter footer, post-signup confirmation page, one social post. The link format is
https://www.google.com/preferences/source?q=yourdomain.com, and Google publishes official translated badge assets you can download. - Ask once, clearly. The conversion copy that works is the honest one: “Want to keep seeing our links in Google’s AI answers? Star us as a preferred source.” Newsletter subscribers are your warmest pool, and the SwG plumbing suggests Google already treats subscriptions as preference signals anyway.
How to measure it
There is no Preferred Sources report in Search Console; Google folds any referral impact into normal organic and News performance data. So measure it the manual way:
- Watch the new generative-AI performance reports in Search Console (AI Overviews and AI Mode views) for trend changes after your install, while accepting they are site-wide, not button-specific.
- Track Discover and Top Stories referrals separately in your analytics; those are the surfaces where the documented boost (“more likely to appear”) applies.
- Ask one real human, a teammate or a subscriber, to star you from the button, then have them run queries where your content appears in an AI Overview and confirm the badge renders. Because the feature is personalized, that is the only way to see it with your own eyes.
- Count button conversions if you use the advanced implementation: the API returns a success status you can log as an event.
The bottom line
Google just shipped the first official, user-driven visibility lever for AI Overviews and AI Mode, priced at two lines of HTML, with zero spam-policy risk in a season when buying AI mentions has become a documented penalty risk. The pool of readers who use Preferred Sources has multiplied since May and will keep growing as AI Mode scales past a billion users. The news industry adopted the clunky early version. The rest of the search economy, including nearly every SEO you have ever read, has installed nothing.
The button does not create loyalty. It converts it. If your site has readers who come back, install it this week, while the ask is still fresh and the starred slots in your readers’ Google are still unclaimed. If your site has no readers who come back, you just found out what your actual SEO problem is.
Sources
- Google (Mrinalini Loew), Personalize the content you see on Search, Discover, and News, Aug 20, 2026 (button launch, 600,000+ selections)
- Google (Duncan Osborn), New ways to find your favorite sources and original content in AI Search, May 27, 2026 (AI Overviews/AI Mode expansion, 345,000 selections, 2x click claim, eligibility)
- Google Search Central, Guide to Preferred Sources in Google Search for Web Publishers, updated Aug 20, 2026 (implementation, deeplinks, subdomain rules)
- Sarah Perez, TechCrunch, Google gives publishers a new way to fight AI-driven traffic losses, Aug 20, 2026
- Barry Schwartz, Search Engine Land, Google makes the Preferred Source button more seamless, Aug 20, 2026 (200,000 May baseline)
- Barry Schwartz, Search Engine Roundtable, Google Preferred Source Button Now Keeps You On The Site, Aug 21, 2026, and Google AI Mode & AI Overviews Gain Preferred Sources, May 28, 2026
- Glenn Gabe, post on X, Aug 20, 2026 (button code, 600,000 figure)
- Suganthan Mohanadasan, Preferred Sources just arrived in AI Mode. I added the button the same day., May 28, 2026
- r/uBlockOrigin, filter rules against Preferred Source banners, Nov 2025
- Pew Research Center, Google Search Results with AI Summaries and Clickthrough Behavior, Jul 2025 (8% vs 15% click rates, 1% on summary links)
- Rand Fishkin, SparkToro, 68% of US Google searches end without a click, Jun 2026; Google I/O 2026 AI Mode figures reported therein
- Firsthand inspection of
news.google.com/swg/js/v1/publisher.js(v1.0.160) by the author, Aug 21, 2026




