Skip to content
2.18Advanced9 min

JavaScript SEO: Rendering and Indexing

Lucas Blochberger··Updated 11 June 2026
Definition

JavaScript SEO encompasses all measures that ensure search engines and AI crawlers can correctly render, index, and use JavaScript-based web content as a source.

Key Takeaways

  • ✓Googlebot renders JavaScript reliably (according to international analysis 100 percent complete renders), but with delay: median 10 seconds, 90th percentile around three hours.
  • ✓Most AI crawlers like GPTBot and ClaudeBot do NOT execute JavaScript and only see the raw HTML; SSR or SSG is therefore a prerequisite for AI visibility.
  • ✓JavaScript-heavy pages cost significantly more crawl budget: up to page 7, 313 hours compared to 36 hours for pure HTML, roughly nine times longer.
  • ✓Dynamic Rendering is considered an outdated workaround; Google no longer recommends it and points to SSR and SSG as robust standard strategies.
  • ✓Key content, internal links, canonical, meta-robots and JSON-LD must be in the initial, server-side delivered HTML, not injected via JavaScript.
  • ✓Structured data belongs server-side in the HTML: Only around 2 percent of crawls add JSON-LD via JavaScript, because server-side markup is more reliable and also readable for non-rendering crawlers.
  • ✓In the DACH region, consent management must not block indexing: The main content must be available to Googlebot independent of consent status.

JavaScript SEO is more critical than ever in 2026, as AI crawlers do not render JavaScript.

Google's JavaScript Rendering

Google renders JavaScript in a two-stage process: first, Googlebot crawls the HTML code, then the Web Rendering Service (WRS) renders the page with JavaScript. There can be a delay of hours to days between crawling and rendering. Content that is only loaded via JavaScript is not visible to Google until after rendering.

AI Crawlers and JavaScript

This is the critical point: GPTBot, ClaudeBot, and PerplexityBot do NOT render JavaScript. Content that is only rendered client-side is invisible to AI systems. Server-Side Rendering (SSR) or Static Site Generation (SSG) is mandatory for GEO visibility.

Rendering Strategies

SSR (Server-Side Rendering): The server fully renders the page and delivers finished HTML. Best practice for SEO and GEO. SSG (Static Site Generation): Pages are pre-rendered at build time. Ideal for content that changes infrequently. ISR (Incremental Static Regeneration): Combination of SSG and dynamic updates. Next.js standard. Client-Side Rendering: Only for app areas behind login. Never for public SEO-relevant content.

Dynamic Rendering: Deprecated

Dynamic Rendering (serving different versions for crawlers and users) was officially declared deprecated by Google in 2025. SSR is the recommended successor.

Data & Statistics

100 Prozent der HTML-Seiten wurden von Googlebot vollstaendig gerendert; Rendering-Verzoegerung: Median 10 Sekunden, 75. Perzentil 26 Sekunden, 90. Perzentil rund 3 Stunden (Basis: ueber 100.000 Googlebot-Abrufe, April 2024)

Vercel / MERJ - How Google Handles JavaScript Throughout the Indexing Process [international] (2024)

313 Stunden bis zur 7. Seite eines JavaScript-Ordners gegenueber 36 Stunden bei reinem HTML, rund neunmal so lange (Rendering-Queue zusaetzlich zur Crawl-Queue)

Onely Blog - Rendering Queue: Google Needs 9X More Time To Crawl JS Than HTML [international] (2022)

Desktop-Startseiten: gerenderter sichtbarer Wortzaehler im Median 400 vs. 330 Woerter im rohen HTML (17,5 Prozent Differenz); nur 2 Prozent der Mobile- und Desktop-Crawls fuegen strukturierte Daten per JavaScript hinzu

Web Almanac 2024 (HTTP Archive) - SEO Chapter [international] (2024)

GPTBot verantwortete 2025 rund 7,5 Prozent des Verified-Bot-Traffics, Googlebot 4,5 Prozent der HTML-Anfragen; Crawling fuer Modelltraining dominiert (am Spitzenwert 7-8x des Such-Crawlings)

Cloudflare Radar - 2025 Year in Review [international] (2025)

Bei einer Suche mit AI Overview klicken Nutzer in 8 Prozent der Faelle auf ein klassisches Ergebnis, ohne AI Overview in 15 Prozent; Klick auf einen Link in der KI-Zusammenfassung selbst nur in 1 Prozent (Basis: 68.879 Suchen, 900 US-Erwachsene)

