Search and SEO
What is Rendering?
Rendering is the step where a crawler executes a page’s JavaScript to see the final content. Google renders on a deferred queue with no guarantee of completeness, and most other crawlers — including every major AI crawler — do not render at all.
Also called: JavaScript rendering · client-side rendering
The one test that settles it
View the page source, not the Elements panel. DevTools shows the DOM after JavaScript has run; view-source shows what the server sent, which is what a non-rendering consumer receives. If the body is an empty container, your content does not exist until execution.
What each approach costs
| Mode | Googlebot | AI crawlers |
|---|---|---|
| Client-side only | Rendered, deferred, never guaranteed | Sees nothing |
| Server-side rendered | Full content on first fetch | Full content |
| Static generation | Full content on first fetch | Full content |
Why it matters more than it used to
"Google renders it eventually" was a defensible position when Google was the only consumer that mattered. When a buyer pastes your URL into an assistant and asks whether you are any good, that fetch does not render, and an empty response is the answer they get.
Where this is covered in depth
A definition can only go so far. JavaScript SEO: the difference between what you see and what gets indexed covers this properly — 3 minutes, free, no email required.
Who wrote this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan. These definitions come from client work rather than from a content brief — where an entry describes a mistake, it is usually one found on a real site. More about how I work.