The Web Rendering Service is the Googlebot component that runs a page's JavaScript in a headless, evergreen version of Chromium so Google can index the rendered HTML. Google confirms it by name in its JavaScript documentation and announced the evergreen Chromium change in May 2019. It is infrastructure, not a ranking system. For a site, it means content injected by JavaScript can be indexed, but only if rendering succeeds, resources are crawlable, and the WRS is not served stale cached scripts.
What is the Web Rendering Service?
The Web Rendering Service (WRS) is the part of Googlebot that loads a crawled page in a browser engine, runs its JavaScript and produces the rendered HTML Google indexes. Google names it in its JavaScript troubleshooting documentation.
Since 7 May 2019 Googlebot has used an evergreen Chromium engine, updated regularly, instead of an older fixed version. At announcement it was Chromium 74.
Googlebot and its Web Rendering Service (WRS) component continuously analyze and identify resources that don't contribute to essential page content and may not fetch such resources.
Google, Fix Search-related JavaScript problems, Google Search Central
How does Google render pages?
Google describes three phases in its JavaScript SEO basics: crawling, rendering and indexing. Googlebot fetches the URL (if robots.txt allows), queues pages with a 200 status for rendering whether or not they use JavaScript, and when resources allow, a headless Chromium renders the page. Google parses the rendered HTML for links and uses it for indexing.
The WRS behaves differently from a user's browser in ways that matter. Google's documentation says it does not keep state across page loads (local storage, session storage and cookies are cleared), may ignore caching headers, and may skip resources it judges non-essential, such as reporting requests.
- Rendering can wait in a queue; Google says for a few seconds, but it can take longer.
- Blocked JavaScript or CSS files are not rendered.
- With a noindex in the original HTML, Google may skip rendering, so JavaScript cannot reliably remove it.
- Google won't load content that needs swiping, clicking or typing to appear.
Once Google's resources allow, a headless Chromium renders the page and executes the JavaScript.
Google, Understand the JavaScript SEO basics, Google Search Central
What evidence is there that Google uses the Web Rendering Service?
The evidence label is Confirmed. Google names the WRS in its documentation, describes its behaviour, and announced the evergreen Chromium change on its Search Central blog. Google's How Search works guide also states that Google renders pages using a recent version of Chrome.
What Google does not publish is the rendering timeout or how long pages wait in the render queue, so claims of a fixed number of seconds are not Google figures.
Googlebot now runs the latest Chromium rendering engine (74 at the time of this post) when rendering pages for Search.
Martin Splitt, Google, The new evergreen Googlebot, Google Search Central Blog
What should a site do about the Web Rendering Service?
Put primary content and links in the server HTML where possible, and make sure the rendered HTML in Search Console's URL Inspection tool contains everything that must be indexed. Where JavaScript is required, keep scripts crawlable, error-free and fingerprinted.
Fingerprinting matters because Google says the WRS may ignore caching headers and use outdated JavaScript or CSS. A file name that changes with its content (for example app.3f9a2c.js) forces a fresh fetch. The falsifiable test: deploy a content change that depends on a new script version, then check the rendered HTML in URL Inspection; if the old output appears, the WRS used a stale file.
WRS may ignore caching headers. This may lead WRS to use outdated JavaScript or CSS resources.
Google, Understand the JavaScript SEO basics, Google Search Central
Which Laurelin audit checks test for the Web Rendering Service?
The new check JavaScript and CSS served without content fingerprinting tests the stale-resource risk Google documents for the WRS. It inspects the site's asset URLs; the WRS itself is Google infrastructure and cannot be observed directly.
Related existing checks: Primary content only present after JavaScript: content that exists only if rendering succeeds. Large raw versus rendered text gap: how much of the page depends on the WRS. JavaScript errors halting render: script errors that stop rendering. Blocked JS or CSS preventing render: resources the WRS is not allowed to fetch. Render timeout exceeds budget: pages slow enough to risk incomplete renders. Hydration mismatch between server and client DOM: server and client HTML that disagree.
What are the key dates for Google Web Rendering Service?
- 2019-05-07: Google announces evergreen Googlebot running Chromium 74 (source)
Frequently asked questions about Google Web Rendering Service
Does Google render JavaScript?
Yes. Google says Googlebot queues pages for rendering and a headless, evergreen version of Chromium executes the JavaScript before the rendered HTML is used for indexing.
Which Chrome version does Googlebot use?
Google says Googlebot runs an evergreen Chromium that it updates regularly. It was version 74 when Google announced the change in May 2019.
Why does Google show an old version of my JavaScript output?
Google says the Web Rendering Service may ignore caching headers and use outdated JavaScript or CSS. Content fingerprinting in file names avoids this.