A post came across my feed this week arguing that Google has quietly handed every website a button that makes AI show you more, and that most webmasters will sleep on it.
The second half of that is almost certainly right. The first half needs a closer look, and I went and did the looking, because I nearly reposted it.
What I got wrong first
My instinct was that the AI part was hype. Google launched preferred sources back in August 2025 as a Top Stories feature, it was about letting readers pin the publications they trust, and I assumed the AI Overviews angle had been bolted on by people who wanted a more exciting headline.
I was wrong, and it took about four minutes to find out. Google's own publisher guidance, updated on 20 August, does name AI Mode and AI Overviews. So the claim is not invented.
What is invented is the precision.
Key Takeaways
- What I got wrong first
- The bit nobody has mentioned, and it is the important one
- What this actually is
- Hints and tips
Here is what Google says about Top Stories: your content is "more likely to appear".
Here is what it says about AI Mode and AI Overviews: your content "can be highlighted with a 'preferred' badge".
One of those changes whether you show up. The other changes what you look like when you already have. I have read the page three times and I cannot make the second sentence mean the first. If Google meant "cited more often in AI answers", that sentence was available to them and they wrote a different one.
I want to be fair about the limits of that reading. Google not documenting something is not proof it does not happen. Maybe preferred sources does lift AI citation frequency and the documentation simply lags. But I am not going to tell you it does, because right now nobody can show me where it says so.
There is a smaller thing here too. The trade article being quoted as the authority for the AI claim does not actually mention AI Overviews or AI Mode anywhere in it. The conclusion holds up, from a different document. The receipt attached to it does not. That happens a lot in this category, and it is worth developing a reflex about.
The bit nobody has mentioned, and it is the important one
Not every site can be chosen.
Google restricts eligibility to domains and subdomains. example.com works. code.example.com works. example.com/blog does not.
If your content lives in a subdirectory of a domain you do not own, and a great many businesses' best writing does, then a reader who wants more of you cannot select you. They can only select the site you are publishing on. You would be building preference for your landlord.
Go and work out where your content actually resolves before you do anything else. It takes a minute, and if the answer is bad, that is much better to know today.
What this actually is
Strip out the mechanics and preferred sources is somebody who already knows you telling Google they want more of you.
Think about what has to be true for that to happen. They found you. They read you. They liked it enough to want more. Then they took a deliberate action to say so.
Every single one of those steps happens after discovery. This feature cannot introduce you to anyone. It makes you louder to people who already chose you once.
That is genuinely useful and I am going to use it. But it is close to the opposite of the thing I get asked about every week, which is how to get named by an AI to somebody who has never heard of you, in an answer you will never see, built from sources you do not control. Preferred sources does nothing for that. It rewards people who have already solved it.
So treat it as a loyalty tool that happens to live in search. It belongs beside your newsletter signup, and it should be funded like one.
Hints and tips
Check you can be chosen at all
Domain or subdomain only. Open the source preferences tool, look for your own site, and if it is not in there then the button is decoration. Do this before anything else, because it is the one answer that makes the rest of this either relevant or irrelevant to you.
The install is two lines
A script tag, and a div carrying the google-add-preferred-source-btn attribute. That is the whole job. The advice going round suggests pasting Google's documentation into a chatbot and telling it which CMS you run so it can walk you through the implementation, which rather oversells the difficulty of two lines of HTML.
There is also a plain deeplink, google.com/preferences/source with your URL on the end, for anywhere you cannot run script.
Ask a satisfied reader, and ask once
The end of an article beats the homepage every time. Someone who has just finished reading you is the only person on your site with a reason to press it. A homepage visitor has no idea yet whether they want more of you.
Then leave it alone. This is a one-time action per reader. A sticky bar nagging people to press a button they pressed last week is a worse experience than asking cleanly at the bottom of something good.
Your email list will beat your website
That deeplink works in a newsletter, and your list is by definition people who already put their hand up to hear from you more often. They will take this action at a far higher rate than a passing visitor will. My guess is that almost everybody will put the button on their website and never think about the list, which is the wrong way round.
Do not move budget for it
Nothing here improves your odds of being recommended to a stranger. Defund the hard problem to chase the easy one and you end up with a slightly more loyal small audience and the same invisibility.
When you do measure it, judge it on loyalty. Returning visitors, direct traffic, repeat opens. Go hunting for the effect in an AI visibility score and you will not find it, then conclude the feature failed while it was quietly doing its actual job.
The honest summary
It is real. It takes ten minutes. It is a good use of that time if you publish regularly and have readers you want to keep, and Google's own SVP of knowledge and information has said publicly that people are twice as likely to click through to a site once they have marked it as preferred. That figure has never made it into the documentation, and a doubling among people who just went out of their way to choose you is roughly what you would expect before the feature does anything, so hold it loosely.
It is also being described as an AI visibility lever when Google's own words describe a badge, and it can only ever act on people who already know your name.
Both of those things are true at once, and the second one is why I am not particularly excited.
Go and ask an AI to describe your business. Not to rank it, to describe it. If it gets you wrong, no button on your website is going to fix that, and that is the job worth doing first.
We published the full documentation analysis on SearchScore: an up-rank in Top Stories, a badge in AI answers.
Google gave your readers a button. It is not the button everyone thinks it is.
About the Author
Ronnie Huss is a serial founder with multiple successful product launches. He builds technology products across SaaS, AI, and blockchain. Learn more about Ronnie Huss →
Follow on LinkedIn
Written by
Ronnie Huss Founder and Consultant, AI Search Visibility, SEO and ConversionSerial founder with multiple successful product launches across SaaS, AI tools and blockchain. Based in London. Writing on AI agents, GEO, RWA tokenisation, and building AI-multiplied teams.