Quick answer: Help readers choose your publication as a Google preferred source by checking domain eligibility and offering the supported button or a clear link to Google’s preferences flow. The reader makes the choice. Keep the invitation optional, explain its purpose and measure your own interaction data without treating a click as proof that a preference was saved.
Audience loyalty matters when readers encounter information through many interfaces. Preferred Sources gives publishers another way to help interested readers find their work in supported Google experiences. It is most useful as part of an existing relationship with an audience that already values the publication, rather than as a substitute for useful reporting or a dependable website.
Feature documentation checked on 21 October 2026. Implementation examples are explanatory and do not establish any particular site’s eligibility.
What does Google’s Preferred Sources feature do?
Google’s publisher documentation explains that readers can choose a publication as a preferred source. It describes more likely appearance in Top Stories for those readers and a preferred badge in supported AI Mode and AI Overviews experiences. Availability and eligibility conditions differ by surface, so review the current guidance for the experience you intend to support.
The preference concerns an individual reader’s choice. It is not an official certification of every claim the publication makes. Avoid describing the feature as a universal ranking boost, a purchaseable search advantage or a guarantee that every selected reader will see every new article.
Check the correct publication identity
Use the domain or subdomain identity that actually represents the publication. Google’s documentation distinguishes those from a subdirectory such as a blog folder. Confirm that the site appears in the source preferences tool and review the stated requirements for supported AI experiences before promoting the feature.
Then check the reader-facing brand. The site name, logo, About page and editorial contact should describe the same publication. A preference invitation is confusing when the button names one brand and the destination shows another. Our guide to expertise and trust provides a broader framework for making the organization and its work understandable.
Choose the simplest supported implementation
Google documents a standard JavaScript button, advanced customization and a deeplink option. Choose according to the website’s capabilities and maintenance needs. A publisher using a restrictive editor may find a clear text link easier to manage than an interactive component. A development team may prefer the supported standard button if it fits the existing layout.
Keep the implementation small. Assign an owner, record where it appears and retain a working version for comparison. Avoid several plugins injecting different preference buttons on the same article. The user should encounter one understandable invitation, not competing prompts that make it difficult to continue reading.
| Option | When it may fit | What to test |
|---|---|---|
| Standard button | The site can load the supported library | Rendering, language and return flow |
| Custom integration | A maintained interface needs a specific design | The supported behaviour and accessibility |
| Deeplink | The editor cannot support the interactive component | The intended publication and confirmation journey |
Place the invitation where it makes sense to the reader
A reader who has just completed a useful article has more context for the choice than someone who has only opened the homepage. Consider a modest invitation after the article, on an About page or within a relevant newsletter. Explain that the feature can help readers find more of the publication’s work in supported Google experiences.
Do not block the answer, cover a form or require the preference before someone can read. Avoid a prompt on every scroll movement. The invitation should support a voluntary relationship with the reader. Your existing newsletter and social links can remain separate options with their own clear purpose.
Use accurate, restrained button copy
Choose wording such as “Add this publication as a preferred source on Google.” A short explanation can say why the reader might want to do that. Avoid promises about ranking, guaranteed notifications or automatic access to every article. The text should match what the destination actually offers.
If the site has several unrelated products, make clear which publication the button concerns. Do not use a broad preference request to imply an endorsement of a commercial offer. Consistent branding and an honest description reduce confusion when the reader leaves the current page to make a choice.
Implement through the appropriate website layer
On WordPress, have the person maintaining the theme or supported integration add the component through an appropriate site-level route. Pasting executable code into ordinary article content can be stripped, duplicated or altered by the editor. Keep the instructions for future maintainers with the integration’s configuration rather than scattering them through published posts.
Use the current official implementation examples for the exact script and markup. Do not rely on an old screenshot of a button’s code. Our WordPress SEO guide covers the surrounding publishing setup, but the feature’s own documentation should remain authoritative for its integration details.
Test the complete reader journey
Open a representative page on desktop and mobile. Confirm that the invitation is visible, labelled clearly and reachable by keyboard where applicable. Follow the action and check that the intended publication appears. Then return to the original page and confirm that reading position and page usability remain reasonable.
Inspect the experience in the reader languages you actually support. A hardcoded label can conflict with an otherwise localized page. Also test a visitor who dismisses the invitation or cannot complete the preference flow. A good integration should let that visitor continue using the article without a broken overlay or repeated demand.
Measure what your site can observe
You may be able to record that a reader clicked your invitation, depending on the implementation and analytics setup. Name that event accurately. A click is not necessarily a saved preference, and a saved preference is not necessarily an additional search impression. Do not invent a conversion total that the integration does not expose.
Use a simple reporting question, such as whether readers of a particular section engage with the invitation. Compare similar periods and note placement changes. Keep this analysis separate from general organic traffic. If several campaigns run together, acknowledge that their effects cannot be isolated from a single site-wide trend.
Keep editorial quality at the centre of audience retention
A preference request works best when readers know what the publication reliably offers. Maintain a clear subject, show who is responsible for important claims, cite useful sources and correct material errors. Our E-E-A-T explanation discusses these reader-facing trust signals without treating them as a substitute for actual expertise.
Publish at a pace the team can maintain. A new badge does not justify expanding into unrelated topics or repeatedly publishing the same answer under slightly different titles. A reader who chooses the publication should continue finding work that matches the reason they made that choice.
Connect the feature to a broader audience plan
Use Preferred Sources alongside channels with distinct roles. A newsletter can deliver an agreed briefing, a social account can support discussion, and the website can remain the maintained reference. Explain each option separately so readers can choose how much contact they want. Avoid treating one audience mechanism as proof that the others are unnecessary.
Our social media planning guide and email strategy guide can help align those channels. Reuse the core editorial subject while adapting the invitation and format to the channel. A newsletter link should lead to the same publication identity as the website button.
Maintain the integration after a redesign
If you test different placements, change one meaningful element at a time and keep the reader task intact. Moving a small invitation from the sidebar to the end of an article is easier to interpret than simultaneously changing its copy, colour, timing and surrounding template. Record the dates and pages involved so the results can be compared fairly.
Ask for qualitative feedback as well. A reader should understand that the invitation concerns finding the publication on Google, rather than purchasing a subscription or joining an email list. If people misunderstand the purpose, improve the wording before pursuing a higher click count. More clicks caused by confusion do not establish a better audience experience.
Keep related prompts visually distinct. Newsletter signup, browser notifications and source preferences create different relationships. A clear page lets readers make each choice independently and continue reading regardless of which option they select.
Add the preference journey to the release checklist when changing navigation, article templates, consent settings or JavaScript loading. Confirm that the control still renders and that the layout remains usable on a small screen. A component can disappear silently if a template is replaced or a script-loading rule changes.
Review the current official documentation periodically and remove obsolete implementations rather than stacking a new one on top. Keep a small record of the chosen method, locations and owner. That makes the feature easier to maintain and keeps the invitation consistent with the reader’s experience.
Common questions about Google Preferred Sources
Does the publisher choose the preference for the reader?
No. The reader makes the selection through the supported Google flow. A website invitation should not imply that the choice has already been made.
Can the feature guarantee higher rankings for everyone?
No. Describe the documented personalized feature accurately. Do not turn it into a claim about universal search placement.
Can I count every button click as a saved preference?
No. Report the event you can actually observe. Do not infer completion unless the supported implementation provides reliable evidence.
Does a blog subdirectory qualify as a separate source identity?
Google’s current guide specifies domain and subdomain eligibility. Check the source preferences tool and documentation for the publication you intend to promote.
Join the discussion