Extractability check

AI crawlers do not run JavaScript. This fetches your page as raw HTML and reports how much of your content, your title and your schema actually reaches them.

GPTBot downloads JavaScript on roughly 11.5% of requests and executes none of it. ClaudeBot downloads it on roughly 23.8% and executes none. Onely's February 2026 analysis found 42% of JavaScript-rendered content never reaches AI systems at all.

So the question is not whether your page looks right in a browser. It is what is present in the HTML the server returned, which is what this fetches. If the word count here is near zero and your page is full of text, that text does not exist as far as the answer engines are concerned.

• critical
  The page's content only exists after JavaScript runs

  AI crawlers do not execute JavaScript. GPTBot, ClaudeBot and PerplexityBot read the raw HTML and nothing else, so a page whose copy is assembled in the browser is a blank page to every answer engine except Google's.

• high
  Title or description is injected by script rather than served

  A title set by JavaScript is a title half the machines reading the page never see. Google usually renders and catches it. The answer engines do not.

• high
  Body content is not present in the served HTML

  If the HTML arrives empty, an answer engine that does not execute JavaScript sees nothing.

• high
  An SEO tool is injecting fixes client side

  Scripts that apply SEO changes in the browser produce fixes no AI crawler can see, and the changes disappear the day the subscription stops because they were never written into the site.

The content is rendered client side. A single-page application, or a framework that ships an empty shell and hydrates it, produces exactly this result. The fix is server-side rendering or static generation for the pages you want cited.

Less, because Googlebot renders JavaScript. It matters for the answer engines, and it matters for how quickly Google picks up a change, because rendering is a second queue with its own delay.