In short. JavaScript-dependent content requires a compatible renderer, so initial HTML and service-specific rendering checks matter for AI search access.
Definition: JavaScript rendering executes scripts to produce page content. Client-side rendering loads content in the browser, which can leave a crawler dependent on JavaScript execution to access that content.
Key facts
- As of 17 October 2026, Google's JavaScript documentation explains that some sites require JavaScript execution before Google can see their actual page content.
- Google's AI features documentation requires a page to be indexed and eligible for a Search snippet to qualify as a supporting link in AI Overviews or AI Mode.
- As of 17 October 2026, Anthropic's web fetch documentation states that its API tool does not support websites dynamically rendered with JavaScript.
How does rendering change what a crawler receives?
Google's JavaScript basics guide describes an application shell: the initial HTML lacks the actual page content, which scripts generate later. For a crawler processing that page, obtaining the initial response and executing those scripts are separate requirements.
The same guide provides this HTML link in its example of accessible page URLs:
<a href="/products">Our products</a>
The link has an explicit destination in its href attribute. When reviewing a JavaScript site, the useful comparison is between content present in the initial HTML response and content produced after execution. A browser displaying the completed page shows the latter.
What changes for AI search access?
Google's AI features guide connects eligibility for AI Overviews and AI Mode to Search indexing and snippet eligibility. It also recommends making important content available as text. Rendering therefore matters when scripts supply the text that Google needs to process for Search.
AI services have different access paths. Anthropic's web fetch tool retrieves content from specified pages through its API, with an explicit restriction on dynamically rendered websites. The documented restriction concerns that particular tool. A successful Google rendering test alone leaves another service's rendering behavior unverified.
How can a website check and reduce rendering dependencies?
Google's JavaScript troubleshooting guide recommends the Rich Results Test or Search Console's URL Inspection Tool to examine how Google crawls and renders a URL. Available diagnostics include loaded resources, JavaScript console output and exceptions, and the rendered document structure. Comparing the expected page text with this output helps locate missing content.
Server-side rendering produces page content on the server; the initial HTML can then contain the actual page text. Google's rendering guidance recommends this approach for JavaScript-generated content. It addresses the application-shell dependency described above.
Related terms
FAQ
Should you remove JavaScript from your website?
Google's rendering guidance recommends server-side rendering for JavaScript-generated content. You can review how the page supplies its main text before deciding which rendering approach to use.
How can you inspect what Google renders?
Use the Rich Results Test or URL Inspection Tool described in Google's troubleshooting guide. You can inspect the rendered content and JavaScript errors to check whether the expected text appears.
Sources
- Google Search Central, "Understand the JavaScript SEO basics", updated 4 March 2026
- Google Search Central, "AI features and your website", updated 10 December 2025
- Anthropic, "Web fetch tool", accessed 17 October 2026
- Google Search Central, "Fix Search-related JavaScript problems", updated 18 December 2025
- Google Search Central, "Dynamic rendering as a workaround", updated 10 December 2025
Check how a page reads to answer engines. Open the GEO score analyzer