OOmnistu

Blog / SEO & Technical

SEO & Technical

JavaScript sites and Google Search: crawl, render, index

Understand how Google crawls, renders and indexes JavaScript sites and what to check when important content depends on browser code.

OOmnistu
Reviewed 2026-11-16 · 3 min read

If your app renders content in the browser with JavaScript, Google's documentation on JavaScript SEO basics explains what happens to it. We read the whole page on 15 November 2026. The guides it links to (lazy-loading, troubleshooting, long-lived caching) were not read.

The three phases

Google processes JavaScript web apps in three phases: crawling, rendering and indexing.

  1. Googlebot takes a URL from the crawl queue and checks robots.txt. If the URL is disallowed, it skips the request, and Google Search will not render it.
  2. It parses the HTML response for links in href attributes and queues them.
  3. Pages with a 200 status are queued for rendering unless a robots meta tag or header says not to index. The page may wait seconds or longer. A headless Chromium then runs the JavaScript, and Google parses the rendered HTML for links and content.

Per the page, pages with non-200 status, such as a 404, may skip rendering. In the app shell model, the first HTML has no content and Google needs rendering to see it.

Practices from the page

Questions for your app

Limits

One page, read in full, but not the guides it links to. We make no claims about how long rendering takes beyond the page's wording, and none about traffic effects.

By Omnistu.

Sources

Previous
Image SEO: how Google finds, picks and describes your images