TL;DR
- AI crawlers like Google-Extended often do not execute JavaScript, so they see a blank page instead of your content.
- An estimated 69% of AI crawlers cannot render JavaScript, making server-side rendering (SSR) a requirement for AI visibility.
- If the AI cannot read your text, it cannot cite you in Google AI Overviews, no matter how good your content is.
- You can diagnose this issue by using Google Search Console’s URL Inspection tool to view the crawled HTML.
- The solution involves switching to a server-side rendered theme or using a dynamic rendering service.
Your modern, interactive WordPress theme looks amazing to human visitors. But to the AI crawlers that power Google's AI Overviews, it might be a completely blank page. This single technical issue is a primary reason why high-quality content gets ignored by AI search engines.
The beautiful animations, dynamic content loading, and slick user interface of your JavaScript-heavy theme come at a cost. They rely on the user's browser (the client) to run scripts and build the page. Many AI crawlers, built for speed and efficiency, skip this step entirely. They read the initial HTML file from your server, and if the content isn't there, they move on.
Why AI Overviews Are Ignoring Your JavaScript-Heavy Theme
The core of the problem is the difference between client-side rendering (CSR) and server-side rendering (SSR). Most visually impressive, app-like themes use CSR. The server sends a nearly empty HTML shell and a large JavaScript file. The user's browser then runs the script to fetch data and build the page.
AI crawlers, especially Google-Extended which feeds Gemini and AI Overviews, operate on a tight budget. Executing JavaScript requires significant CPU resources. It is far cheaper and faster for them to simply read pre-rendered HTML. When the crawler requests your page and receives an empty shell, it correctly concludes there is no content to index for AI answers. Your page is invisible.
This isn't a new problem. Traditional SEO has dealt with JavaScript rendering for years. But the stakes are higher now. While Googlebot has gotten better at rendering JavaScript for regular search, the new generation of AI-specific crawlers are far less patient. To learn more about this specific bot, read our guide on what Google-Extended is and why it matters. They are not trying to rank a webpage; they are trying to extract facts and answers as quickly as possible.
Client-Side vs. Server-Side Rendering for AEO
Understanding the two main rendering methods shows why one is a liability for AI visibility and the other is a necessity.
- ✓ **Server-Side Rendering (SSR)**
- ✓ Content is visible to all bots immediately
- ✓ Faster initial page load for users
- ✓ Works perfectly with all 18+ AI crawlers
- ✓ Structured data is always readable
- ✓ Best for Answer Engine Optimization
- ✗ **Client-Side Rendering (CSR)**
- ✗ Often results in a “blank page” for AI crawlers
- ✗ Content is invisible until JavaScript runs
- ✗ Slower perceived performance for first-time visitors
- ✗ Incompatible with most AI data ingestion pipelines
- ✗ Structured data may never be seen by bots
The choice is clear for sites that want to be cited in AI answers. Your content must be present in the initial HTML document your server sends. If it depends on a script running later, you are leaving your visibility to chance.
How to Tell if Your Theme Is the Problem
You can run a simple test to see what AI crawlers see. You do not need complex tools.
- Use Your Browser: In Chrome, go to one of your pages. Right-click and select "View Page Source." Do not use "Inspect Element," as that shows the rendered page. "View Page Source" shows the raw HTML from the server.
- Look for Content: Scan the source code. Can you find the text from your article paragraphs? If you see a lot of
<script>tags and not much human-readable text, you have a JavaScript-heavy theme. - Use Google Search Console: The most definitive test is to use the URL Inspection tool in GSC. Enter your URL and run a live test. After the test completes, click "View Crawled Page." In the panel that opens, view the "HTML" tab. This is exactly what Google's crawlers see. If it is missing your main content, you have found the reason you are not appearing in AI Overviews.
The AI Crawler Landscape in 2026
It is not just one bot you need to worry about. The AI space is populated by a growing number of crawlers from different companies, each with its own capabilities. Relying on JavaScript rendering means you are likely invisible to most of them.
Here is a breakdown of key AI crawlers and their known JavaScript capabilities.
| AI Crawler | Vendor | Primary Use | JavaScript Rendering |
|---|---|---|---|
| Google-Extended | Gemini / AI Overviews | Limited / Unreliable | |
| OAI-SearchBot | OpenAI | ChatGPT Search | Limited |
| PerplexityBot | Perplexity | Perplexity Answers | No |
| ClaudeBot | Anthropic | Claude Model Training | No |
| Applebot-Extended | Apple | Apple Intelligence | No |
As the table shows, you cannot assume AI bots will see your content if it is rendered with client-side JavaScript. The only reliable strategy is to deliver fully-formed HTML from the server. This is a foundational step if you want to understand how to appear in Google AI Overviews.
Fixing the JavaScript Problem for AI Visibility
If you have confirmed your theme is hiding your content from AI, you have a few paths forward. The goal is to ensure your content is served as plain HTML.
1. Switch to a Server-Side Rendered Theme
The most direct solution is to switch your WordPress theme. When choosing a new theme, look for terms like "classic theme," "block theme," or "built for speed." Avoid themes that advertise themselves as "React-based" or "Vue-based" unless they specifically state they support server-side rendering.
A good block theme built for the WordPress Site Editor is often the best choice. These themes are designed to be fast and generate clean HTML, making them perfectly readable for all AI crawlers.
2. Use a Dynamic Rendering Service
If you cannot change your theme, you can use a third-party service for dynamic rendering. These services act as a middleman. When a request comes from a real user, they pass them to your website as normal. When a request comes from a known bot, they intercept it, render the JavaScript on their own servers, and then serve the complete HTML page to the bot.
This allows you to keep your interactive theme for users while serving a fully-rendered, bot-friendly version to crawlers. Services like Prerender.io specialize in this. This is a more complex technical solution but can be effective if a theme change is not possible.
3. Pre-render Your Site (Static Site Generation)
For some sites, a static approach works best. Tools can crawl your JavaScript-based site and save the output as a collection of static HTML files. You then host these files instead of the live WordPress site.
This approach offers maximum speed and compatibility but sacrifices the dynamic nature of WordPress. You would need to re-run the process every time you update content. This is best for sites that do not change often.
Even with a perfectly rendered site, you still need to ensure your content is structured correctly. Proper use of schema markup is critical, but it's useless if the crawler can't see the content it describes. The AEO God Mode schema engine automates this process on content that is visible to crawlers.
Monitoring your site's logs is also essential. You need to know which bots are visiting and what they are seeing. You can learn more about how to check AI bots crawling your site traffic to get a clear picture of your AI visibility.
Ultimately, visibility in AI Overviews begins with crawlability. The most insightful, well-researched content is worthless if the machine reading it only sees a blank page. Fixing the JavaScript rendering issue is the first and most important step in any successful Answer Engine Optimization strategy. The AEO God Mode plugin includes a Google Search Console integration that can help spot indexing issues that often point back to rendering problems.