Text is present without JavaScript. Most AI fetchers read HTML; they do not run your JavaScript.
The check fetches each page twice — the raw HTML, and the page rendered in a headless browser — and compares the main text. Content that exists only in the rendered version is content a fetcher reading raw HTML never sees.
Most AI fetchers read HTML; they do not run your JavaScript. A React, Vue or Angular page that renders client-side hands them a root div and a script tag. To the fetcher the page is empty, and an empty page is quoted by nobody.
View the page source (not the inspector — the source) and look for your headline and first paragraph. If they are not there, they are drawn by JavaScript. The what-AI-sees tool measures how much of the main content is readable without rendering.
What AI actually sees → — free, no signup.
What the agent does: the agent can write the opening into the page itself — the heading and first paragraph in the HTML — once you approve the words.
Part of the 23 checks · group: Page content — text without JavaScript, response time, internal links, answer-first structure, self-contained sections, headings/dates/authorship.
Google does, with a delay. The AI retrieval fetchers largely do not; they read what the server sends. Design for the raw HTML and both are served.
The check reports coverage: how much of the rendered text is in the raw HTML. Below the threshold it fails, with the blocks that only appear after render listed.
The page check reads your public pages from outside and runs all 22 — free, no signup, no AI engine involved.