Rendering is the stage at which a browser or search engine executes HTML, CSS and JavaScript to produce the finished page. For search engines it sits between crawling and indexing.
Google renders using an evergreen Chromium engine, but does so in a second pass separate from the initial crawl, and that pass may be queued for hours or days. The rendered HTML — not the raw source — is what gets indexed, which is why inspecting the raw source alone can be misleading.
Rendering is where many modern SEO problems originate. Content injected by JavaScript may be indexed late or, if the script fails or times out, not at all. Resources blocked in robots.txt cannot be fetched during rendering, so a page may render very differently for Googlebot than for a user.
Compare the rendered HTML in Search Console's URL Inspection tool against your raw source to see what Google actually receives. Ensure CSS and JavaScript required for rendering are not blocked in robots.txt, and prefer server-side rendering for content that must be indexed reliably.
Want to learn more? Explore our SEO Glossary or check out our expert guides on SEO strategies.