Methodology
Server-side rendered content
ia.server-rendered-content · 3.1
Read
MUST
Measured study
AR-READ-01
AR-READ-03
Why it matters
Fetch-only crawlers and non-rendered retrieval cannot depend on client-side JavaScript. Browser agents may combine the rendered DOM, accessibility tree, and screenshots. Meaningful server-rendered HTML keeps core content available across both access modes.
How to fix it
Render the main content in the HTML response, without JavaScript.
-
Fetch the page without JavaScript and compare the text with the rendered page.
-
Enable server-side rendering or static generation for the main content.
-
Keep headings, body text and links in the initial HTML.
Verify
curl -sf https://{domain}/
Expected: The HTML response contains the main headings and body text
Run a new scan for this checkpoint:
isagentready results {domain} --checkpoint ia.server-rendered-content
Details Mapping, lifecycle and references
- AR mapping
- Full match
- Evidence source
- agentready.org AR-READ-01
- Score role
- Core
- Introduced
- 2026-08-24
- Methodology version
- 2026-10-22