Rendering in SEO refers to the process by which a browser - or Googlebot - executes a web page's code to produce the final visual output. For plain HTML pages, rendering is instant: the HTML is the content. But for pages built with JavaScript frameworks like React, Vue, or Angular, the HTML delivered to the browser is often just a bare shell. The actual content is generated by JavaScript running in the browser after the initial page load. Googlebot must run that JavaScript to see the full content - and this two-step process has significant implications for indexing and rankings.

Google's crawlers process pages in two waves. The first wave fetches the raw HTML immediately. The second wave renders the JavaScript - but this second wave can be delayed by days or even weeks, depending on Google's rendering queue. Any content that only appears after JavaScript execution may not be indexed for a long time. This is a critical consideration for JavaScript-heavy single-page applications (SPAs) where the entire page content is client-side rendered.

Client-Side vs. Server-Side Rendering

Rendering Approaches for SEO Server-Side (SSR) HTML built on server Google sees full content immediately on crawl Best for SEO Next.js SSR, WordPress, static HTML sites Client-Side (CSR) JS runs in browser Google sees empty shell until render queue runs Risky for SEO React SPA, Vue SPA without hydration SSG / Hybrid Pre-built at deploy time Static HTML delivered JS enhances after load Ideal for SEO Next.js SSG, Gatsby, Astro, Hugo
Test with Google's URL Inspection Tool: In Google Search Console, the URL Inspection tool shows you both the crawled HTML and the rendered HTML for any page. If content appears in the rendered version but not the crawled version, that content is at risk of not being indexed.

How Rendering Affects Indexing

Because Google prioritizes fast crawling over rendering, content hidden behind client-side JavaScript is effectively invisible until Googlebot processes the rendering queue. This means critical SEO elements - your H1, body text, internal links, and structured data - should never depend solely on JavaScript to render. For technical SEO audits of JavaScript-heavy sites, the key questions are: Does critical content appear in the raw HTML? Are internal links present in the initial HTML? Is structured data rendered in the first pass or the second? Tools like Chrome's View Source, Screaming Frog's JavaScript rendering mode, and Google's Rich Results Test all help diagnose rendering issues before they affect page performance and indexing.