--- title: "JavaScript-only pages without a rewrite | Agent Ready Checklist" description: "How to handle JavaScript-only pages without a rewrite. Steps, a command for each step and the cited facts behind them. Run the kit to confirm the result." canonical: https://agentreadychecklist.com/guides/javascript-only-pages-without-a-rewrite site: "Agent Ready Checklist" last_updated: 2026-11-05 date: 2026-11-04 section: "Guides" --- # JavaScript-only pages without a rewrite | Agent Ready Checklist > How to handle JavaScript-only pages without a rewrite. Steps, a command for each step and the cited facts behind them. Run the kit to confirm the result. Source: https://agentreadychecklist.com/guides/javascript-only-pages-without-a-rewrite Site: Agent Ready Checklist Last reviewed: 2026-11-05 Agent endpoints: https://agentreadychecklist.com/llms.txt (index), https://agentreadychecklist.com/openapi.json (API), https://agentreadychecklist.com/mcp (MCP server), https://agentreadychecklist.com/ask (search) Access: https://agentreadychecklist.com/auth.md (no key). Pricing: https://agentreadychecklist.com/pricing.md (free). # How to handle JavaScript-only pages without a rewrite Get answers into the initial HTML with prerendering or a hybrid route, page by page, starting with docs and pricing. It covers 3 requirements: AR-READ-01, AR-READ-03, AR-READ-11. Ora's lab found (published 2026-10-21) that the homepage was reached in 69% of runs and docs in 83%, so those two page types come first. ## Before you start You need the list of pages that answer questions agents ask: pricing, docs, product pages, support answers. Work through them in that order. ## Steps 1. **[AR-READ-01: Answer in the initial HTML.](https://agentreadychecklist.com/checklist/ar-read-01/)** Put the answer in the initial HTML: server-rendered or prerendered, not injected by a single-page app after load. ```bash curl -fsSL https://agentreadychecklist.com/kit/verify.sh | bash -s -- https://example.com --only=initial-html ``` Watch for: Prerendering the shell but fetching the answer client-side. 2. **[AR-READ-03: Home page with real links.](https://agentreadychecklist.com/checklist/ar-read-03/)** Serve the homepage as raw HTML with real links to docs, product and pricing. ```bash curl -fsSL https://agentreadychecklist.com/kit/verify.sh | bash -s -- https://example.com --only=initial-html ``` Watch for: Navigation built from
elements with click handlers. 3. **[AR-READ-11: Pricing as first-party HTML.](https://agentreadychecklist.com/checklist/ar-read-11/)** Publish pricing on a first-party page: plans, free tier and limits as HTML text, not an image, a calculator or a sales form. ```bash curl -fsSL https://agentreadychecklist.com/kit/verify.sh | bash -s -- https://example.com --only=initial-html ``` Watch for: Prices only inside a toggle rendered by JavaScript. 4. **Pick the cheapest route per page.** A page that rarely changes can be prerendered at build time. A page that depends on a request can render on the server for that route only, while the rest of the app stays a single-page app. Start with the pages that hold facts. ## How you know it is done You are done when each of those pages returns its answer in the response of a plain fetch, and the kit initial-html check prints PASS for them. ## The facts behind it - The spec calls moving a client-rendered site to SSR, prerendering or a hybrid a real migration and the prerequisite for agents that fetch rather than run JavaScript.primary source: [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md), read 2026-11-04 - Ora's lab found (published 2026-10-21) that the homepage was reached in 69% of runs and docs in 83%, so those two page types come first.vendor claim, 2026-10-21: [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md), read 2026-11-04 - Ora's lab found (published 2026-10-08) that pricing answers built from the business own pages were 60% accurate against 37% from elsewhere.vendor claim, 2026-10-08: [ora.ai/blog/ax-is-the-new-aeo](https://ora.ai/blog/ax-is-the-new-aeo?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=guide), read 2026-11-04 - The spec says content negotiation, .md endpoints, agent detection and frontmatter did not change whether agents succeeded once the HTML carried the answer.primary source: [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md), read 2026-11-04 - is-agentic says its public report pages render the latest score in the initial HTML so crawlers need not run JavaScript.vendor claim, 2026-11-04: [is-agentic.com](https://is-agentic.com/), read 2026-11-04 ## Sources - [github.com/agentready-org/standard/blob/main/spec/spec.md](https://github.com/agentready-org/standard/blob/main/spec/spec.md)read 2026-11-04 - [ora.ai/blog/ax-is-the-new-aeo](https://ora.ai/blog/ax-is-the-new-aeo?utm_source=agentreadychecklist.com&utm_medium=referral&utm_campaign=guide)read 2026-11-04 - [is-agentic.com](https://is-agentic.com/)read 2026-11-04 Edition Data 2026-11-04 Reviewed 2026-11-05 Spec AgentReady v2.0, 273d2d7 Crawl 13,071 rows, 2026-11-04 Ora 132 checks, contract 1.38.0, 2026-11-05 Verify with Ora The scanner this site recommends for the whole checklist. 132 checks, a score out of 100, no account. `npx ax@0.10 audit --min-score ` [Why Ora, and its limits](https://agentreadychecklist.com/verify-with-ora/) Method - [How rows, commands and rates are made](https://agentreadychecklist.com/method/) - [How an Ora check is matched to a row](https://agentreadychecklist.com/checklist/ora-checks/) - [Pass rates by rank band](https://agentreadychecklist.com/data/by-rank/) Sources and read dates sit at the foot of the page. Last reviewed 2026-11-05. AgentReady v2.0, read 2026-11-04.