Google Preferred Sources: What the New Publisher Button Actually Does

A reader finishes a useful article, bookmarks the site, and plans to come back. Then life gets busy.

The bookmark disappears into a folder, and the newsletter goes unopened. The next Google search sends that reader somewhere else.

Google’s Preferred Sources feature lets readers signal which sites they want to see more often. On August 20, Google released an interactive publisher button.

The button can add a site as a reader’s preferred source. It then returns that person to the page they were reading.

Google says selected sources are more likely to appear for that reader in Top Stories. A preferred badge can also highlight them in Top Stories, AI Overviews, and AI Mode.

That sounds like a new SEO shortcut to more traffic. It isn’t. The button does not:

• Raise a site’s rankings for everyone
• Force content into an AI answer
• Turn a business blog into a news publication

The button is a reader-choice feature. Its value depends on whether people already care enough about the site to choose it.

The domain must also be eligible. The publisher has to keep producing material worth finding again.

Reporting note: This article reflects Google’s public documentation available on August 31, 2026. Availability, interface details, and documentation can change. Any examples below are hypothetical and are not client results, forecasts, or performance promises.

Key takeaways

• Preferred Sources personalizes what a reader may see. It is not a universal ranking boost.
• Google supports a standard JavaScript button or a custom JavaScript integration. A direct link to the source-preferences tool also works.
• Only eligible domains and subdomains can be selected. A folder such as example.com/blog cannot be treated as a separate source.
• A button click shows interest. It doesn’t prove the person completed the preference flow or later clicked a Google result.
• Earn the request by placing the button after useful content. Measure it as an audience signal, not a guaranteed search tactic.

What is Google Preferred Sources?

Preferred Sources is a Google Search personalization setting. A person chooses publications or websites they want to see more often.

Suppose Google has fresh, relevant content from one of those sources. That content may then get greater visibility for that person in supported search features.

The phrase “for that person” matters. Say one reader selects a local newspaper. Another reader who never selected it does not automatically get the same treatment.

The selection follows one person’s preference. It is not a sitewide authority score that every searcher shares.

Google first framed the feature around Top Stories. Its current publisher documentation adds AI Mode and AI Overviews, where those features are available. There, preferred sources can also appear with a preferred badge.

The documentation does not say that a selection guarantees inclusion in any result.

What changed with the new publisher button?

Readers could already manage preferred sources through Google. The August update changed the publisher side of the experience.

A website can now place an interactive Google button directly on a page. The reader starts the preference flow there. Once they finish, Google returns them to the original page.

That return path removes a clumsy step. A publisher no longer has to send someone away with no obvious route back.

Google also documents these options:

• Light and dark themes
• Automatic language selection
• A language override
• Programmatic controls for a custom interface

Google reported in April that readers were twice as likely to click through. The finding applies to sites they had marked as a Preferred Source. Treat that as Google’s aggregate observation, not an expected lift for one site.

People who choose a source already have a stronger relationship with it. So the number does not prove the button caused every additional click.

Where can a preferred source appear?

The clearest use remains Top Stories. Say a selected source has current, relevant reporting for a search. Google says its content is more likely to appear there, possibly with a preferred badge.

This makes the feature most natural for publishers with a steady editorial cadence.

Google’s documentation also includes AI Mode and AI Overviews. Google may highlight a selected source with a preferred badge in those experiences.

Read that language carefully. Highlighted does not mean quoted, ranked first, or shown for every related question.

The feature is available globally for Top Stories in languages Google Search supports. AI appearances depend on where AI Mode and AI Overviews are available. Check the live documentation instead of assuming every reader sees the same surfaces.

What the feature does not do

Preferred Sources is easy to oversell because it sits near ranking, news, and AI features. A publisher can describe the setting without inventing claims Google has not made.

• It does not make a site a Google-approved publication.
• It does not raise rankings for people who did not select the source.
• It does not guarantee a Top Stories, AI Overview, or AI Mode appearance.
• It does not replace crawling, indexing, clear authorship, accurate reporting, or ordinary search work.
• It does not prove a button click became a saved preference, visit, lead, or sale.

Avoid labels such as “Boost our Google ranking” or “Make Google recommend us.” Those phrases misstate the feature.

Clear copy works better, such as “Add Ardoz Digital as a preferred source on Google.” That label tells readers what the control does without promising a result.

Check eligibility before adding anything

Start with Google’s source-preferences tool and search for the site. Google tells publishers to confirm that the site appears there before promoting the feature. If the tool doesn’t list the domain, a polished button only creates confusion.

Eligibility works at the domain or subdomain level. Google’s example allows example.com and code.example.com as separate choices, but not example.com/blog.

So a company cannot ask readers to prefer only its blog folder. The choice covers the main domain as a whole.

For a business publication, that distinction affects the wording. The source is the company’s domain, even if the button appears beneath an article.

Before adding it sitewide, check these details:

• The domain name
• The favicon
• The publisher identity
• The editorial pages

