robots.txt and evergreen Googlebot
Googlebot runs an "evergreen" rendering engine — a regularly updated Chromium — so it can execute modern JavaScript and CSS. This raises the stakes for robots.txt: an evergreen renderer that supports your framework still cannot use resources you disallow. This page explains the implications for robots.txt on JavaScript-heavy sites.
What 'evergreen Googlebot' means
Historically Googlebot rendered with an older Chrome version, which lagged modern web features. Google moved Googlebot to an evergreen model: its rendering engine tracks recent stable Chromium, so newly shipped JavaScript and CSS features are generally supported soon after they reach Chrome.
This means modern frameworks render well in Googlebot — provided the renderer can actually fetch the code. An up-to-date engine does not help if robots.txt disallows the bundles, stylesheets, or data endpoints the page depends on.
- Googlebot's renderer tracks recent stable Chromium (evergreen)
- Modern JS/CSS features are generally supported
- Capability does not override a robots.txt block on resources
robots.txt implications
Because the renderer is capable, the common failure mode shifts from "the engine is too old" to "the engine could not fetch what it needed." Keep render-critical JavaScript, CSS, fonts, and data endpoints crawlable so the evergreen renderer can build the full page.
Do not rely on the evergreen engine to compensate for blocked resources, slow responses, or content that only appears after user interaction the renderer does not perform. Verify with URL Inspection that the rendered page is complete and no required resource is blocked by robots.txt.
How it appears in analytics and logs
If a modern JS page indexes incompletely despite Googlebot's evergreen renderer, the cause is usually blocked resources or crawl issues — not an outdated rendering engine.
Diagnostic use case
Understand that an evergreen Googlebot can render modern JS, so the limiting factor becomes whether robots.txt lets it fetch the resources, not browser capability.
What WebmasterID can help detect
WebmasterID records which resources Googlebot requests, so you can confirm the evergreen renderer is reaching the JS and CSS your framework needs rather than hitting a robots.txt wall.
Common mistakes
- Assuming an evergreen renderer can index content whose resources are robots.txt-blocked.
- Blaming an old rendering engine when the real cause is blocked or slow resources.
- Relying on interactions the renderer does not perform to reveal content.
Privacy and accuracy notes
This topic concerns Googlebot's rendering engine and resource crawling, not visitors. No personal data is involved in robots.txt or rendering decisions.
Related pages
- robots.txt and page rendering
Google indexes the rendered version of a page, fetched in a second pass by its Web Rendering Service. robots.txt rules that block render-critical resources cause the renderer to skip them, producing an incomplete rendered DOM. This page explains the rendering pipeline and how robots.txt interacts with it.
- robots.txt and JavaScript/CSS files
Google renders pages with a headless browser before indexing, so it must fetch the JavaScript and CSS your page depends on. Disallowing those resources in robots.txt can prevent proper rendering and harm how the page is understood. This page explains why render-critical resources should stay crawlable.
- robots.txt and AMP pages
AMP pages depend on the AMP runtime, cached resources, and a crawlable canonical relationship. Disallowing AMP paths or required resources in robots.txt can break validation, caching, or discovery. This page explains which AMP-related resources must stay crawlable and how robots.txt interacts with AMP.
- Web crawler reference
How Googlebot and other crawlers identify themselves.
Sources and verification notes
- Google — Googlebot and the evergreen rendering engineGooglebot uses an evergreen Chromium-based rendering engine.
- Google — JavaScript SEO basics (rendering)Rendering supports modern features but still fetches resources subject to robots.txt.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.