Why it matters
Browser APIs that need user permission, such as location and payments, are not supported when Google renders a page, and WebGL effects are not applied. Google recommends feature detection with polyfills or differential serving, and prerendering on the server for content that depends on WebGL.
How to meet it
Render indexable content first; ask for permissions only after a user action and keep a complete default (for example the full store list) if the request is declined. Wrap WebGL and other optional APIs in feature detection with a plain HTML fallback. Add polyfills for missing APIs the content needs, knowing that some features cannot be polyfilled.
How to test it
In URL Inspection the screenshot and rendered HTML show the main content, and the JavaScript console messages of the live test show no uncaught errors from missing APIs.
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 documents02
- 01Fix Search-related JavaScript problemsGoogle Search Central (opens in a new tab)
- 02Understand the JavaScript SEO basicsGoogle Search Central (opens in a new tab)
Claims in the knowledge base05
- D2-C269ConfirmedWhat is Google friendly JavaScriptSaid on stage
- D2-C277ConfirmedWhat is Google friendly JavaScriptSaid on stage
- D2-C278SourceWhat is Google friendly JavaScriptGoogle's documentation
- D2-C280SourceWhat is Google friendly JavaScriptGoogle's documentation
- D2-C282n/aWhat is Google friendly JavaScriptThe author's interpretation
Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)
- Confirmed
- Google's documentation states the same thing.
- Source
- The claim is the cited document itself.
- n/a
- Nothing to verify: a quotation, framing, opinion or analysis.