Discussion starter: a technical SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- Crawling
- Indexing
- Technical SEO
Can you still measure a delay between Google crawling a JS page and indexing its rendered content in 2026, or is the rendering queue worry outdated?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
adminAdmin
You can still measure it, and it is worth doing once on your own stack, but for most sites the rendering queue is no longer the bottleneck people feared in 2018. Google has said for years that the “two waves of indexing” picture was an oversimplification, and public measurements since then suggest Google renders the vast majority of pages it crawls, usually within seconds or minutes, with a long tail that can stretch to hours. The JavaScript problems that still hurt sites in 2026 are different ones: content that only appears after user interaction, rendering that fails or times out, links that are not real anchor elements, noindex handling, and non-200 responses. And for AI crawlers, many of which do not render JavaScript at all, server-rendered content matters more than it does for Google.
What the public evidence says
- Google’s position. Google has described rendering as happening for essentially all pages it indexes, and its JavaScript SEO documentation treats it as part of normal processing. Its December 2025 documentation update added two points that matter more than delay: pages with non-200 status codes might not be rendered, and a noindex in the original HTML can stop rendering, so removing it with JavaScript may not work.
- Independent measurement. A 2024 study by Vercel and MERJ, based on Googlebot activity on nextjs.org, found that Google rendered all the HTML pages it crawled in the sample, with most rendered within seconds to minutes and a long tail extending to hours.
- Other crawlers. Vercel’s analysis of crawler traffic across its network found that the major AI crawlers it examined did not render JavaScript, while Google’s crawler infrastructure did.
That combination is why I describe the rendering queue worry as mostly outdated for Google, while JavaScript dependence as a whole is not outdated at all.
How to measure the delay on your own site
You cannot see Google’s render timestamp directly, but you can infer it from requests that only happen during rendering.
- Create a render-only request. On a test set of pages, have the client-side code fetch a unique URL per page, such as an API endpoint with a page-specific token, that is never requested by the server-rendered HTML.
- Log verified Googlebot requests. Record the time Googlebot fetched the HTML and the time it requested the render-only URL. The difference approximates the render delay for that page.
- Watch for caching. Google’s rendering service caches resources aggressively. Make the render-only URL unique per page and per deployment so the cache does not hide the request.
- Check what was indexed. Place a unique phrase in JavaScript-rendered content and check, with URL Inspection’s indexed view rather than the live test, when it appears. This measures crawl-to-index, which includes more than rendering.
Separate three delays that get blended together:
Discovery to crawl (how long before Googlebot fetches a new URL), crawl to render (the rendering queue), and render to index (whether and when the page is added and served). Most sites that think they have a rendering problem actually have a discovery or indexing problem. Measuring the middle one on its own shows whether JavaScript is really the cause.
JavaScript problems that still cost traffic
Problem Why it matters How to check Content loaded only on click, scroll or tab change Google’s renderer does not click or scroll like a user Compare the rendered HTML in URL Inspection with what users see after interaction Links built with click handlers instead of anchor elements with hrefGoogle generally only follows anchor elements with an href Crawl with JavaScript rendering and compare discovered URLs API calls failing or timing out during render Content missing from the rendered page Check URL Inspection’s rendered HTML and resource errors; log API responses to Googlebot Noindex set in HTML and removed by JavaScript Rendering may never happen, so the noindex stands Inspect the raw HTML response, not the rendered DOM Error pages returning 200 and rendered client-side Soft 404s and wasted crawling Test missing URLs for their status codes Canonical or metadata changed by JavaScript Conflicting signals between raw and rendered HTML Compare raw and rendered head elements When the delay still matters
A short median delay does not help if your content lives in the long tail of the distribution, or changes faster than the render cycle. Cases where I would still care about render timing:
- News and live content, where hours matter and a story that is indexed late may miss its window in Top Stories.
- Prices, stock and offers that change several times a day and are injected client-side. The indexed version can lag what users see.
- Large new sections launched at once, where many pages join the render queue together and the tail gets longer.
- Heavy pages whose scripts take a long time to execute or depend on slow APIs. Google’s renderer does not wait indefinitely, so content that arrives late may not be captured at all.
In all four cases, moving the critical content into the server-rendered response removes the question entirely.
Why server rendering still matters in 2026
Even if Google’s rendering delay is short, content in the initial HTML has advantages. It is available to crawlers that do not render, including several AI crawlers that feed assistants. It removes a failure point, since rendering can fail on some requests. It is faster for users on slow devices. And it makes debugging easier, because what the server sends is what gets indexed. For product data, prices, main copy, internal links and structured data, I would still put everything in the server-rendered HTML and use JavaScript to enhance, not to supply.
Hypothetical example:
A publisher’s single-page app shows new articles in search a day or two after publication, and the team blames the rendering queue. Logs show Googlebot fetching the HTML of new articles several hours after publication, and the render-only API calls following within a minute. The delay is in discovery, not rendering: new articles are linked only from a JavaScript-rendered homepage module and appear in the sitemap on a nightly job. Adding them to a server-rendered “latest” list and updating the sitemap on publish cuts the delay without touching the rendering setup.
Measure the render delay once with render-only requests so you know your number, then spend the effort where problems actually are. For Google, that is usually discovery, interaction-dependent content and fragile rendering. For everyone else reading your site, including AI crawlers, it is getting the important content into the HTML in the first place.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.