Google’s New Preferred Sources Button: Your AI Overviews Publisher Recovery Playbook

Google just handed publishers something they have been asking for since AI Overviews rolled out. On August 20, Google announced an embeddable Preferred Sources button that any site can drop onto a page with two lines of code. One click from a reader sets that outlet as one of their Preferred Sources across Google Search, AI Overviews, AI Mode, and Top Stories, then sends them right back to the article they were reading (Google).

You have watched AI Overviews eat referral clicks all year. Your clients have watched it too. The click cliff is real, and rescue plans that lean on more content alone are running out of runway. The preferred sources button gives you a different lever. It moves the loyalty signal out of a hidden settings menu and puts it directly on the page, where reader intent is highest.

This is your operator guide. Not a hype piece. What the button actually does, who benefits, how to install it on a client site today, and where to place it so that click-through goes up instead of sideways.

What the preferred sources button changes on the page

Before August 20, a reader who wanted to see more of your content in Google had to open Search personalization settings, find the source preferences tool, and add your site manually. Most readers never made that trip. Google reported 600,000 unique sources selected since the feature expanded, which sounds large until you divide it across the global Search userbase.

The preferred sources button collapses that whole flow into one tap. The reader stays on your page. The Google account gets the preference. Your future stories start showing up in that reader’s Top Stories carousel, AI Overviews responses, and AI Mode answers. This is a permanent signal, not a session cookie.

Two things worth calling out. First, only domain-level and subdomain-level sites are eligible. If your client’s blog lives on a subfolder of a shared domain, the preference attaches to the parent domain, not the blog (Google Search Central). Second, the button is available globally in every language where Google Search operates, so a Canadian or UK client is not waiting for a rollout window.

Who actually benefits from the preferred sources button

Three client profiles get the most out of this feature, and each one has a different install pattern.

Local news and vertical publishers benefit most. Their readers already return two or three times a week. The button converts that habit into a permanent Top Stories advantage. For a home services or senior services vertical publisher, that is direct competition against national brands who get default Top Stories placement.

Agencies with owned-and-operated content sites are the second group. If you publish playbooks, industry roundups, or thought leadership on a site you control, this is a straight referral recovery tool. Every reader who clicks the button gives you a permanent seat in their AI Overview and AI Mode results.

The third group is client sites with strong newsletter or community engagement. If a client already sends a weekly email or runs an active Facebook group, the button turns those loyal readers into ranked sources across every future Google session. This is exactly the follow-up move for anyone who worked through the publisher AI Overviews playbook earlier this year.

The two-line install for the preferred sources button

Google’s Search Central documentation lays out three install paths. The standard JavaScript path is the one you want for 90% of client work. Here is what it looks like.

Add one script tag to the head of the page. Google recommends the head element, not the body:

<script async src="https://news.google.com/swg/js/v1/publisher.js"></script>

Add one div tag anywhere in the body where you want the button to appear:

<div google-add-preferred-source-btn></div>

That is the full install. The library renders a Google-styled, auto-translated button in the reader’s language. You can set the theme to dark or light with a data-theme attribute. You can force a specific language with data-lang. That is it.

If your client’s CMS blocks script tags in the head, use the deeplink path. You add a plain anchor link that opens the source preferences tool with your client’s domain pre-filled:

<a href="https://www.google.com/preferences/source?q=example.com">Add as Preferred Source</a> where you swap example.com for your client’s domain.

The deeplink version does not send the reader back to the article automatically. That is a real conversion cost. Only fall back to it when JavaScript is genuinely off the table.

Where to put the preferred sources button on a client site

Placement matters more than most agencies realize. The button competes with your email signup form, your Google follow prompt, your comment section, and every affiliate CTA on the page. Three placements have shown the best early behavior across sites that installed the button in the first week.

End of article, above the author bio. Readers who finish a full article are your highest-intent audience. They already decided this content was worth their time. Put the button between the last paragraph and the byline, in the same visual weight as a follow-on-social row.

Sticky footer bar on category and archive pages. Category browsers are exploring your site with breadth, not depth. A persistent, low-friction button in a footer bar catches them before they bounce back to Search. Keep it dismissible so it does not annoy paying subscribers.

Post-comment thank-you state. If your client site accepts comments or reader questions, the confirmation screen after a submission is high-intent real estate. The reader just invested effort in your content. Show the button on that state.

What you want to avoid is dropping it in a sidebar next to ten other widgets. The button loses its meaning if it lives in a graveyard of forgotten CTAs. Treat it as a first-class conversion element, not a checkbox on your homepage template.

How the preferred sources button ties into your bigger AI Overviews plan

This button is not a standalone play. It is the loyalty layer that sits on top of every other AI Overviews recovery move your agency is running. Your GEO content audit tells you which of a client’s pages are getting scraped without citation. Your passage-level citation signals tell you which sentences AI Overviews likes to quote. The preferred sources button gives readers who already trust your content a way to push it back into that quotation pool.

Here is the operator sequence. Fix citation gaps on the ten pages driving the most impressions. Add the preferred sources button to those same pages, plus the site’s top-level category archives. Push a two-week email or newsletter campaign asking loyal readers to click it. Measure your Top Stories and AI Overviews impressions for those pages in Search Console over the next 60 days. That is a complete referral recovery loop that most agencies are not running yet.

The contradictions between paid search and AI Overviews also matter here. When your organic content gets Preferred Source status, it starts appearing above and around your paid ads in AI Mode. That changes what your paid team needs to bid on, because the loyal-reader signal is now baked into the algorithm’s response, not just the ranking layer.

What to measure once your preferred sources button is live

Do not judge the button on click count. That is the wrong metric. Every click is a permanent preference. One click per reader is the maximum, and that reader now compounds across every future search they run.

Measure four things in Search Console and GA4. Track Top Stories impressions for the pages where the button lives, week over week. Track AI Overviews and AI Mode citations if your client has access to the AI performance report in Search Console. Track referrer sessions from google.com to those pages, filtered for returning users, since Preferred Source signals mainly influence repeat behavior. And track your newsletter conversion rate on pages that carry both the button and the signup form, because a lift in one usually means a lift in the other.

If you are running Facebook or Meta ads to drive newsletter growth for the same client, the 30-day brand monitoring playbook we published earlier this year plugs directly into this measurement stack. Preferred Source lift shows up first in returning-user branded search, which is one of the signals that playbook tracks.

Do not expect a click-through spike in the first two weeks. This is a compounding signal, not a paid campaign. The first real lift shows up around week four or five, when Google’s ranking layer has enough repeat sessions to weight the preference confidently.

The AI search opt-out playbook we published for lead-gen clients pairs well with this too. Publishers who opted out of AI training but stayed in Search now have a button that gives them a fighting chance in AI Overviews without giving up their opt-out stance. That is a rare win for the publisher side of the fence.

Book time with our team through our free consultation if you want to walk through where the preferred sources button fits into your specific client stack. Let’s Grow!