Google Preferred Sources Button Is Live: The Embed Playbook

Google just handed publishers a small piece of code that could reshape how your content shows up in Top Stories, AI Overviews, and AI Mode. On August 20 the company released an embeddable Google Preferred Sources button that readers can click right on your site. One click marks your domain as their preferred source across Google, then sends them straight back to what they were reading.

Two lines of HTML. That is the whole implementation for the standard version. If you write, publish, or manage content for a living, this is one of the more useful 15-minute changes you can make this month. Here is what the button actually does, why it matters for AI search visibility, and the exact embed playbook you should run today.

Who this is actually for. Run one filter before you spend the 15 minutes. Preferred Sources only feeds Google’s news surfaces. A reader picks you, and your fresh content then shows up more in Top Stories, plus the AI Overviews and AI Mode answers that ride on news and timely queries. That makes this a tool for news publishers and trade press. If you run a lead-generation or local-service business, an HVAC company, an insurance agency, a solar installer, your pages almost never reach Top Stories, so the button will do nothing for you.

There is a fast way to know your camp. Search your own domain in Google’s source preferences tool. If it appears, readers can mark you preferred, so keep reading. If it does not, your site is not in Top Stories today, and no button changes that. Put the time into the content and links that get you ranked instead.

What The Google Preferred Sources Button Actually Does

Preferred Sources launched last year as a feature buried inside Google’s source preferences tool. Readers had to search for a publication by name, confirm the selection, then bounce back to whatever they were doing. The friction cost publishers most of the opt-ins that might have happened. The new Google Preferred Sources button closes that loop by living on your own page, so the reader never leaves.

According to Google’s August 20 announcement on The Keyword, more than 600,000 unique sources have already been selected by readers. That number was around 345,000 in late May, so adoption is climbing fast even without the new button. Google also said users who select a preferred source are about twice as likely to click through when that source appears in results.

Once a reader picks your domain, three things happen. In Top Stories, your fresh content is more likely to surface and can carry a preferred badge. In AI Overviews, your links can appear with the same badge inside the summary itself. In AI Mode, your stories can appear flagged inside the conversational answer.

Eligibility is set at the domain or subdomain level. Individual article pages and subdirectories are not eligible on their own. If your domain appears in Google’s source preferences tool when you search for it, you qualify. If it does not, you have a Top Stories inclusion problem to solve first before the button will do anything for you.

Two facts in Google’s own documentation should shape how hard you chase this. First, the level rule is strict. A root domain like yourbrand.com counts and a subdomain like news.yourbrand.com counts, but a subdirectory like yourbrand.com/blog cannot be a preferred source, a limit that trade coverage from PPC Land spells out. Second, the button is optional. Google’s documentation says the embed button and the deeplink are only examples of how to build your audience, and that neither is required for your site to appear as a preferred source.

That optional framing sets the priority. Eligibility is earned by surfacing in Top Stories, not by pasting in code, so the button just lowers the friction on an opt-in the reader already wanted to make. The reach is wide, too. Per PPC Land, Preferred Sources became available for Top Stories in every language where Google Search operates after an April 30, 2026 refresh that added deeplinks and translated button assets, and Google’s Search Central documentation now carries a last-updated date of August 20, 2026.

Why The Google Preferred Sources Button Matters More Than It Looks

This is not a minor UI tweak. It is a signal about how Google plans to route traffic in an AI Overviews world. Publishers have been watching referral traffic soften as AI Overviews answer more questions inside the results page, a shift we covered in our post about publishers blocking Google AI Overviews. The preferred source badge is Google’s counter-offer. Get readers to pick you. Earn more visibility inside the AI answer, not just around it.

Two things make this different from the usual publisher tools Google ships. First, the flow is designed for opt-in, not audit. Second, the badge follows the reader across surfaces, so a selection made on a Top Stories carousel also carries into AI Overviews and AI Mode results the same reader sees. That is a signal you own, not one you rent from a ranking algorithm.

That cross-surface badge is part of a larger shift. Getting named inside an AI answer is becoming its own distribution channel, and the pattern repeats from one engine to the next. Our breakdown of how to get cited by Grok shows the same lesson on X’s assistant, where earning the mention beats gaming the feed.

The click-through claim also lines up with how we have seen personalized surfaces perform. If Google is telling the truth about the 2x click-through lift, that is a meaningful number for a channel that has been losing ground. For context, our review of what Google Discover AI personalization means for advertisers flagged the same pattern. Personalization is becoming the surface, and earning that pick is the new distribution job.

The 15-Minute Embed Playbook

Here is the exact sequence to get the button live on your site today. It assumes you have direct access to your theme or CMS templates. If you run WordPress and use a page builder, you can drop the div anywhere in a custom HTML block, but keep the script tag in the head via a header snippet plugin.

