started · updated
Googlebot technical processes for JavaScript crawling and rendering
Googlebot utilizes a three-stage process to handle JavaScript-heavy websites: crawling the URL to read raw HTML, rendering the page using a headless Chromium-based Web Rendering Service (WRS), and finally indexing the rendered HTML. This distinction is critical because the content indexed is the result of JavaScript execution rather than the initial server-sent HTML.
Several factors can prevent rendering, including robots.txt disallow rules, non-200 HTTP status codes, or blocked JavaScript files. Notably, a 'noindex' tag present in the raw HTML will stop the rendering process entirely, meaning JavaScript cannot be used to remove a 'noindex' instruction.
Modern technical SEO also requires optimizing for Core Web Vitals, specifically Interaction to Next Paint (INP). INP measures the latency of user interactions through input delay, processing time, and presentation delay. Common performance bottlenecks include long tasks on the main thread, forced synchronous layouts, and hydration issues in Server-Side Rendering (SSR) frameworks.