Rendering
Rendering is the process where a browser or search engine executes JavaScript to generate the fully visual and interactive page after receiving the raw HTML.
Definition
Rendering matters to SEO because search engines must decide how much of a page's JavaScript they will execute before indexing its content. Googlebot renders pages using a modern Chromium engine, but rendering consumes crawl budget, delays indexation, and can fail silently. Pages that rely heavily on client-side JavaScript risk having key content missed if the render queue is deep or the JS errors out.
Two Waves of Indexing
Google operates a two-wave indexing system. In the first wave, Googlebot crawls the raw HTML and indexes whatever it finds. In the second wave, a headless Chromium browser renders the page, executing JavaScript. Content rendered by JS may not appear in the index for days or weeks after the initial crawl.
The JavaScript SEO Trap
Single Page Applications (SPAs) and frameworks like React, Angular, and Vue are notorious for SEO problems. If critical content or internal links are only injected via JavaScript, Google may never see them. Server-side rendering (SSR), static site generation (SSG), or hybrid rendering are essential mitigations for JavaScript-heavy sites.
Note
Key takeaways
- Rendering executes JavaScript to build the final page
- Google uses two-wave indexing: HTML first, JS later
- JavaScript-rendered content faces delayed indexing and higher failure risk
At a glance
- Engine
- Chrome (headless)
- Risk
- Delayed indexing, silent failure
- Mitigation
- SSR, SSG, or hybrid rendering
How Atomic Glue helps
Atomic Glue builds SEO strategies that turn technical fundamentals into measurable rankings. Get in touch to discuss your SEO & GEO services needs.
Get in touchUnderlined terms have their own entry. Selecting one shows it on the map below.
Atomic Glue. "Rendering." Glossary.atomicglue.co/glossary/rendering
How Rendering connects
Rendering is the process where a browser or search engine executes JavaScript to generate the fully visual and interactive page after receiving the raw HTML.
Definition
Rendering matters to SEO because search engines must decide how much of a page's JavaScript they will execute before indexing its content. Googlebot renders pages using a modern Chromium engine, but rendering consumes crawl budget, delays indexation, and can fail silently. Pages that rely heavily on client-side JavaScript risk having key content missed if the render queue is deep or the JS errors out.
Two Waves of Indexing
Google operates a two-wave indexing system. In the first wave, Googlebot crawls the raw HTML and indexes whatever it finds. In the second wave, a headless Chromium browser renders the page, executing JavaScript. Content rendered by JS may not appear in the index for days or weeks after the initial crawl.
The JavaScript SEO Trap
Single Page Applications (SPAs) and frameworks like React, Angular, and Vue are notorious for SEO problems. If critical content or internal links are only injected via JavaScript, Google may never see them. Server-side rendering (SSR), static site generation (SSG), or hybrid rendering are essential mitigations for JavaScript-heavy sites.
Note
Most common misconception: 'Google can render JavaScript so I don't need to worry about it.' Google can render JS, but the process is delayed, resource-constrained, and error-prone compared to server-rendered HTML. Critical content must be in the initial HTML response whenever possible.
Key takeaways:
Rendering executes JavaScript to build the final page
Google uses two-wave indexing: HTML first, JS later
JavaScript-rendered content faces delayed indexing and higher failure risk