Agent Ready HTML

How to move the answer into the initial HTML without a rewrite

In short

If the answer only appears after scripts run, a fetch-only agent never sees it. The cheapest fixes are server rendering, prerendering at build time, or putting a prerendered copy in front of agents. Pick the one your framework already supports, then confirm with a plain fetch.

The aim is narrow: the sentence a person came for must be in the bytes the server sends. A rewrite is not required if your framework can already render on the server.

What the evidence says

  • Client-rendered sites may need server-side rendering, prerendering or a hybrid so fetch-only agents can read answers. [primary source] source, read 4 November 2026.
  • Astro prerenders every route by default and lets single routes opt out with export const prerender = false. [primary source] source, read 4 November 2026.
  • Next.js App Router pages and layouts are Server Components by default and prerender HTML. [primary source] source, read 4 November 2026.
  • Nuxt universal rendering returns fully rendered HTML; one line of configuration switches it to client-side rendering. [primary source] source, read 4 November 2026.
  • Scrunch AXP serves prerendered HTML to AI user agents from a separate origin without changing the human site. [vendor claim] source, read 4 November 2026.
  • Cloudflare Markdown for Agents converts the HTML the origin returns, so it cannot recover content that only exists after JavaScript runs. [primary source] source, read 4 November 2026.

Steps

  1. Find the pages that matter (pricing, docs, product pages) and run each through the viewer. Any page that shows few words in the initial HTML is a candidate.
  2. Check how the framework renders by default. Astro prerenders routes unless one opts out; Next.js App Router pages are Server Components that prerender; Nuxt renders on the server unless a configuration switch turns it off.
  3. If a route was set to client-only rendering, remove the opt-out for pages that carry content, or move the content fetch to the server.
  4. If a rewrite is out of reach, serve a prerendered copy to agent user agents from the edge, and check that it matches what people see.
  5. Convert after rendering, not before: a markdown converter at the edge works on the HTML the origin returns, so it cannot recover text that only exists after scripts run.
  6. Run the viewer again. The H1 and the first 200 words should now be marked in the left pane.

Check the result

The test is the left pane of the viewer: if the H1 and the first 200 words are highlighted there, the page passes this check for a plain-fetch client. Open the viewer to run it on your own URL.

Related: all guides, initial HTML, llms.txt, checking the initial HTML like an agent.

Sources

  1. Vercel and Ora: Make your site readable by AI agents https://vercel.com/kb/guide/make-your-site-readable-by-ai-agents, read 4 November 2026
  2. Astro: on-demand rendering https://docs.astro.build/en/guides/on-demand-rendering/, read 4 November 2026
  3. Next.js: Server and Client Components https://nextjs.org/docs/app/getting-started/server-and-client-components, read 4 November 2026
  4. Nuxt: rendering modes https://nuxt.com/docs/4.x/guide/concepts/rendering, read 4 November 2026
  5. Scrunch help: How AXP serves content to AI agents https://helpcenter.scrunchai.com/en/articles/12845899-how-axp-serves-content-to-ai-agents, read 4 November 2026
  6. Cloudflare docs: Markdown for Agents https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/, read 4 November 2026

Last reviewed 4 November 2026