Ask An SEO: Can AI Systems & LLMs Render JavaScript to Read ‘Hidden’ Content?
For this week’s Ask An SEO, a reader asked:
“Is there any difference between how AI systems handle JavaScript-rendered or interactively hidden content compared to traditional Google indexing? What technical checks can SEOs do to confirm that all page-critical information is available to machines?”
This is a critical question. Beyond the hype around LLM-optimization lies a real technical challenge: ensuring your content can actually be found and read by AI systems.
While Googlebot has improved significantly at crawling and rendering JavaScript-heavy pages, newer AI bots may not handle it the same way. Here’s what you need to know—and what you can do to ensure your content is accessible to both.
How Googlebot Renders JavaScript
Googlebot processes JavaScript in three stages: crawling, rendering, and indexing.
1. Crawling
-
Pages are queued for crawling if discovered on the web.
-
Pages blocked via
robots.txtor other methods will be skipped.
2. Rendering
-
Googlebot checks for index eligibility (e.g., no
noindexmeta tags). -
Rendering is queued; the full page DOM is constructed once JavaScript executes.
-
Resource-intensive, so rendering may not be instantaneous.
3. Indexing
- Eligible pages are stored in Google’s index for search results.
Interactively Hidden Content
Content hidden behind tabs, accordions, or other interactive elements may not be accessible to Googlebot unless it is already present in the DOM on first load.
Think of hidden content as “in a box” in the HTML—the server needs to “open the box” before Googlebot requests the page. If it’s hidden until user interaction, Googlebot might miss it.
Making Content Accessible to Googlebot
Server-Side Rendering (SSR) is the best way to ensure content is immediately accessible:
-
The server pre-renders the HTML with all page content.
-
Browsers and bots receive fully-rendered content without executing JavaScript.
Client-Side Rendering (CSR) relies on the browser to compile JavaScript before content is visible, which can be a problem for bots.
How LLM Bots Handle JavaScript
Unlike Googlebot, there is no standard for LLM bots. Each AI system crawls the web differently, and most do not share their technical details.
-
Vercel’s 2024 research and Glenn Gabe’s follow-up tests showed that most LLM bots cannot render JavaScript.
-
Exceptions include Gemini (uses Googlebot infrastructure), Applebot, and CommonCrawl’s CCbot.
-
Interactively hidden content is particularly challenging for LLM bots; if it requires JS execution, they may miss it entirely.
Key takeaway: cater to the lowest-capability bots by ensuring critical content is available in the static HTML.
Technical Checks for SEOs
1. Check the DOM via Developer Tools
-
Open Chrome → Right-click → Inspect → Elements tab.
-
Ensure content is present in the DOM without interacting with the page.
2. Google Search Console (GSC)
-
Use the URL Inspection tool → “Test live URL” → “View tested page.”
-
Confirms Googlebot can see your content.
3. Source HTML Check
-
Right-click → View Page Source.
-
Ensure the text exists in the static HTML, so even the lowest-capability LLM bots can access it.
4. Ask LLMs Directly
-
Prompt AI systems to extract or summarize content.
-
If they fail to read it, the content may be JavaScript-dependent and invisible to bots.
What This Means for Your Website
-
Googlebot is much better at handling JavaScript than LLM bots.
-
LLM bots are a different type of crawler and may never mimic Googlebot.
-
Actionable strategy:
-
Ensure all critical content loads in the DOM on page load.
-
For AI visibility, ensure content exists in the static HTML.
-
Test regularly via GSC, developer tools, and LLM prompts.
-
By doing this, you cover both Google’s search index and emerging AI-driven search tools.
Additional Resources
-
Google’s JavaScript Warning & How It Relates to AI Search
-
How LLMs Interpret Content: How To Structure Information For AI Search
-
The Technical SEO Debt That Will Destroy Your AI Visibility