How to fix content not in the HTML (GEO)

This finding occurs when the majority of your page text is loaded via JavaScript rather than being present in the source HTML. If LLM crawlers cannot see the text in the raw response, they cannot process or cite your content.

What is wrong

Modern web frameworks often send a nearly empty HTML shell to the browser, relying on client-side JavaScript to fetch and render the text. You can identify this by viewing the page source (Ctrl+U) in your browser; if the main body text is missing from the code, it is invisible to most AI agents.

Why it matters

Unlike Googlebot, which has a dedicated rendering phase, many Generative Engine Optimization (GEO) crawlers and LLM agents operate on raw HTML to save resources. If less than 50% of your content exists in the served HTML, these engines will perceive the page as empty or low-value, preventing it from being used as a citation source.

How to fix it

1. Implement Server-Side Rendering (SSR)

Configure your web framework (such as Next.js, Nuxt, or React) to render the initial state of the page on the server. This ensures the full text content is present in the HTML document before it reaches the crawler.

2. Use Static Site Generation (SSG)

For content that does not change frequently, use SSG to build HTML files at deployment time. This provides the fastest possible response and guarantees that every word is indexable without JavaScript execution.

3. Verify with a 'No-JS' view

Disable JavaScript in your browser settings and reload the page. If the main content disappears, the fix is not yet complete. Ensure all critical text remains visible and readable.

Platform notes

For WordPress users, this is rarely an issue unless using a 'headless' setup or heavy AJAX-based themes. Ensure your theme follows standard PHP rendering patterns.