RankAssurance
Owner Tests · AI citations · Updated 7 September 2026

The Preferred-Source Test.

A User Pin Is Not a Ranking Package You Buy

The Short Answer

The Preferred-Source Test separates Google's user-side pin — a reader choosing to see more of a publisher — from any pitch selling the feature as a placement you can buy.

People can tell Search which publishers they want highlighted in Top Stories, AI Overviews, and AI Mode. That is a pin. It is not a backlink, a citation buy, or a Search Console switch you purchase.

The question this article answers

Official publisher documentation: a domain or subdomain can be eligible; a subdirectory is not. Users who selected you can see a badge on those sources in Top Stories and in AI experiences. Publishers may add a documented button so readers can pin the site. None of that is a paid ranking credit.

Google has published that people who use Preferred Sources are more likely to click those sources. That is a published product note about users who already chose you. It is not a reason to buy a “Preferred Sources campaign.” If an invoice names the feature as a deliverable — something no vendor can control inside other people’s accounts — that pitch belongs to the SEO Pitch Test and the Vendor Claim Test.

Did a person choose this source — or did someone sell the pin as a ranking product?
Two columns contrast a user setting with a ranking package. Left, a pin: preferred source The Greenfield Ledger, a star that lives in the searcher's own settings, badged for that person. Right, an agency invoice selling “Buy Preferred Sources” to influence rankings and visibility. A user setting is not a ranking package.
Figure 1. Official object: a user setting. Not a ranking package.
Three parallel panels naming what makes an AI answer stable: consistency — the same answer holds across similar queries and days; usefulness — the page truly answers the question asked; verification — independent sources confirm the claim. Not a named ranking slot; no one can buy a citation.
Figure 2. Preferred Source is the fourth branch. Vendor Claim if they sold it as a slot.

Pitch Anatomy: The Offer Against the Document

The lines below are a composite of the pitch pattern, scored against Google’s own publisher document. Every row is the same failure: a user-side setting resold as a vendor-side deliverable.

The pitch line · What the document says
“We will get you into Preferred Sources”
There is no placement to get. A reader pins a source inside their own account.
“Guaranteed AI Overview visibility”
The badge and the published click note apply only to readers who pinned you. No documented effect on anyone else’s results.
“We will enroll your /blog folder”
Not eligible. A domain or subdomain can be eligible; a subdirectory cannot.
“Monthly Preferred Sources report”
No owner-side report exists. No instrument — Google’s or anyone’s — reports pin counts to the publisher.

What a Reader Actually Does

Google’s user help documents the whole flow, and it is three of the reader’s own clicks: search a topic, open the preferred-sources control beside the news results, select the sites to see more of. From then on that reader sees more of those sources — badged — in Top Stories and in AI experiences. Nothing in the flow has a vendor in it.

Eligibility in one breath: domain or subdomain — yes; subdirectory — no; the badge shows only to readers who chose you; and no count of who did is reported to anyone.

The one documented thing a publisher can do: place the official link inviting readers to pin the site. An invitation to people who already trust you — that is the entire owner-side lever the document grants.

What is official

The shared official model — same index, foundational SEO, the ignore-list for special AI files — is kept once, dated, at the Citation-Surface Test. What matters on this page is narrower: Preferred Sources is documented as a user-side setting that changes what the person who pinned you sees — and changes nothing for anyone else. Everything a pitch adds beyond that sentence is the pitch’s own invention.

Calculator

The Preferred-Source Test Calculator

Do not do tonight: sign anything with “Preferred Sources placement” as a line item. A setting that lives in readers’ own accounts cannot be delivered by a vendor — the rest of the invoice deserves the same reading.

Official-path next step

  1. Read the publisher document yourself — it is linked below and one page long. Every pitch claim should survive it.
  2. Check eligibility: is the property a domain or subdomain? A subdirectory ends the conversation.
  3. If you want pins, add the documented invitation for readers — the only owner-side lever that exists.
  4. If someone sold the feature as a slot, run the invoice through the SEO Pitch Test and the Vendor Claim Test.
The sentence to keep. Did a person choose this source — or did someone sell the pin as a ranking product?

Questions

Can we buy Preferred Sources placements?

No. It is a user setting. You can invite readers to pin you with the documented control.

Does pinning replace citations?

No. The Citation-Surface Test still applies for everyone who did not pin you — and that un-pinned public is what the AI Answer report measures: what engines say to a person with no preferences set.

How would we know how many people pinned us?

You would not. No owner-side count exists, on Google’s side or anyone’s. A vendor report that claims to measure it is measuring something else.

Sources