geo
How to fix: Core content in raw HTML (no JS required)
Why this matters
Most AI crawlers don't execute JavaScript. Client-side rendered content is invisible to them — and cannot be cited. Server-side rendering or static generation is non-negotiable for content pages.
Background
Most AI crawlers don't execute JavaScript. Client-side rendered content is invisible to them — and cannot be cited. Server-side rendering or static generation is non-negotiable for content pages.
References
AI crawler behaviour · Server-side rendering research
How to fix
Code snippet for each stack we cover. Pick the one matching your server / framework.
nginx
No server config — application architecture decision.
apache
Same.
cloudflare
Cloudflare Pages supports SSR via Workers; Cloudflare's Bot Management can also serve pre-rendered HTML to known AI bots.
wordpress
WordPress is server-rendered by default. The risk: a heavy theme or page builder (Elementor, Divi) sometimes wraps content in JS-dependent components. Check raw view-source for the page content.
flask
Already server-rendered — good. Avoid pure-frontend SPA patterns for content pages.
express
Use Next.js / Remix / Nuxt for SSR — not raw React without rendering.
rails
Already server-rendered — good. Hotwire / Turbo enhances without breaking the SSR baseline.
Verify it's working
curl -A 'GPTBot/1.0' https://your-site/ | grep '<h1>' — should show your H1 text in the raw response.
Want to know if your site has this issue?
Run a free 53-check audit — security, GDPR, NIS2, and technical SEO.
Audit my site →