Google Preferred Sources with a Privacy-Conscious Double-Click Flow

Diesen Artikel auf Deutsch lesen

Google Preferred Sources lets readers select a website as a preferred source in Google Search. The official integration is simple, but an automatically loaded third-party script is not always the right first step. This article shows a controlled double-click flow: explain what happens first, then load Google's script only after the visitor explicitly confirms.

What are Google Preferred Sources?

Google lets people choose websites as preferred sources. Google says that content from selected sources can be highlighted in relevant Top Stories, and that a preferred badge can appear in AI Mode and AI Overviews. This is a user-controlled signal, not a promise of better rankings.

Only domains and subdomains can be selected. A subdirectory such as example.com/blog cannot be selected separately. See Google's official guide for web publishers for the current implementation options.

The simple direct link

The simplest implementation is a link to Google's source preferences:

<a href="https://www.google.com/preferences/source?q=example.com"
   target="_blank" rel="nofollow noopener">
    Add as a preferred source
</a>

This is technically valid and may be all a website needs. The visitor leaves the site immediately, though, and receives no site-specific explanation before the Google connection starts.

Why two clicks?

Our approach uses an initial click to open a site-owned information dialog. It explains:

• what the next step will do,
• that a connection to Google will be established,
• that technical data and browser information may be transmitted to Google,
• where to find the privacy policy and Google's own settings.

Only after the visitor clicks “I agree – continue to Google” do we load Google's script and start the flow. Without that second click, the Google connection is not started.

The technical implementation

Google documents both a standard button and a programmatic integration. The script can be loaded with preferred-sources-control="manual" and the flow can then be started with preferredSource.addPreferredSource(). That lets the site's own interface control when the call happens.

<script async preferred-sources-control="manual"
        src="https://news.google.com/swg/js/v1/publisher.js"></script>

<button type="button" id="follow-source">Follow</button>

<script>
    // Run this only after the site's information dialog.
    preferredSource.addPreferredSource();
</script>

For a genuine double-click flow, the script element itself must also be created only after confirmation. Putting it in the regular page head would load it before the dialog and defeat the purpose of the design.

What we can measure – and what we cannot

Google does not provide website owners with a dashboard showing how many people selected their site as a preferred source. We can therefore measure only our own part of the flow:

• the page where the flow was started,
• the time of the explicit confirmation,
• the start of the hand-off to Google.

We cannot tell whether Google actually stored the selection. This is a confirmed hand-off metric, not a Google success metric.

A careful note on GDPR and consent

A double-click flow can make the information and order of events clearer. It is not an automatic privacy certificate, however. Whether a specific integration is lawful depends on the website, its purpose, the Google feature used and the operator's privacy notice.

In Germany, Section 25 TDDDG generally requires clear and comprehensive information and consent for storing or accessing information on an end user's device, unless an exception applies. GDPR consent must also be freely given, specific and demonstrable. See Section 25 TDDDG and the GDPR on EUR-Lex.

That is why we should not advertise this as “guaranteed GDPR compliance”. A more accurate description is: a privacy-conscious technical integration with an information step and explicit confirmation. The website operator remains responsible for the legal assessment of the concrete site.

No ranking promise

Preferred Sources do not replace useful content, freshness, technical quality or ordinary search optimisation. Google may highlight selected sources in certain search surfaces, but that does not guarantee better positions, more visitors or higher revenue.

Conclusion

A direct Google link is the simplest option. A double-click flow is useful when site owners want to explain an external script first, let visitors make a conscious decision and count their own confirmed hand-offs.

It does not reveal what Google stored internally. It does make the site's own part of the process transparent – without storing an IP address and without pretending to be Google Analytics for Preferred Sources.

← Back to Projects