Can AI crawlers read JavaScript-rendered content?

Google's crawler renders pages in a headless browser after fetching the HTML. Vercel's December 2024 analysis of crawler traffic reported that Gemini benefits from Googlebot's rendering and that AppleBot also renders JavaScript, but that the main crawlers from OpenAI, Anthropic, Meta, ByteDance and Perplexity did not execute it. Crawler behaviour can change, so re-test periodically.

What this means for your site:

• Single-page apps that build the page in the browser may be invisible to AI assistants even if they rank in Google.
• Content loaded after an interaction, such as tabs or 'load more' buttons, may be missed if it isn't in the initial HTML.
• Prices, product details and FAQs injected by client-side scripts are common blind spots.

The fix is to put important content in the server response, through server-side rendering, static generation or pre-rendering. A quick test is to view the page source, not the inspected page, or fetch the URL with JavaScript disabled, and check that your headline, main copy and links are there.

Our AI search readiness study includes this check across 1,319 websites.