Should publishers add Google’s new Preferred Sources button?

By Greg Nowak. Last updated 2026-08-24.

For many publishers, the answer is yes. Add it as a measured audience experiment, though, rather than expecting it to repair search traffic on its own.

Google’s embeddable Preferred Sources button lets an existing reader signal that they want to see more from a publication. After selecting a site, that reader is more likely to encounter its fresh, relevant content in Top Stories. Preferred links may also be highlighted in AI Overviews and AI Mode.

That is more useful than a conventional follow button. A relationship formed on the publisher’s website can influence what the same reader later sees inside Google Search. As AI-generated answers change the route from a search to original reporting, publishers have a good reason to test that connection. They also need to be clear about its limits.

What the preference actually changes

Preferred Sources is a personalisation signal. It does not give the publication a universal ranking boost. Google’s reader documentation says preferred sites appear more often in Top Stories when they have published fresh content relevant to the search. Its publisher guide says selected content is more likely to appear and may carry a “Preferred” badge.

Quality, relevance and freshness still count. The reader also has to use a Google surface where the feature applies. Selecting a site will not make an unrelated article fit a query, compensate for a publication that rarely updates or guarantee a prominent result.

The realistic proposition is simple: loyal readers get a supported way to make relevant work from your publication easier to spot in future Google experiences. That is useful, but it is a different promise from recovering lost search traffic.

Google’s click figure needs context

Google reports that people are twice as likely to click through to a site after marking it as a Preferred Source. With preferences now extending beyond Top Stories to AI Overviews and AI Mode, that result makes the feature well worth investigating.

It does not mean a publisher’s total Google traffic will double. The figure concerns the click behaviour of people who selected a source, not every searcher, query or article. The eventual effect depends on how many suitable readers notice the invitation, complete Google’s selection flow and later see relevant content on a supported search surface.

Confirm eligibility before working on the design

Google advises publishers to check that their site appears in the source preferences tool before promoting the feature. Eligibility works at domain or subdomain level. Readers may be able to select example.com or news.example.com, for instance, but they cannot independently select a directory such as example.com/news.

Google’s reader help also says sources that are not updated regularly may be unavailable. Start by checking the precise hostname your readers know. Then confirm that a domain-level preference fits the way your publication, brands and sections are organised.

The standard button is the sensible starting point

Google recommends its standard JavaScript implementation. A library is loaded and a button container is added to the page. The component offers light and dark themes, can follow the reader’s browser language and supports an explicit language override. Crucially, the reader completes the Google interaction and returns to the page they were viewing.

On Drupal or WordPress, adding the code is unlikely to consume much of the project. The decisions around it will. The script should load once, the component needs a reliable home in templates or blocks, and its position must make sense alongside article content, account journeys and subscription prompts.

The custom JavaScript SDK becomes relevant when the Google-styled component genuinely conflicts with an established interface, or when the prompt belongs at a particular point in an application journey. Google documents both ES module and conventional script integrations. More control also means more responsibility for accessibility, responsive behaviour and testing after future site changes.

Where JavaScript cannot be added, use the deeplink. Google specifically presents it as an option for CMS-constrained websites and promotions in email, social media and other channels. On an ordinary article page, the embedded experience is usually stronger because it gives the reader a more coherent route back.

Ask at the moment the choice makes sense

Choosing a Preferred Source is a lasting decision, so raw exposure is a poor placement strategy. A reader who has not yet read the article has little reason to act. Someone who reaches the end, considers joining the newsletter or returns regularly has already seen what the publication offers.

A restrained placement on eligible editorial templates is a sound first test. Launching prompts in the header, article body, footer and an overlay at the same time creates several problems: it competes with registrations, subscriptions and advertising, and it becomes much harder to learn which context produced a worthwhile interaction.

Treat Google’s script like any production dependency

Both standard and custom implementations load JavaScript from Google. Review the integration as you would any third-party production dependency: check content security rules, consent requirements, page performance, failure behaviour, and compatibility with caching and optimisation layers.

Google’s example loads the script asynchronously, which reduces the risk of blocking page rendering. Testing is still necessary. The article should remain usable when the library is delayed or unavailable, and the component should not cause a noticeable layout shift when it appears.

Multilingual publishers should test the automatic localisation as well. Browser language and publication language do not always match, so an explicit setting may produce a more consistent editorial experience.

Measure more than the first click

A button click records intent. It does not prove that the reader finished selecting the source in Google’s managed flow. Keep separate measures for button impressions, flow starts or outbound clicks, observable returns to the article, and the engagement that follows.

Placement-level results are more informative than one blended click-through rate. Depending on the site, useful comparisons could include new and returning readers, article category, device, language and logged-in status. Avoid false precision: any search benefit may arrive days later or on another device when the reader is signed into the same Google Account.

Record a baseline for relevant Google referrals before launch and agree on the test period. Then examine whether people use the prompt, whether they return successfully and whether it suppresses more valuable actions such as registration or subscription. Referral changes are worth monitoring, but rankings, search demand and publishing volume move too, so the button should not receive automatic credit for every increase.

Who should put it on the roadmap?

Publishers with an eligible domain, a regular publishing schedule and a recognisable returning audience have enough reason to run a controlled test. Use the standard button by default. Move to a custom flow when closer design-system integration will materially improve the experience, and keep the deeplink for constrained websites and off-site promotion.

The feature cannot replace distinctive reporting, sound technical search work or direct audience development. It is a modest piece of infrastructure that carries a reader’s explicit preference into Google’s changing search environment. With sensible placement and honest measurement, it can earn its place on the publisher roadmap.

Related on GrN.dk

• Search Console Can See TikTok Now. Your Reporting Has to Catch Up
• Your Website Can Answer Questions Now. Should It?
• Agentic AI: What It Is, How It Works, and When to Use It

Need help with this kind of work?

Plan your Preferred Sources test Get in touch with Greg.

Sources

• Guide to Preferred Sources for web publishers
• Preferred Sources expands globally
• Preferred Sources enters Google’s AI experiences
• Preferred Sources user documentation
• Google gives publishers a response to AI-driven traffic losses