Render-parity for AI crawlers

Render parity compares two versions of the same page: the raw HTML the server returns, and the DOM a browser builds after running the page's JavaScript. On a server-rendered site they are nearly identical. On a client-rendered single-page app, the raw HTML can be an empty shell with a script tag, and every heading, paragraph, and case study appears only after hydration.

That gap matters more for AI engines than for Google. Googlebot renders JavaScript, though in a deferred second pass. The main AI crawlers have been observed fetching pages without executing JavaScript: Vercel's analysis of crawler traffic published in December 2024 found that none of the major AI crawlers it observed, including GPTBot, ClaudeBot, and PerplexityBot, executed JavaScript, even when they downloaded the script files. If the content is not in the raw HTML, those engines do not see it, cannot index it, and will not cite it.

We measure parity as the share of the rendered page's meaningful text that is already present in the raw HTML, and we report it per page rather than as a single pass or fail, because the fix depends on which content is missing. The remedies are well understood: server-side rendering or static generation for marketing pages, streaming server components, or pre-rendering for crawlers as a last resort. For an AI agency in particular, low render parity is the most common and most damaging finding in our audit.