Why it matters
Said at Search Central Live by a community speaker: offer counts, prices and promotions sometimes differ between the server HTML and the rendered page, for example a different newsletter discount in each, so bots and users can get different versions. Google's documentation does not cover this case specifically.
How to meet it
Generate both versions from the same data source with the same filters, and treat any difference in prices, availability, offer counts, links or meta tags between raw and rendered HTML as a bug.
How to test it
On every release, diff the raw HTML (curl) and the rendered HTML (headless Chrome or URL Inspection) of each key template for prices, offer counts, links and meta tags.
How Regensbot covers it
Decided automatically once Regensbot renders your pages.
Headless Chromium renders the page on an isolated render service, and the raw and the rendered HTML run through the same parsers.
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 base03
- D2-C147UndocumentedLightning session D: Rendering and JavaScriptSaid on stage
- D2-C137n/aLightning session D: Rendering and JavaScriptShown on screen
- D2-C148n/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.