Buyer's question

AI can't read my site. Is it the JavaScript?

Often, yes. Most AI fetchers read the raw HTML a server sends back and do not run JavaScript, so a page whose text only appears after the browser executes a script can look to them like a blank page with a script tag in it.

By Reflexa Technologies — the team building Reflexa, the agent that works on your site · November 13, 2026

In brief

This is the second layer in the chain the What is GEO pillar lays out: a crawler first needs access to the page, then it needs to actually read what is on it. A page that lets every AI crawler through and still renders its answer only in the browser fails at this second layer, and the two failures look identical from the outside until you check which one it is.

Why doesn't AI see content my JavaScript adds?

Because an AI fetcher is a simple HTTP client, not a browser, so it never runs the script that would draw that content in. A server can answer a page request in one of two ways: send back a finished HTML document, or send back a mostly empty shell plus a JavaScript bundle that builds the real page once it runs in a browser. A fetcher that only reads that first response sees the shell. The headline, the pricing, the FAQ, whatever JavaScript was going to insert, none of it exists yet as far as that fetcher is concerned.

Why it matters: this is not a ranking signal or a quality judgment. It is a plumbing problem: the words are on your site, but they never reached the response the fetcher actually received.

Does Google treat JavaScript the same way AI engines do?

No. Google renders JavaScript, with a delay, through its own separate rendering queue, while the retrieval fetchers behind live AI answers largely do not render at all. Google's own documentation describes a two-wave process: pages are crawled and indexed first on the raw HTML, then queued for rendering later so the JavaScript-built content can be picked up on a second pass. The fetchers that power a live ChatGPT, Claude or Perplexity answer work on a tighter loop than that queue and read what the server sends back immediately, without a rendering step behind it.

Proof: Google Search Central — Understand the JavaScript SEO basics.

Do this: design for the fetcher with no rendering step, since a page built that way is also fine for Google's eventual render. Building only for Google's second wave leaves AI answer engines with nothing.

How do I check if my own site has this problem?

Open the page, view its source rather than its rendered DOM, and search for your own headline and opening sentence. A browser's "Inspect" or "Elements" panel shows the page after JavaScript has already run, which is exactly what a fetcher that skips that step never sees. "View page source" (or curling the URL) shows the first response instead, the same thing most AI fetchers read.

Shortcut: the Text without JavaScript check fetches the page twice, raw and rendered, and lists exactly which blocks of text only appear after rendering.

Which platforms and frameworks already solve this?

Most static sites and no-code builders already send finished HTML; the risk is concentrated in single-page apps built by hand. Framework choice decides this more than almost any other setting on the page.

Platform or frameworkText in the raw HTML by default?
Webflow, Framer, SquarespaceYes, these render server-side already
WordPress (standard themes)Yes, server-rendered PHP
Next.js, Nuxt, Astro, SvelteKit, RemixYes, if server rendering or static generation is configured; no if left as a plain client-rendered app
Plain React, Vue or Angular (client-rendered only)No, the page ships an empty shell and a script bundle

Note: the framework name alone does not settle it. A Next.js or Nuxt site can still be configured to render only in the browser; the setting that matters is whether server rendering or static generation is actually switched on for the pages that carry your answers.

What fixes it if my site is already client-rendered?

Server-render or pre-render the text that matters, and let JavaScript enhance the rest. You do not need to rebuild the whole site to fix this; you need the words a buyer's question would be answered by to exist in the first HTML response.

Bottom line: the goal is not "no JavaScript." It is "the sentence that answers the question exists before any script runs."

What to do this week

None of this requires buying anything, and each step takes a few minutes:

Keep reading

Frequently asked questions

Is my site invisible to AI if I built it in React or Vue?

Not necessarily. It is invisible only if the text that answers a buyer's question renders in the browser with no server rendering or pre-rendering step behind it. Many React and Vue sites already ship server-rendered or statically generated HTML.

Does Google rendering JavaScript mean AI engines do too?

No. Google renders JavaScript, with a delay, through its own separate rendering queue. The AI retrieval fetchers that answer engines use to read a page live, such as OAI-SearchBot and PerplexityBot, largely read only the raw HTML a server returns.

How do I check this on my own site in one minute?

View the page source, not the browser's Elements panel, and search for your own h1 and opening sentence. If they are missing from the source, a fetcher that does not run JavaScript cannot see them either.

What is the fastest fix for a single-page app?

Add server-side rendering or static pre-rendering for at least the title, the h1, the opening paragraph and the key facts on the page. JavaScript can still enhance everything else after that core text is already in the HTML.

Does fixing the JavaScript problem guarantee AI will recommend me?

No, it only removes a hard blocker. Once a fetcher can read the page, the text still has to answer the buyer's question in the first sentence to be worth citing or recommending.

Can AI actually read your pages?

The free check reads your site the way ChatGPT, Claude and Perplexity read it, raw HTML included, and shows exactly where the gap is. 3 minutes, evidence included.

Run the free check →

Done for you by Reflexa Agent: how the agent fixes this on your site · the 35+ checks it runs · Reflexa Agent på svenska