JavaScript rendering

JavaScript rendering is running a page's scripts to build its content. Most AI crawlers don't do it, so content that only appears through JavaScript can be invisible to them.

TechnicalUpdated 1 min read

Also called client-side rendering · JS rendering

What it means

Some websites send a nearly empty page and use JavaScript in the browser to fill it with content. People see the full page. A crawler that doesn't run JavaScript sees the empty one.

Why it matters for AI

Googlebot runs JavaScript, so Google's AI usually sees the full page. But analyses of AI crawler traffic have found that the main AI crawlers, such as OpenAI's and Anthropic's, generally don't run JavaScript. They read the raw HTML.

If your prices, features or reviews only appear after scripts run, those AI tools may not see them.

How to check

  • View source in your browser (not "inspect"): is the important text there?
  • Or fetch the page with a simple tool like curl and look for your key facts.

How to fix it

Use server-side rendering or static generation for important pages, so the content is in the HTML from the start. Most modern web frameworks support this.

Example

A pricing page loads its plans from an API after the page opens. In the raw HTML, there's only "Loading...". ChatGPT keeps saying the company "doesn't publish pricing".

After switching the page to server-side rendering, ChatGPT starts quoting the prices.

Free tool: AI Page InspectorSee any page the way an AI crawler does: the text it gets, the passages it can quote, and checks with fixes.Try it →

Frequently asked questions

Does Google's AI see JavaScript content?

Usually, because Googlebot renders pages. It can be slower, though.

Is my site affected?

If it's built as a single-page app without server rendering, likely. Check the raw HTML of your key pages.

Do AI browsers run JavaScript?

Yes. They're real browsers. The problem is crawlers, not browsers.

Go deeper

All posts →

Make AI search your next revenue channel

Start free trial