JTSTech Services
← All articles

AI Visibility · August 21, 2026 · 8 min read

Google just shipped a button that outranks your SEO. It's two lines of HTML — and your /blog subfolder doesn't qualify.

On 20 August Google made its Preferred Sources button embeddable, so a reader can mark you as a source they want to see more of without leaving your page. It affects Top Stories, AI Overviews and AI Mode — the surfaces that took your clicks. It costs two lines of HTML. But it attaches to a domain or subdomain and never to a subdirectory, so the /blog most companies publish into cannot be picked. And it only works on people who already found you once, which is precisely what search used to do for you. Here is what it actually is, what it cannot do, and whether it is worth the third-party script.

Written by Jeremy Souffir Founder, JTS Tech Services

The short version: on 20 August Google announced that any eligible site can now embed a Preferred Sources button on its own pages. A reader clicks it, your domain is added to their personal list of preferred sources, and they are returned to the spot on your page they were reading rather than being bounced off to a Google settings screen. From then on your content is more likely to surface for that person in Top Stories, in AI Overviews and in AI Mode, marked with a preferred badge. Google says more than 600,000 unique sources have been selected this way so far, and that people are roughly twice as likely to click through to a preferred source when one is available. The implementation is two lines of HTML. The catch nobody is printing: preference attaches to a domain or a subdomain and never to a subdirectory, so if your content lives at yourcompany.com/blog, the thing a reader can pick is the whole company domain, not the blog. And the deeper catch: this lever only reaches people who already found you. It is a retention mechanism wearing a search-visibility costume.

What exactly did Google ship on 20 August?

Preferred Sources itself is not new. Google rolled it out in May 2026 as a setting inside Search: a reader could go to a Google preferences page, type in publications they wanted more of, and see those sources promoted in their own results. The friction was obvious. Nobody navigates to a settings page to advocate for a website. What changed on 20 August is that the choice moved to where the reader already is — onto your page, as a button you host.

  • The button is embeddable by the site itself, using code published in Google's Search Central documentation.
  • Clicking it adds your source and returns the reader to their position on your page. The previous route sent them to Google and left them there.
  • The effect shows up in Top Stories, in AI Overviews and in AI Mode, in all available languages and locales, with preferred sources marked by a badge.
  • Google's stated adoption figure is more than 600,000 unique sources selected across the feature so far.
  • Google's stated effect is that a reader is about twice as likely to click through to a source they have marked as preferred.
  • It is explicitly optional. You can be selected as a preferred source without ever embedding anything — the button only removes friction.

Whose numbers these are

The 600,000 sources figure and the doubled click-through claim are both Google's own, published in its announcement, and neither has been independently audited. We are repeating them as Google's claims rather than as findings. Treat the direction as credible and the magnitude as marketing until someone measures it from the outside. Nothing in the rest of this post depends on either number being exactly right.

Two different roads to the same answer box. The top lane is ranking: everything you publish competes through one narrow gate and most of it never emerges. The bottom lane is preference: one reader marks you once, and that connection does not go through the gate at all.
Two different roads to the same answer box. The top lane is ranking: everything you publish competes through one narrow gate and most of it never emerges. The bottom lane is preference: one reader marks you once, and that connection does not go through the gate at all.

How do you actually install it?

It is genuinely two lines. Google's documentation gives a script tag that loads its publisher library and a div that the library turns into a button. There are data attributes for a dark theme and for language, an ES module variant if you are on a modern build, and a callback queue if you want to control when the flow starts. If you would rather not run any JavaScript at all, Google also documents a plain deeplink — google.com/preferences/source with your domain as a query parameter — which you can put behind an ordinary anchor tag. That version is not as smooth, because it takes the reader to Google, but it costs you nothing at runtime.

The requirement that will stop most companies is not technical. Your site has to already be showing up in Google's source preferences tool, and the entry has to be a domain or a subdomain. Google's documentation is unambiguous: yourcompany.com and help.yourcompany.com are eligible; yourcompany.com/blog is not.

Preference attaches at the domain and subdomain level only. A subdirectory cannot be picked, so a reader who loves your blog ends up preferring your entire company site — everything else it publishes included.
Preference attaches at the domain and subdomain level only. A subdirectory cannot be picked, so a reader who loves your blog ends up preferring your entire company site — everything else it publishes included.

The mistake this sets up

A marketing team reads the announcement, drops the button at the bottom of every blog post, and reports that the blog is now a preferred source. It is not. The reader has preferred the whole domain. If that domain also publishes pricing pages, press releases, support notices and job ads, all of it is now in the running to be promoted to that person. For a single-brand company that is usually harmless and occasionally helpful. For a business running several distinct properties out of one domain with subfolders, it means readers cannot express the preference they actually have, and you should not pretend the metric measures what you want it to.

