JavaScript rendering and AI crawlers

When a crawler fetches your page, it gets the initial HTML the server sends. A browser then runs JavaScript to build the final page a human sees. But many AI crawlers don't run that JavaScript - they read only the initial HTML. So if your content only appears after JS executes (client-side rendering), those crawlers see an empty or skeletal page. Content they can't see, they can't cite.

This is one of the most common and overlooked technical reasons genuinely good content fails to earn citations: it's there for humans, but invisible to the crawler.

The solution is to ensure your important content is present in the HTML the server sends, before any JavaScript runs. That means server-side rendering (SSR) or static generation - the page arrives complete. Then a crawler that doesn't run JS still sees your full content, and one that does run JS sees the same thing. Either way, you're citable.

Don't trust the rendered page in your browser - that's after JS runs. To see what a non-JS crawler sees, fetch the raw HTML: use 'view source' (not inspect/DevTools, which shows the rendered DOM), or a command-line fetch. If your key content, headings, and answer text aren't in that raw HTML, a non-JS crawler can't see them either.

You don't have to drop React/Vue/etc. Modern frameworks support SSR and static generation precisely so content ships in the initial HTML while you keep a rich JS app. The goal isn't 'no JavaScript' - it's 'important content present before JS runs'. Interactive enhancements can still be client-side; the citable content just needs to be server-rendered.