Crawling IndexingJavaScript SEO

JavaScript rendering

The execution of a page's client-side JavaScript by a search engine so that content and links generated at runtime become indexable.

In full

Google renders with an evergreen Chromium and indexes the resulting DOM, but rendering is deferred, resource-limited and unforgiving: it does not click, scroll indefinitely, accept cookies, or wait for user interaction. Content behind interactions, requests blocked by robots.txt, or errors that throw during hydration simply will not be indexed. Other engines and most AI crawlers render far less reliably than Google, which is why server-rendered HTML remains the safest baseline.

Example

A site loads reviews only after a 'Show reviews' click; the reviews never appear in Google's rendered HTML, so review keywords never rank.

Related terms

Render queue

The deferred queue in which Google executes a page's JavaScript with a headless Chromium instance after the raw HTML has already been…

DOM (Document Object Model)

The in-memory tree representation of a document that the browser builds from HTML and mutates with JavaScript; the rendered DOM is what…

Server-side rendering

Generating a page's full HTML on the server for each request, so crawlers and users receive complete markup without executing JavaScript.

Hydration

Attaching client-side JavaScript behaviour to server-rendered HTML so a static page becomes interactive.

Single-page application

An architecture where one HTML shell loads and JavaScript handles all subsequent routing and content updates without full page loads.

Tools that touch this