GEO clusterJul 12, 2026·4 min read
Making content extractable: the anti-JavaScript checklist
AI models crawl HTML, not React. Here's how to keep your best content in reach.
Part of the Generative Engine Optimization cluster
New here? Start with the pillar guide: Generative Engine Optimization: the complete guide.
TL;DR
Most AI crawlers do not execute JavaScript. If your answer content only appears after a client-side render, models see an empty shell and cite someone else.
Key facts
- GPTBot and PerplexityBot do not run JS.
- Content behind tabs, accordions, or ‘load more’ buttons is often invisible.
- Server-side rendering or static generation solves 90% of extractability issues.
The checklist
- Server-render or statically generate hero and answer sections.
- Avoid gating content behind interactive tabs or accordions loaded via JS.
- Publish primary facts in plain HTML, then decorate with JS.
- Test by disabling JS in your browser — can you still read the answer?
Frequently asked questions
Is a JS-rendered SPA fatal for GEO?
Not always — but you need SSR or a pre-rendered version for the pages you want cited.
Put this into practice
Run a RocketRank™ audit and see exactly where you're invisible — and the one-click fix for each finding.
