JavaScript sites: what Google actually indexes
Google documents its JavaScript processing precisely: crawl, render, index — and it is the rendered result that counts. That resolves an old myth, and creates a quieter dependency worth knowing about.
Last reviewed: 2026-09-15
Three phases, one source of truth
Supported, from Google’s current documentation: JavaScript web apps are processed in three main phases — crawling, rendering, indexing; the rendered HTML produced after JavaScript execution is what gets indexed; and Google parses that rendered HTML for links, queueing newly found URLs for crawling. So a client-rendered page can be indexed and its links can be discovered — the myth that “Google can’t do JavaScript” has been out of date for years.
The dependency it creates
Rendering is still an extra step your content must survive. One supported detail illustrates how literal the environment is: Google’s Web Rendering Service clears Local Storage and Session Storage between page loads. A page whose content only appears after client-side state, logins or storage reads may render empty for the indexer while looking fine to a returning visitor. The safest content is content that exists in HTML without ceremony.
Editory’s position: don’t take the bet
Editory-published pages are fully server-rendered and ship zero JavaScript by default — interactive blocks hydrate as small islands only where a page actually uses one, and their no-JS baseline stays complete and indexable. The rendered HTML the indexer sees is the same HTML every visitor gets, so nothing depends on the rendering phase going well.
Editory’s recommendation
If you control the stack, server-render your content. If you must client-render, verify what the indexer sees (the rendered HTML, not the source) and never gate content behind storage or session state.
Common misconceptions
“Google can’t index JavaScript sites.”
Outdated: Google documents rendering as a standard phase and indexes the rendered HTML. The real question is whether your content reliably survives that phase.
What the engine does
renderer:zero-js-ssrPublished pages are fully server-rendered and ship zero JavaScript by default; interactive blocks hydrate as per-block islands whose no-JS baseline remains complete and indexable.
Evidence
The claims behind this page, with their status in the evidence release. Click a claim for its sources.
Supported — asserted as written
Google currently describes JavaScript web-app processing as three main phases: crawling, rendering, and indexing.Supported
Claim ID: clm_95e08672-5e5f-4558-8b1c-a3624d1cbf58
Sources
- Understand the JavaScript SEO basics | Google Search Central — Google · primary source
“Google processes JavaScript web apps in three main phases: Crawling Rendering Indexing”
- SEO Guide for Web Developers | Google Search Central | Documentation | Google for Developers — Google · primary source
“To learn more about how Google handles JavaScript when crawling, rendering, and indexing, see the following video.”
- JavaScript SEO & Rendering: How Google Handles JS [2026] — SEO Kreativ
“Google describes three phases: crawling, rendering, indexing.”
- JavaScript SEO: How to Optimize JS for Search Engines — Semrush
“Google processes JS in three phases: Crawling Rendering Indexing”
Google currently states that the rendered HTML produced after JavaScript execution is used to index a page.Supported
Claim ID: clm_e5035a9c-9e17-4ba5-a925-572c1e94b904
Sources
- Understand JavaScript SEO Basics | Google Search Central — Google for Developers · primary source
“a headless Chromium renders the page and executes the JavaScript... Google also uses the rendered HTML to index the page”
- No-JavaScript fallbacks in 2026: Less critical, still necessary — Search Engine Land
“Google clearly states that JavaScript rendering doesn't necessarily happen on the initial crawl.”
- JavaScript SEO: What Google Actually Indexes After Rendering — IndexProbe
“Google executes JavaScript with a headless Chromium and indexes the result of the render.”
Google currently states that it parses rendered HTML for links and queues newly found URLs for crawling.Supported
Claim ID: clm_73cb48e9-9910-4f4d-bc35-d9770131f920
Sources
- Understand the JavaScript SEO basics | Google Search Central — Google · primary source
“Googlebot parses the rendered HTML for links again and queues the URLs it finds for crawling.”
- Google crawling documentation changelog — Google · primary source
“The content hasn't changed, only the location.”
- JavaScript links can make your pages invisible to AI search — Search Engine Land · primary source
“A hit on a division page in the JS group is only possible if the bot rendered the parent page’s JavaScript.”
- No-JavaScript fallbacks in 2026: Less critical, still necessary — Search Engine Land
“Google's documentation now gives us a much clearer picture of how JavaScript rendering actually works.”
Google currently states that Web Rendering Service clears Local Storage and Session Storage data across page loads.Supported
Claim ID: clm_ae57a94a-38b2-42fe-9ec6-03aab2b805a2
Sources
- Fix Search-related JavaScript problems | Google Search Central — Google · primary source
“WRS does not retain state across page loads: Local Storage and Session Storage data are cleared across page loads.”
- Inside Googlebot: demystifying crawling, fetching, and the bytes we process | Google Search Central Blog | Google for Developers — Google · primary source
“the WRS operates statelessly — it clears local storage and session data between requests.”
- JavaScript analysis is extremely important and anyone can do it (BrightonSEO) — SlideShare (Gaca-Tworek)
“WRS does not retain state across page loads”
Related topics
Redirects and error codes: what Googlebot does with them
HTTP status codes are one of the few places where Google documents its behavior precisely. The supported facts make migration and error handling decisions mechanical.
Core Web Vitals: real factor, modest weight
Page experience is one of the most over-optimized areas in SEO. The supported picture is refreshingly precise: Core Web Vitals matter, they guarantee nothing, and polish beyond them buys no direct ranking help.