Modern websites rely heavily on JavaScript. Frameworks such as React, Vue, and Angular create fast, interactive experiences, but they can also hide content from crawlers. Googlebot renders JavaScript, although with some delay and limitations. Many AI crawlers are less capable. If your content only appears after scripts run in the browser, some AI systems may never see it.
This guide explains why JavaScript creates challenges for AI crawlers, how to test what they see, and the rendering strategies that keep your content visible in AI search.
Why JavaScript Is a Problem for AI Crawlers
When a browser loads a JavaScript-heavy page, it downloads the initial HTML, then runs scripts that fetch data and build the page content. Humans see the finished page. Crawlers see whatever they can process.
- Googlebot renders JavaScript using a recent version of Chrome, though rendering can be delayed and resource-limited.
- Many AI crawlers fetch the initial HTML and may execute little or no JavaScript. Independent analyses of AI crawler behaviour have repeatedly found that several major AI bots do not render client-side JavaScript.
If your main content, product details, or pricing depend on client-side rendering, those AI crawlers may see an almost empty page. That content cannot be retrieved or cited. For background on retrieval, see how AI search works.
Rendering Approaches Explained
| Approach | How it works | AI crawler friendliness |
|---|---|---|
| Client-side rendering (CSR) | Browser builds content with JavaScript | Poor for crawlers that do not render JS |
| Server-side rendering (SSR) | Server sends fully rendered HTML | Strong |
| Static site generation (SSG) | HTML pre-built at deploy time | Strong |
| Incremental static regeneration | Static pages updated periodically | Strong |
| Hybrid rendering | Critical content server-rendered, interactivity added later | Strong if critical content is in HTML |
| Dynamic rendering | Serving pre-rendered HTML to bots | Workaround; Google no longer recommends it as a long-term solution |
The safest approach is to ensure important content is present in the initial HTML response.
How to Test What AI Crawlers See
View the Raw HTML
Open your page and view the page source rather than the rendered DOM. If key text, headings, and links are missing from the source, crawlers that do not execute JavaScript will not see them.
Disable JavaScript
Use browser developer tools to disable JavaScript and reload the page. What remains is roughly what non-rendering crawlers see.
Use a Command-Line Fetch
Fetch the page with a simple HTTP request tool and inspect the returned HTML. This mimics basic crawler behaviour.
Compare With Google’s Rendered View
Use the URL Inspection tool in Google Search Console to see Google’s rendered HTML. Compare it with the raw source to identify content that depends on JavaScript.
Check Server Logs
Review logs for AI crawler visits and the pages they request. If AI crawlers visit but your pages are not cited, rendering may be one reason.
What Content Must Be in the HTML
Prioritise these elements in server-rendered HTML:
- Main headings and body content
- Product names, descriptions, prices, and availability
- Service descriptions and location information
- Navigation and internal links
- Structured data (JSON-LD)
- Metadata such as title and meta description
- FAQ and support content
Interactive elements, such as calculators or filters, can still use JavaScript, as long as the core informational content is available without it.
Common JavaScript SEO Problems
Content Loaded After User Interaction
Content hidden behind tabs, accordions, or “load more” buttons that only fetch data on click may not be seen. Load the content in the HTML and use CSS or lightweight scripts to toggle visibility.
Client-Side Routing Without Proper URLs
Single-page apps sometimes use fragments or client-side routes that crawlers cannot follow. Use proper, crawlable URLs for each page.
Links Without href Attributes
Navigation built with click handlers instead of standard anchor tags with href attributes may not be followed. Use real links.
Lazy-Loaded Text
Lazy loading is great for images, but text content should not depend on scrolling events.
Structured Data Injected by Scripts
Schema added only via client-side JavaScript may be missed. Include JSON-LD in the server response.
Blocked Resources
If robots.txt blocks JavaScript or API endpoints needed for rendering, even Googlebot may struggle.
Framework-Specific Tips
- React: use a framework with SSR or SSG support, such as Next.js or Remix
- Vue: use Nuxt for server rendering or static generation
- Angular: use Angular’s server-side rendering support
- WordPress: most themes render HTML server-side; check page builders and plugins that load content with JavaScript
A Quick Audit Checklist
- View source on key templates: homepage, product, service, blog
- Confirm headings and main content are present
- Confirm internal links use href attributes
- Confirm JSON-LD is in the initial HTML
- Test with JavaScript disabled
- Compare raw HTML with Google’s rendered view
- Review AI crawler activity in logs
An AI SEO audit can run these checks across your whole site.
Final Thoughts
JavaScript powers great user experiences, but AI crawlers need content they can read without running complex scripts. Make sure your important information is present in the initial HTML through server-side rendering or static generation. That single change can make the difference between being invisible and being cited in AI search. For a complete technical review, use our AI SEO checklist and see the broader AI SEO ranking factors.
Frequently Asked Questions
Can AI crawlers render JavaScript?
Googlebot renders JavaScript, but many AI crawlers fetch only the initial HTML and execute little or no JavaScript. Content that depends on client-side rendering may be invisible to them.
What is the best rendering approach for AI SEO?
Server-side rendering or static site generation is best, because important content arrives in the initial HTML. Interactivity can still be added with JavaScript after the content loads.
How can I see what AI crawlers see on my page?
View the raw page source, disable JavaScript in your browser, or fetch the page with a basic HTTP tool. Missing content in these views is likely invisible to non-rendering crawlers.
Is dynamic rendering still recommended?
Google no longer recommends dynamic rendering as a long-term solution. It can be a temporary workaround, but server-side rendering or static generation are more reliable and easier to maintain.
Should structured data be added with JavaScript?
It is safer to include JSON-LD structured data in the server-rendered HTML. Schema injected only by client-side scripts may be missed by crawlers that do not execute JavaScript.
Do WordPress sites have JavaScript SEO problems?
Most WordPress themes render content server-side, but some page builders, sliders, and plugins load content with JavaScript. Check key templates by viewing source to confirm content is present.
