Skip to content
regensbot
DEV-PRF-03May3 of 4 in PRF

Load per-session-billed third-party tools only after a user interaction

Level
May

Optional: worth doing where it fits.

Documentation

Said at Search Central Live

Said or shown at the event and not in Google's documentation: read it as said at Search Central Live, not as documented policy.

Covered

Automatic

Decided from one URL.

Why it matters

Said at Search Central Live by a community speaker: third-party systems billed per session (chat, personalisation, testing, session replay) also run when bots render pages and can cost a high-traffic site thousands of euros a month.

How to meet it

Initialise such tools on the first user interaction (click, keypress, scroll) when they add no content that needs indexing, and compare the sessions they bill with real user sessions.

How to test it

Vendor-billed session counts match analytics sessions, and a headless render of a page starts no vendor session before an interaction.

How Regensbot covers it

AutomaticNeedsOne URL

Decided from one URL.

An audit reads the response, the headers, the HTML, robots.txt, the sitemaps and the structured data, and the finding shows the evidence it saw.

How verdicts workWhat you connect

Sources

Google documents00

No Google document is cited. This requirement was said at Search Central Live and is not documented policy.

Claims in the knowledge base02

  1. D2-C163UndocumentedLightning session D: Rendering and JavaScriptSaid on stage
  2. D2-C165n/aLightning session D: Rendering and JavaScriptThe author's interpretation

Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)

Undocumented
Said or shown at the event, not in the documentation.
n/a
Nothing to verify: a quotation, framing, opinion or analysis.

Audit

Check it on your site.

One audit checks a URL against all 138 requirements and returns one finding for each, with its source. One URL decides 66; for each of the others, the finding says which source to connect.