Term
JavaScript Rendering by Googlebot
Googlebot renders JavaScript pages in two stages — first an HTML crawl, then rendering via the Web Rendering Service (Chromium-based). The delay can hold up indexing of client-rendered content.
JavaScript Rendering by Googlebot — explained in more detail
For JavaScript pages, Googlebot operates in two phases. Phase 1 fetches the initial HTML and queues the page for rendering. Phase 2 hands the page to the Web Rendering Service (WRS), a modern Chromium instance that executes JavaScript, mutates the DOM, and indexes the final rendered HTML. The delay between phases is typically seconds to minutes today; years ago it could be days.
WRS behaves like a modern headless browser: it runs almost any JavaScript, but it has no cookie memory between requests, won’t bypass noindex/login walls, and never simulates user input.
Example / In practice
A React SPA that loads all content client-side appears to the first crawl as an empty <div id="root">. Only after WRS rendering does Google see the actual content. The fix: SSR or SSG (e.g. Next.js, Astro) ships full HTML immediately — indexing without render lag.
Distinction from similar terms
Dynamic rendering was an old workaround (user-agent-based SSR for bots only) — Google now considers it deprecated. Hydration is a client-side concern about mounting interactive logic; it doesn’t affect crawling itself.
Entdecke mehr
Hydration
The process by which static HTML rendered on the server is retroactively given JavaScript interactivity in the browser — turning "dead" markup into a reactive app.
LexikonTechnical SEO — what Google actually has to crawl, render and index
How crawl budget, robots, sitemap, JS rendering, indexing, canonical and Core Web Vitals fit together — the full arc for production sites.
NewsGoogle Search Central Live Toronto 2026 — what Google officially said about the future of search
Information Gain as the new guideline, Google-Extended clarified, AI Mode with 93% zero-click. The key statements from Toronto.