Rendering
Quick Definition
Rendering in SEO is the process by which a search engine executes JavaScript and builds the visual layout of a web page. Google uses a two-phase indexing system where pages are first crawled, then rendered.
Why It Matters
Google uses a two-phase indexing system: first it crawls your HTML, then it queues pages for rendering (executing JavaScript). Pages that depend on JavaScript rendering may wait hours or days in Google's render queue before being fully indexed. Understanding rendering helps you ensure critical content is visible without JavaScript execution.
Real-World Example
A React single-page application sends only a nearly empty HTML shell to the browser (and Googlebot). All content is loaded via JavaScript after the page renders. Googlebot crawls the empty shell first, then may take days to render the JavaScript and see the actual content. During that delay, the page has no content in Google's index.
Signal Connection
Presence -- Content that requires rendering to become visible faces delayed indexing. Pages with content available in the initial HTML response achieve faster and more reliable search presence than JavaScript-dependent pages.
Pro Tip
Use Google Search Console's URL Inspection tool and click 'View Crawled Page' to see the rendered HTML. Compare it to what you see in your browser. If critical content like product details, prices, or article text is missing from the rendered view, you have a rendering problem.
Common Mistake
Assuming all JavaScript frameworks are equally SEO-friendly. Client-side rendering (CSR) frameworks like vanilla React or Vue require extra work for SEO, while server-side rendering (SSR) frameworks like Next.js and Nuxt send fully rendered HTML to crawlers.
Test Your Knowledge
Why does Google's two-phase indexing system affect JavaScript-heavy websites?
Show Answer
Answer: B. Because JavaScript pages are crawled first but may wait in a render queue before content is indexed
Google first crawls the raw HTML, then places JavaScript-heavy pages in a render queue for later processing. This delay means JavaScript-dependent content may not be indexed for hours or days, while content in the initial HTML is indexed immediately.