Pew Research Center - Google users are less likely to click on links when an AI summary appears [international, USA] (2025)

Google haelt in Oesterreich 81,87 Prozent Suchmaschinen-Marktanteil, vor Bing mit 9,01 Prozent und DuckDuckGo mit 2,75 Prozent (Mai 2026)

StatCounter Global Stats - Search Engine Market Share Austria [Oesterreich] (2026)

8,69 Millionen Internetnutzer in Oesterreich bei 95,3 Prozent Online-Penetration (Anfang 2025)

DataReportal - Digital 2025: Austria [Oesterreich] (2025)

2023 setzten 31 Prozent der oesterreichischen Unternehmen auf E-Commerce, im Dienstleistungsbereich 35 Prozent (Produktion 22 Prozent)

Statistik Austria - 31 % der Unternehmen setzen auf E-Commerce (IKT-Einsatz in Unternehmen) [Oesterreich] (2024)

FAQ

Can Google render and index JavaScript?
Yes. An international analysis by Vercel and MERJ based on over 100,000 Googlebot requests showed that 100 percent of HTML pages were fully rendered, including asynchronously loaded content and modern frameworks like Next.js. However, rendering happens with delay: median after 10 seconds, 90th percentile only after around three hours. Google renders reliably, but with delay and higher crawl effort than with pure HTML.
Do AI crawlers like GPTBot and ClaudeBot render JavaScript?
Generally no. Most AI crawlers only process the raw HTML of a page and do not execute JavaScript. Content that is exclusively generated client-side via JavaScript does not exist for these systems and therefore cannot be used as a source in AI responses. Anyone who wants to be visible in generative search must provide their content server-side in HTML, i.e. via Server-Side Rendering (SSR) or Static Site Generation (SSG).
What is the difference between CSR, SSR and SSG for SEO?
With Client-Side Rendering (CSR), the server delivers nearly empty HTML, the browser builds the page via JavaScript, so content appears with delay. With Server-Side Rendering (SSR), the server renders the complete HTML per request, crawlers see the content immediately. With Static Site Generation (SSG), the HTML is generated in advance at build time, resulting in maximum speed and immediately indexable HTML. For SEO and AI visibility, SSR and SSG are the robust options because the content is already in the initial HTML.
Why is Dynamic Rendering no longer recommended?
Dynamic Rendering was a workaround where crawlers received a pre-rendered HTML variant and users the JavaScript version. Google now classifies this approach as outdated and no longer recommends it, because it creates additional maintenance overhead and carries the risk that crawlers and users receive different content. Instead, Google points to Server-Side Rendering and Static Site Generation as sustainable standard solutions.
Should structured data (JSON-LD) be delivered server-side or via JavaScript?
Server-side. According to Web Almanac 2024, only around 2 percent of crawls add structured data via JavaScript, the vast majority delivers it in the raw HTML. The reason: Server-side delivered JSON-LD is immediately available, independent of the rendering queue and also readable for crawlers that do not execute JavaScript. For reliable Rich Results and for discoverability by AI systems, JSON-LD therefore belongs in the initial HTML.
How do I check if my JavaScript content is being indexed?
Via URL Inspection in Google Search Console, you can view the HTML actually rendered by Google for a URL and compare it with the raw source code. Large discrepancies indicate rendering-dependent content. Additionally, the Rich Results Test checks structured data, Lighthouse and CrUX check Core Web Vitals, and a log file analysis shows how often and with what delay Googlebot renders the pages. It is important that key content, canonical and meta-robots are also contained in the rendered result.
Does a consent banner affect indexing in the DACH region?
It can, if the main content only becomes visible after consent. Googlebot does not accept cookies and does not click away consent banners, so it does not see content that is behind consent. The actual page content must therefore be available server-side independent of consent status, while optional tracking and marketing scripts must not block the rendering of the main content. This keeps GDPR compliance and indexability compatible with each other.

Related Articles

How does your website perform?

Get a free, AI-powered SEO report of your website by email: technical SEO, on-page, keywords & competitors. No obligation.

Get a free SEO audit →
Previous← XML Sitemaps: Best Practices for Large WebsitesNextEdge SEO: CDN-Level Optimization with Cloudflare Workers →