Signal
Server-rendered, crawlable content
Commerce-critical fields and full policy text appear in the raw server HTML, not behind JavaScript, a PDF, or a click-to-fetch accordion, so a non-executing crawler can read them.
Per-platform status
Where a platform documents relevant behavior, its status and source are shown. Undocumented platforms show "unknown" - honest unknowns, never invented.
| Platform | Status | Notes | Source |
|---|---|---|---|
| ChatGPT | Unknown | Not documented by this platform. | - |
| Gemini / Google AI Mode | Supported | Google documents that rendering is queued and deferred, that not all bots run JavaScript, and recommends server-side or pre-rendering for critical content. | Source (opens in new tab) · verified 2026-03-04 |
| Perplexity | Unknown | Not documented by this platform. | - |
| Copilot | Unknown | Not documented by this platform. | - |
| Claude | Supported | The web fetch tool does not support pages rendered dynamically with JavaScript and accepts only text, HTML and PDF. | Source (opens in new tab) · verified 2026-09-18 |
Evidence and sources
This signal is typed hypothesis (Low confidence).
- ucptools.dev: UCP/ACP validator (opens in new tab) · 2026-07-08
How to act on this
Load the product and policy pages with JavaScript disabled (view source, not devtools) and confirm title, price, availability, description, and full policy text are all present in the raw response.
Related checklist items
Handbook chapters