How to Become a Preferred Source in Google AI Overviews (2026)
Google's new Preferred Sources button is two lines of code. What it actually does, who's eligible, why it isn't a ranking factor, and how we installed it on our own site. A loyalty punch card for search: it brings back readers who already chose you.
Somewhere on your site right now there's a reader who likes you. They came back a third time this month. They'll never tell Google that, because until three weeks ago there was no easy way to. Now there's a button.
A preferred source is a site a reader has personally chosen in Google's source preferences tool. Once they pick you, your content gets a "preferred" badge and shows up more often for that reader in Top Stories, AI Overviews, and AI Mode. On August 20, 2026 Google shipped an embeddable button so readers can do that from your page in one click. The install is two lines of HTML. Eligibility is the catch: your domain has to already appear in Google's source preferences tool, and only domains and subdomains qualify, not subdirectories. It is not a ranking factor. It changes results for the readers who chose you, nobody else. Think of it as a loyalty punch card for search. It brings back people who already like you. It won't find you new ones.
That's the whole mechanic. The interesting part is what it says about where Google is steering traffic, and what that means if you publish for a living.
What changed on August 20
Preferred Sources isn't new. It started as a setting buried in Google's source preferences tool, mostly aimed at news readers who wanted their outlets to show up in Top Stories. Earlier this year Google extended it into AI Overviews and AI Mode, so a selected source can carry its badge inside the AI answer itself.
The problem was friction. A reader had to leave your page, find the tool, search your name, confirm, and come back. Almost nobody did.
On August 20 Google published an embeddable button that closes that loop on your own page. Reader clicks, picks you, lands back where they were. Google's announcement put the count at more than 600,000 sources selected by readers, up from about 345,000 in late May (Google, August 2026). Same post claims a reader is roughly twice as likely to click through to a source once they've marked it preferred.
Twice. For a channel that's been bleeding clicks to AI answers all year, that's the number that made us stop and read the docs.
How the button works
Two lines, per Google's own documentation. A script in your <head>:
<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>And a div wherever you want the button to show:
<div google-add-preferred-source-btn data-theme="light"></div>That's it. Google renders a localized, Google-styled button. Swap light for dark to match your page. Add data-lang="en" if you want to pin the language. There's a JavaScript SDK if you'd rather trigger the flow from your own UI, and a deeplink for places you can't run script, like a newsletter footer:
https://www.google.com/preferences/source?q=yourdomain.comSigned-in readers get an "Add as a Preferred Source" confirmation. Signed-out readers get a Google sign-in first. Both come back to your page.
The eligibility rule most guides skip
Here's where a lot of the "15-minute playbook" posts get sloppy. The button doesn't make you eligible. It only lowers the friction on an opt-in that was already possible.
Two things have to be true. Your site has to be a domain or a subdomain. yourbrand.com works, news.yourbrand.com works, yourbrand.com/blog does not. And your domain has to already appear when you search for it in Google's source preferences tool. If it doesn't show up, no amount of code changes that.
The tool itself carries one more line worth reading twice: sources that are not updated regularly may be unavailable. Freshness keeps you on the list. Go quiet for a season and the punch card can disappear.
So check first. Open the tool, type your domain, see if it's there. Thirty seconds. Then decide whether to spend the fifteen minutes.
Does it affect rankings? No. Here's what it does affect.
Google is plain about this and so are we. Preferred Sources is not a ranking signal. Selecting you changes what that reader sees. It does nothing for the person who has never heard of you.
What it does change is worth naming, because it's a different kind of citation than the one everyone's chasing. Most answer engine optimization work is about cold citation: convincing Google's models to pull your page into an answer for a stranger. That's the hard, slow game we write about in how to rank in AI Overviews.
This button creates something else. Call it return-reader citation: your page badged inside the AI answer because the person asking already chose you. You don't earn it from the algorithm. You earn it from the reader, one click at a time, on your own page.
That distinction decides whether the button is worth anything to you.
Who should bother
Sites with a returning audience. That's the honest filter.
If you're a news outlet, a trade publication, or a blog people come back to, this is a real lever, because you have readers who would punch the card if you asked. If your traffic is one-and-done search visitors who never return, the button will sit there. Nobody punches a loyalty card at a place they'll never visit again.
Same logic within a site. Put the button where readers already show up more than once and read to the end. Skip the pages nobody finishes. Pair it with your newsletter ask, since it's the same request in a different shape: you liked this, here's one click to see more of it.
And if you're an agency or a consultancy publishing to be found rather than followed, be realistic. The pages that already lead an AI Overview are the ones where a badge compounds. The rest of the site can wait.
How we installed it on automatonagency.com
We're an AEO shop that runs its own autonomous SEO/AEO engine on this site, so we're not going to write about a lever we didn't pull.
First, the eligibility check. We typed our domain into the source preferences tool. It's there, favicon and all.
Second, placement. We put the button in two spots on every insights post, under the byline and in the footer next to the related-reading block, and once on the home page. Not on case studies, not on utility pages. The reasoning was the filter above: our insights posts are where we already lead a handful of AI Overviews, and where the same readers keep showing up.
One build note, since the docs won't tell you this. Google's script scans the page once on load and never again, so on a site with client-side navigation the drop-in button disappears after the first page change. We used the manual-init path from the docs instead and render our own button that calls Google's API on click, with the deeplink as a fallback if the script never loads. If your site is a single-page app, budget twenty minutes for that instead of two.
Third, what we're measuring. Search Console doesn't have a Preferred Sources report yet, so the read is indirect. We're watching click-through on the queries where we already hold an AI Overview citation, week over week, and we'll report the first month's numbers here whether they move or not. That's the deal with everything we publish about generative engine optimization: show the work, including the flat results.
What to expect, honestly
Small numbers at first. A button only converts readers who already like you, and most sites have fewer of those than they think. If you get a few dozen selections in the first month, that's normal. The lift shows up as a slow widening of click-through on queries you were already appearing for, not as a new stream of traffic.
Which is fine. The click Google is offering here is a click you were going to lose to the AI answer anyway. Getting some of it back, from the readers who care, is the point.
Punch the card. Then go earn the cold citations, because the button doesn't do that part. If you want a read on which of your pages are actually positioned for either kind, that's what our Revenue Audit is for.