Why is Google doing this now?

Because the traffic problem became impossible to keep quiet about. Press Gazette's reporting on the AI Mode rollout collected the numbers publishers have been putting on the record: HubSpot describing losses of roughly 70 to 80 percent of its organic traffic, Chegg reporting a decline near half, DMG Media documenting drops as steep as 89 percent on some queries. Those are individual companies describing their own dashboards rather than a controlled study, and the underlying causes are tangled — algorithm updates, AI answers and changing behaviour all landed in the same window. But the direction is not in dispute, and Google knows what the open web concludes when the referrals stop arriving.

Read in that light, Preferred Sources is Google offering publishers a lever that does not require Google to send more clicks by default. It is closer to a subscribe button than to a ranking factor. And that framing is the most useful thing about it, because it tells you exactly what to expect from it.

The two conclusions that both get this wrong

The dismissive read is that this is a cosmetic gesture from the company that caused the problem, and that installing it legitimises the arrangement. The enthusiastic read is that it is a recovery plan for lost search traffic. Both are wrong, in opposite directions.

  • It is not cosmetic. It reaches into AI Mode and AI Overviews, which is the surface where the clicks actually went. Very few things you can do in an afternoon touch that surface at all.
  • It is not a recovery plan. Every click on that button comes from somebody already on your site. It cannot introduce you to a stranger, and introducing you to strangers is the entire thing search was doing for you.
  • It compounds slowly or not at all. With a hundred readers a month, this is a rounding error. With a real returning audience, it is a way of converting that audience into recurring visibility on surfaces you otherwise cannot influence.
  • It has a real cost that most coverage skips: you are adding a third-party Google script to your pages. Load it async, keep it off pages where performance is revenue, and be honest with whoever owns your privacy notice about what you have added.

The genuinely useful part

Strip the announcement back and it is a signal about where visibility is heading. For twenty years the asset was a ranking — a position you rented from an algorithm, revocable without notice, and every business we work with has now had it revoked at least once. What Google just added is a surface where a human being's explicit choice beats the ranking. You cannot optimise your way into it and no agency can sell you a shortcut to it. The only input is whether someone wanted to hear from you again. That is a harder asset to build and a far harder one to take away, and the companies that spent the last two years building an audience rather than a keyword position are about to find out that they were right.

So what should you actually do this week?

  • Check whether your domain even appears in Google's source preferences tool. If it does not, the button is not available to you yet and no amount of code changes that.
  • Decide which domain or subdomain you want preferred, and be honest about whether that matches the thing your readers actually value. If your content lives in a subfolder, the preference lands on the parent.
  • If you install it, put it where a reader is already satisfied — the end of a genuinely good article, not a popup on arrival. This is a button for people who just got value, not for people deciding whether to stay.
  • Load the script async and check your Core Web Vitals before and after. A visibility feature that slows down your product pages is a net loss on a store.
  • Do not build a reporting line around it. There is no dashboard showing who preferred you, so any number you present internally will be invented.
  • Spend the rest of that afternoon on the thing that actually feeds this: a reason for someone to want you again. The button is plumbing. The audience is the asset.

Where we fit

The reason this kind of change keeps catching growing companies out is not that any single item is difficult — this one is two lines of HTML. It is that nobody owns the standing question of what the machines that decide your visibility currently see when they look at you, across Google, ChatGPT, Gemini and Perplexity at once. So each announcement gets read, forwarded, half-implemented and forgotten, and the compound effect over a year is a business whose visibility is drifting for reasons nobody can name. Retaining JTS means that question has an owner. We fetch your site the way each of these systems does, check what your feed, your edge rules, your pages and your logs actually hand back, tell you which of the week's announcements touch you and which are noise, and hand you a short ordered list rather than a newsletter. On this specific change that means confirming your eligibility, choosing the right domain, installing it without hurting your page speed, and — the part that matters more — making sure that when a reader does mark you preferred, the next thing Google shows them is worth the click they just promised you.

Sources

← Back to all articles

Keep reading

AI Visibility

In 93% of free ChatGPT answers, nobody opens your page. Here's the 200 characters it reads instead.

Security

The payload isn't in the model. It's in the notes your agents keep for each other.

AI

The “permanent” price cut lasted twelve weeks. Your AI bill now has peak hours.

Free AI Shopping Visibility audit

Do you know what Google, ChatGPT and Gemini currently see when they look at you?

We fetch your site the way each of them does — feed, edge, pages and logs — and send back a prioritised report on what they read, what they miss, and what to fix first. Free, within three business days.

Get your free audit