Why the raw HTML matters
A browser runs your JavaScript and shows the finished page. Many AI crawlers do not: they read the HTML your server returns and stop there. A site built as a client-side app (React, Vue, Angular without server rendering) can look complete to visitors and empty to AI assistants.
An assistant cannot quote or recommend text it never received. This check shows how much of your page is in the raw HTML, and how much needs JavaScript.
How to read the result
Content visible without JavaScript: the raw HTML holds most of the text, AI crawlers read it.
Content partly behind JavaScript: the raw HTML holds less than 60 % of the text. Part of the page is invisible to crawlers that do not run JavaScript.
Content behind JavaScript: the raw HTML holds less than 20 % of the text. For those crawlers, the page is close to empty.
How to fix it
Render the content on the server (server-side rendering) or generate the pages at build time (static generation). Most frameworks offer one or the other: Next.js, Nuxt, SvelteKit, Astro, Remix. The goal is that the HTML returned by your server already contains the text, headings and links.
Frequently asked questions
Which page should I check?
Start with your home page, then your most important pages: product, pricing, articles. Each page is checked on its own.
Does this check use AI?
No. It reads your page twice, once as raw HTML and once in a browser, and counts the words. Nothing is sent to an AI model.
My page is fine here. Can AI assistants still miss it?
Yes: robots.txt, a firewall or a CDN rule can block AI crawlers before they read anything. The AI crawler checker covers robots.txt, and a full Beakon audit checks every page of the site.
A Beakon audit also checks your technical SEO and structured data, and tests whether Claude and Perplexity cite you. Free to start.
Run a free full audit