Together, they should give readers a consistent picture of who they are choosing.

Three ways to add the button

Google documents three implementation paths. The right one depends on your publishing system and design requirements. It also depends on how much code the team can maintain.

The standard option is only a small integration. Google tells publishers to load its publisher library in the page head. Then they place an element with the preferred-source button attribute where the control should render.

The default language follows the reader’s browser. Publishers can pick a light or dark theme.

The custom option gives a development team control over the visible trigger. Google’s end-user flow stays the same.

That flexibility helps when the standard button clashes with a design system. But the custom label still needs to describe the action honestly.

The direct link is the low-code fallback. It can live in an article footer, newsletter, or social post.

It sends the reader to Google to confirm the source. Because it leaves the current page, the surrounding copy should set that expectation.

Where should the button appear?

Ask after the site has earned the request. A giant prompt before the first paragraph asks for a relationship before offering any value. The end of a strong article is usually a better moment.

• Place it after the article’s main answer, not in front of it.
• Use one clear placement before repeating the control elsewhere on the page.
• Explain that the setting affects the reader’s Google experience, not the website account.
• Keep the button separate from newsletter consent, cookie choices, and form submissions.
• Test the return path on mobile, tablet, and desktop before publishing it broadly.

A short line is enough: “Want more of our reporting in Google? Add this site as a preferred source.”

Don’t hide the action inside a generic button such as “Continue.” Never pair it with claims about better rankings.

How should you measure it?

The measurement plan should match the feature’s limits. Google’s public publisher guide explains implementation and availability. It offers no clean report from button exposure to saved preference to later search click.

Name the analytics event plainly, such as preferred_source_button_click. Record the page, placement, device category, and date.

Do not name it preferred_source_added unless the implementation can verify that outcome. A click and a completed preference are different events.

Then review the wider picture. Google Search Console can show page and query performance. The Generative AI report can show qualifying AI impressions for properties with access.

Neither report identifies the readers who selected the site. Use the numbers as separate clues and resist combining them into a made-up attribution path.

Some publishers also post on YouTube or social platforms. For them, Search Console platform properties answer a different question. They show how supported off-site content performs in Google Search.

Keep Preferred Sources, website performance, and platform-property data distinct in reporting.

A hypothetical publisher example

Imagine a regional business publication testing the standard button for 30 days. The following figures are invented to show the analysis. They are not benchmarks.

The newsletter page produced fewer clicks but a higher start rate. That makes sense because those visitors already chose a closer relationship with the publication.

Next, keep both placements running long enough to see whether the pattern holds. Don’t claim that the button increased Google traffic by 3.5 percent.

Should a service business add it?

Maybe, but the case is weaker for a site that publishes occasionally. That is especially true if it relies almost entirely on evergreen service pages.

Preferred Sources centers on reader choice and recurring editorial interest. If you post twice a year, the button shouldn’t be a major call to action.

A stronger candidate publishes material that readers actively follow. Think timely research, industry analysis, original data, local reporting, or recurring commentary.

Even then, the domain must appear in Google’s source-preferences tool. Eligibility comes before design work.

For many service businesses, the higher-priority work is simpler. First, publish clear answers. Then cover the other basics:

• Connect articles to relevant services
• Maintain credible authorship
• Keep facts current
• Make the site easy to use

Preferred Sources can support that work. It cannot replace it.

A practical rollout checklist

1. Search for the domain in Google’s source-preferences tool.
2. Confirm whether the domain or a specific subdomain is the correct source identity.
3. Choose the standard button, custom JavaScript flow, or direct link.
4. Write a label that describes the action without making a ranking claim.
5. Place the first test after content that gives the reader real value.
6. Confirm the light or dark version has sufficient contrast in the chosen location.
7. Test the full flow and return path on mobile, tablet, and desktop.
8. Track button impressions and clicks with honest event names.
9. Keep preference metrics separate from Search Console clicks and business conversions.
10. Review the placement after a meaningful sample instead of judging it after a few days.

The technical work is small. The judgment lies in two questions.

Is the audience relationship strong enough to justify the ask? Will the reporting stay honest after the button goes live?

Use the button to support a real audience

Preferred Sources is useful because it acknowledges something search reporting often misses. Some readers choose a publication, not only a topic. The new button gives those readers a cleaner way to express that choice inside Google.

But the order still matters:

1. Publish work people want to see again.
2. Build a recognizable source.
3. Ask for the preference in plain language.
4. Measure the response without turning a reader choice into a ranking promise.

Not sure whether the button fits, where it should live, or how to measure it? Ardoz Digital can review the editorial path and build a practical test.

No placement, badge, ranking, traffic level, lead volume, or revenue outcome can be guaranteed. Ardoz Digital is not affiliated with or endorsed by Google.

We mention Google, Google Search, and Top Stories only to identify the products discussed. The same applies to AI Overviews, AI Mode, and Preferred Sources.