Step one. Confirm your domain is eligible. Go to Google’s source preferences tool. Search for your domain. If it appears, you qualify. If it does not, your site is not currently surfacing in Top Stories, so save yourself the trouble and go work on ranking first.

Step two. Add the loader script to your site head. Google’s Search Central documentation for the Preferred Sources button lists the exact tag. The standard integration is one script from news.google.com plus a div carrying the google-add-preferred-source-btn attribute wherever you want the button to render.

Step three. Pick your placement. Do not stuff it into every page. The best spots are the top of your article template, right under the byline, and a persistent sidebar module. If you run a newsletter signup or an email capture module, place the preferred source button next to it. Same audience. Same intent to hear from you again.

Step four. Set the theme. The button accepts a data-theme attribute with light or dark values. Match your site theme so it reads as native, not as a Google embed pasted on top.

Step five. Update your content security policy. Google’s script loads from news.google.com and displays a small overlay that pulls from www.gstatic.com and fonts.gstatic.com. If your site enforces a strict CSP, you need those three hosts added to script-src, frame-src, and font-src.

Step six. Test with two accounts, one signed in and one in a private window, on both a desktop and a phone. The signed-in flow shows the “Add [publication] as a Preferred Source” confirmation. The signed-out flow prompts a Google sign-in. Both should return the reader to your page.

Step seven. Ship a deeplink fallback for email newsletters, social posts, and anywhere JavaScript will not run. The format is google.com/preferences/source with your domain as a query parameter. Google documents this as the deeplink option and it is still the only route for off-site placements.

What To Do After The Google Preferred Sources Button Is Live

Embedding the button is the easy half. The harder half is getting readers to click it. Here is what we are testing on the Elevarus site and on client accounts.

Ask on the pages that already convert. If a page has a high scroll depth and a decent email capture rate, it also has a decent chance at a preferred source opt-in. Add the button to those pages first. Skip the pages nobody finishes.

Pair it with your newsletter ask. The value proposition to the reader is the same. “You like this content. Here is one click to see more of it.” Two options at the same moment help the reader choose the format they prefer.

Reference it in your top-of-funnel content. If you rank for a “what is” or “how to” query that lands in Top Stories, the reader is already showing interest in your take. Mention the preferred source option in a short editorial note near the top of those posts.

Track badge appearances. Once you are getting selections, watch Search Console. You will not see a dedicated report yet, but you can monitor impression and CTR shifts on queries that already trigger Top Stories or AI Overviews. If the same query starts pulling higher CTR after your button goes up, the badge is doing work.

Watch for algorithm crossover. Preferred sources signals are personalized, but they can interact with broader ranking updates. Keep an eye on your reporting through the current August 2026 spam update recovery window. If you see volatility on the same queries where you have preferred-source badges appearing, the interaction is worth flagging in your weekly client note.

What The Google Preferred Sources Button Does Not Solve

Be clear-eyed about what this button is not. It is not a ranking factor for readers who did not opt in. It is not a workaround for a site that does not surface in Top Stories. It is not a substitute for the trust signals that get you into AI Overviews in the first place. Google has been explicit that eligibility tracks with whether your site already earns Top Stories placement.

Keep the mechanism straight, because the name misleads people. This is a reader-preference signal, not a broad ranking factor. As Search Engine Land puts it, readers star the publications they trust, and Google shows those readers more stories from the outlets they picked. Google’s own documentation says the lift applies to the users who selected you, not to everyone who searches. So a preferred pick widens your reach with people who already like you. It does not raise your rank for the audience that has never heard of you.

The button also does not fix the paid-search side of the same story. If your organic click share is shrinking because AI Overviews are pulling answers above the fold, the preferred source badge helps only where you were going to appear anyway. The contradictions AI Overviews are creating in paid search quality scores are a separate problem that needs a separate audit.

If you publish under multiple properties, remember the domain-level rule. A single article at yourbrand.com/blog/post is not eligible. The full yourbrand.com or news.yourbrand.com subdomain is. Plan your embed strategy accordingly. Every property you want to earn preferred source status needs its own placement plan.

Finally, do not confuse this with the Search Console platform properties workflow that lets you consolidate cross-platform reporting. That is a completely different lever, covered in our Search Console platform properties playbook. Both matter. Neither replaces the other.

The best AI search play in 2026 is a slow one. Earn Top Stories eligibility. Publish content readers actually want to see again. Ask them for one click that keeps you in their feed. Watch for the badge. If you want help sequencing this alongside your paid media and organic strategy, book a free consultation with our team. We are running this exact test across our own sites and can share what we see.

Let’s Grow!