Choose the Right Preferred Sources Flow for Your Publication

Use Google’s JavaScript button on article pages when your site can load it. Use the deeplink in newsletters, social posts, or a CMS that cannot run the embed. Both help readers select your publication as a Preferred Source, but the button provides a documented return to the originating page; the deeplink does not provide the same flow.

Choose your placement and publication status to find the appropriate integration.

Google recommends the standard JavaScript implementation because it provides an automatically localized button and returns readers to where they left off. A graphic styled as a button but attached to a deeplink still uses the deeplink flow—not the interactive embed.

The Button Provides a Return-to-Article Flow

Decision Point	JavaScript Button	Deeplink
Selection flow	Publication-specific add flow	Preferences tool targeting your publication
Return to article	Documented automatic return	No automatic return in SEJ’s mobile test
Integration	Google library and container	Text link or linked image
Localization	Automatic; override available	Publisher-written text or artwork
Best fit	Script-enabled website pages	Email, social, script-restricted pages

In Search Engine Journal’s reported mobile test, the embed opened a confirmation page with the publication already identified. The reader tapped Add and returned to the article. The deeplink opened the preferences screen with the publication search filled in, but the reader still had to select the publication’s checkbox and did not automatically return.

That is a reported mobile observation, not a guarantee of identical screens on every device or account. Google independently documents the embed’s return-to-page behavior in its product announcement.

Those sources support choosing the embed for a smoother on-site flow. Neither establishes a conversion-rate lift, so there is no supported percentage improvement to use in a rollout forecast.

Confirm the Publication Target Before Deployment

Before changing templates, search for your publication in Google’s source preferences tool, linked from the publisher documentation. Google’s implementation guidance applies if your site appears there.

Only domain-level and subdomain-level sites are eligible in that tool.

Publication Address	Separate Target Allowed
example.com	Yes, if listed
news.example.com	Yes, if listed
example.com/blog	No

If a publication lives in a subdirectory, do not build a campaign around selecting that section independently. If it lives on a subdomain, check that specific host rather than treating the root domain as interchangeable. Adding a button is not a remedy for a missing listing.

For a network of publications, this check belongs before template deployment: a working button pointed at the wrong host is not a successful integration.

Use the Standard Button on Script-Enabled Pages

Google’s standard setup loads its preferred-sources library and places a container marked with google-add-preferred-source-btn where the button should appear. The library renders the interface. Use the official implementation instructions for the current embed details.

The standard button defaults to a light theme and uses the reader’s browser language. Its data-theme setting supports light or dark styling; data-lang can override the language. Leave automatic localization in place unless the page has a specific language requirement.

A custom design does not require abandoning the interactive flow. Google also documents an advanced JavaScript integration that binds the same flow to your own controls. Choose that only when the standard button cannot meet the interface requirement: it adds implementation work without changing the underlying reader task.

The implementation choice is therefore not simply “Google artwork versus our artwork.” A custom JavaScript control can retain the interactive flow, while an image linked to Google’s preferences page remains a deeplink.

Use the Deeplink Where the Embed Cannot Run

The deeplink targets the /preferences/source path on Google’s website, with your publication’s domain in the q query parameter. Google supplies the exact format and examples in its deeplink instructions.

Use descriptive link text such as “Add Example Publication as a Preferred Source.” A linked graphic is another supported presentation. Neither needs the publisher-side JavaScript library, which makes the deeplink suitable for newsletters and social distribution. It does not mean Google’s destination works without JavaScript.

A publisher can use both implementations: the standard button on website pages and the deeplink in distribution channels. Keep their reporting separate because they start different reader flows.

Verify the Target, Selection Steps, and Return

A release check should cover both a desktop browser and the mobile environment most common among your readers:

1. Confirm that the intended publication appears in the preferences tool.
2. For the embed, check rendering, theme, localization, and the publication shown after clicking.
3. Complete the add flow and verify the return to the originating article.
4. For the deeplink, confirm the targeted publication and the remaining selection steps.
5. Check that one activation produces one analytics event, not duplicate events from overlapping listeners.

Do not treat the reported mobile test as a substitute for testing your own placement. The target, rendered control, and return destination are all part of the release check.

Measure Clicks Without Claiming Saved Preferences

Call a click-based event something like preferred_source_button_click, not preferred_source_added, and record whether it came from the embed or deeplink. SEJ explicitly notes that its button-click tracking does not confirm completion inside Google.

A click is evidence of an attempt to start the flow, not proof that the flow loaded or a preference was saved. Returning to the article alone is not proof of a saved preference either.

If comparing placements or implementations, define exposure and click-through consistently using a content experiment brief. Report the result as a change in clicks unless you have separate, verified completion evidence.

Preferred Sources is personalization for readers who choose you, not a promised sitewide ranking boost. Google says selection makes your content more likely to appear in their Top Stories. It can also highlight your content with a preferred badge in AI Mode and AI Overviews where those features are available; Google’s documentation says that eligibility for this display requires inclusion in Search generative AI features in Search Console.

Choose the button for the documented on-site return flow. Choose the deeplink to reach readers where the embed cannot run. Evaluate deployment quality and clicks separately from saved preferences and search visibility.