rendering queue
Also called: render queue, two-wave indexing
The rendering queue is the deferred second stage of Google's indexing pipeline where pages that need JavaScript wait for the Web Rendering Service, a headless Chromium, to execute their scripts before the rendered content can be indexed.
Google processes a JavaScript page in three phases: crawl, render, index. When Googlebot fetches a URL and gets a 200 status, it queues the page for rendering, whether or not the page actually uses JavaScript. Google reads the raw HTML first. Anything that only appears after scripts run has to wait until Google’s resources free up and a headless Chromium (the Web Rendering Service) executes the JavaScript. Only then can the rendered content be indexed.
Why the delay matters
Older Google talks framed this as “two waves of indexing”: raw HTML first, rendered content later. Google’s Martin Splitt has since called that an oversimplification, and the current docs just describe render as a deferred pass that runs “once Google’s resources allow.” The queue is real but usually short. A Vercel and MERJ study of 37,000+ URL pairs (April 2024) found a median render delay near 10 seconds and 26 seconds at the 75th percentile, but a long tail: roughly 3 hours at the 90th percentile, and worse for URLs carrying query strings.
The practical read: content locked behind client-side rendering is invisible to Google until that second pass lands, and the wait is unpredictable. Server-side rendering or static generation puts your critical text, links, and canonical tags in the first HTML response, so nothing important depends on the queue.
How it affects your traffic
If your titles, body copy, internal links, or canonical tags only exist after JavaScript runs, Google can crawl and provisionally index a thin version of the page, then leave the real content sitting in the rendering queue. On large or slow sites that gap slows how fast new pages get discovered and can suppress rankings for content Google has not rendered yet. A Technical SEO engagement compares what Googlebot sees in raw HTML versus the rendered DOM, moves must-have content and links server-side, and closes that render gap so pages index on the first pass.
Get Technical SEO that moves the needle
We turn terms like this into ranked pages and qualified pipeline. Start with a free Initial SEO Strategy.