Google Preferred Sources now has a site button: what creator publishers should build first

The August 20 update: a direct selection path from your own site

Google Search Central updated its Preferred Sources documentation on August 20, 2026 with a new custom interactive button for publishers. The recommended implementation loads a Google library and renders a localized button on the publisher's page. Google also documents an advanced custom implementation and a deeplink that can be used in a website, social post, newsletter or promotion.

When a signed-in reader selects an eligible site, that publication is more likely to appear for that reader in Top Stories and can be highlighted with a preferred badge in AI Mode and AI Overviews where those features are available. Google says the Top Stories preference is global across supported Google Search languages. The feature is personal to the reader; it is not a global boost applied to every searcher.

First decide whether you are a publisher, not just a profile

The feature operates at the domain or subdomain level. Google says a root domain or a subdomain can be eligible, while a subdirectory such as example.com/blog cannot be selected on its own. The site must also appear in Google's source preferences tool. Google Search Help notes that sources which are not updated regularly may not be available.

This creates a useful boundary for creators. A social profile, link-in-bio page or occasional campaign landing page is not automatically an owned publication. The strongest candidate is a stable site that repeatedly publishes timely, attributable work: industry notes, original interviews, field reports, product tests, event coverage or analysis connected to primary evidence. The creator's name helps; the publishing system makes the source durable.

Run an eligibility and trust audit before adding a button

Start in the source preferences tool and search for the exact domain. If it is not present, do not add a broken or misleading prompt. Instead, audit the publication fundamentals: crawlable article pages, one canonical URL per story, visible author and dates, a clear about/editorial page, source links, descriptive headlines, an archive or hub, a feed or sitemap and regular publication. These practices do not guarantee eligibility, but they make the site understandable to readers and search systems.

Next, review the content promise. A creator who publishes only repackaged platform posts gives readers little reason to choose the website as a source. The owned edition should add something the social clip cannot: full methodology, source documents, corrections, transcripts, downloadable checklists or a dated decision log. Preferred-source selection is most credible when the reader already knows what unique value will return.

• Exact domain appears in Google's source preferences tool.
• Articles are public, crawlable and consistently attributed.
• Publication and update dates are visible and honest.
• Primary evidence and corrections can be followed from the page.
• The archive demonstrates a stable topic lane and current cadence.

Choose the lowest-friction implementation that your site can maintain

Google's standard button is the sensible default for most creators because it is localized automatically and returns the reader to the page after the selection flow. A dark or light theme can match the site. A custom implementation makes sense only when a developer can preserve the same user flow and maintain the integration. A deeplink is the fallback for a CMS that cannot run the script, and it is also useful in email or social promotion.

Do not imitate the button with a graphic that implies the reader has already selected the site. The action should be explicit and initiated by the user. Test the exact production domain, language, mobile and desktop return path. If the site uses several subdomains, decide which one carries the publication; splitting the prompt across domains can fragment reader choice and editorial identity.

Place the prompt after value, not before trust

A full-screen request before a reader sees the article is a poor trade. The best moment is after the reader has received a complete piece of value: below the takeaways, near the end of an article, on the publication hub or inside a newsletter confirmation page. Explain the benefit in plain language, such as seeing more of this publication in relevant Google experiences, without promising rankings or guaranteed visibility.

Use frequency limits. A returning reader who has dismissed the prompt should not see it on every page. Keep the preferred-source action separate from newsletter consent, account creation and creator-network registration; each is a different user choice. The goal is a voluntary return path, not a bundle of dark-pattern permissions.

Measure the publishing loop, not the badge

Google does not present the button as a ranking guarantee, and a preferred badge is not evidence that a page was indexed or that a reader clicked. Creators should measure what they control: button visibility, voluntary click-through to the Google flow, return visits to the owned site, article engagement, newsletter sign-ups and the share of new stories that meet the publication's source and freshness standard.

Annotate the implementation date in analytics and compare cohorts carefully. Search demand, news cycles and publication volume can change at the same time. Do not attribute every traffic movement to Preferred Sources. A useful review asks whether the site is publishing more consistently, whether readers return to the same topic lane and whether creator opportunities reference the owned work as evidence of expertise.

A 14-day creator publishing sprint

Days one to three are for qualification: check the exact domain, audit the archive and choose one editorial lane. Days four to seven are for evidence: publish or materially update two source-led pieces with visible authorship, dates and links. Days eight to ten are for infrastructure: verify the hub, feed, sitemap, mobile layout and correction path. Days eleven to fourteen are for the audience loop: add the standard button or deeplink, test the full selection-and-return experience and introduce one restrained call to action in the newsletter or article footer.

KOLMKT's operating view is that the new button matters most for creators who already act like reliable publishers. A platform audience can discover the creator; an owned publication can preserve the creator's evidence, expertise and commercial readiness. Preferred Sources adds one reader-controlled return route. The durable advantage still comes from work worth preferring.

• Verify domain eligibility before implementation.
• Publish original, source-led work on a predictable cadence.
• Use the standard button unless customization has a real maintenance owner.
• Place the request after value and limit repeat exposure.
• Measure return behavior and publishing quality without claiming ranking gains.