Content is present in the initial HTML

What this check means

Compares the content in your HTML as delivered against what a browser produces after running your JavaScript.

Why it matters

This is the most consequential failure on the list, and the least visible. The page looks perfect in your browser because your browser runs the JavaScript. Many AI crawlers do not — they read the HTML as delivered. If your content arrives only after a bundle executes, those systems see an empty container.

How we detect it

We first look at the HTML exactly as served: how much readable text it contains, whether it has an empty framework mount, and how many scripts it loads. When that is unambiguous we stop there. When it is not, we render the page in a headless browser and compare the text a browser ends up with against the text that was delivered. Rendering is time-boxed; if it cannot complete we fall back to the delivered-HTML signature and say so.

How to fix it

Server-render or pre-render your pages so the content is in the HTML. Every major framework supports this — Next.js, Nuxt, SvelteKit and Remix all render on the server by default.

Check whether this applies to your site.

Run an AI audit