What is Rendering?
Rendering is the process of turning a page's code, including HTML, CSS and JavaScript, into the final content and layout that users and search engines see.
With server side rendering, the server sends ready built HTML. With client side rendering, the browser runs JavaScript to build the content after loading. Static generation and hybrid methods sit in between.
Google can render JavaScript, but it takes extra resources and can be delayed. Content that only appears after user actions, or depends on blocked scripts, may never be seen.
How Google renders pages
- 1Googlebot fetches the HTML of the page.
- 2It queues the page for rendering in an evergreen version of Chromium.
- 3The rendering service runs JavaScript and builds the final page.
- 4Google reads the rendered content and links for indexing.
- 5Links found in the rendered page are added to the crawl queue.
Rendering methods compared
| Method | How it works | SEO risk |
|---|---|---|
| Server side rendering (SSR) | Server sends fully built HTML | Low |
| Static site generation (SSG) | Pages built ahead of time | Low |
| Client side rendering (CSR) | Browser builds content with JavaScript | Higher, content may be missed or delayed |
| Hybrid and hydration | HTML sent first, JavaScript adds interactivity | Low when core content is in HTML |
| Dynamic rendering | Different HTML for bots | A workaround Google no longer recommends |
How to check rendering issues
URL Inspection tool
View the rendered HTML and screenshot Google sees.
Compare source vs rendered
Check that headings, copy and links exist in the rendered version.
Do not block resources
Robots.txt must allow CSS and JavaScript files.
Use real links
Use a tags with href, not click handlers, for navigation.
Rendering mistakes to avoid
Key content only after user clicks
Content that appears only after a click may not be rendered for indexing.
Blocked JavaScript files
Blocking scripts in robots.txt prevents Google from rendering the page properly.
Slow client side rendering
Very slow scripts can delay or prevent content from being seen.
Rendering and crawl budget
Rendering JavaScript takes more resources than reading plain HTML. Google crawls the HTML first, then queues pages for rendering, and on large sites the rendering step can lag behind crawling. Content and links that only appear after JavaScript runs may be discovered later or missed if rendering fails.
Sites with thousands of pages should serve important content, links and metadata in the initial HTML wherever possible. Server side rendering or static generation removes the dependency on Google's rendering queue and also helps other crawlers that render JavaScript poorly.
Rendering problems to check
Missing content in the HTML
Use view source or a crawler with JavaScript disabled to see what appears before rendering.
Blocked resources
Scripts or CSS blocked in robots.txt can stop pages rendering properly for Google.
Lazy loaded text
Content that loads only on scroll or click may not be rendered. Load key text without user interaction.
Client side redirects and metadata
Titles, canonicals and redirects set only with JavaScript can be applied late or ignored.
Rendering test steps
- 1Inspect the URL in Search Console and view the rendered HTML.
- 2Compare it with the raw HTML from view source.
- 3Check that main content, links and metadata appear in both.
- 4Crawl the site with JavaScript rendering on and off.
- 5Fix gaps by moving key content into server rendered HTML.
Rendering for AI crawlers
Many AI crawlers and some search engines render JavaScript poorly or not at all. Content that depends on client side scripts may be invisible to them, which means it cannot be used in AI answers. Server rendered HTML keeps your content readable to the widest range of crawlers.
Why Rendering matters for SEO
If search engines cannot render your content, they cannot index or rank it. Many JavaScript heavy sites lose rankings this way.
Rendering also affects speed. Heavy client side rendering often slows Largest Contentful Paint and Interaction to Next Paint.
How Rendering works
There are three main rendering approaches.
Server side rendering
The server builds HTML for each request, so content is visible immediately.
Static generation
Pages are built ahead of time and served as fast static files.
Client side rendering
The browser builds the page with JavaScript, which is slower for search engines.
A React based property site shows listings only after JavaScript runs. Google indexes empty templates for many pages. Switching key pages to server side rendering gets listings indexed and ranking within weeks.
Rendering checklist
- ✓Use server side rendering or static generation for key pages
- ✓Test pages with the URL Inspection tool
- ✓Do not block JavaScript or CSS in robots.txt
- ✓Put important content in the initial HTML
- ✓Use real links with href attributes
- ✓Keep JavaScript bundles small
Common Rendering mistakes
Content behind clicks
Content loaded only after user actions may not be indexed.
Links without href
JavaScript only links can stop crawlers following them.
Blocking scripts
Blocked files stop proper rendering.
Heavy bundles
Large scripts slow rendering and hurt Core Web Vitals.
Related SEO terms
Rendering FAQs
What is rendering in SEO?
+
The process of turning page code into visible content for users and search engines.
Is server side rendering better for SEO?
+
Usually, because content is visible immediately.
What is dynamic rendering?
+
Serving pre rendered pages to bots and normal pages to users, now considered a workaround.
Does rendering affect Core Web Vitals?
+
Yes. Heavy client side rendering can delay the main content and increase interaction delays, which can hurt Largest Contentful Paint and Interaction to Next Paint scores.
What is hydration in rendering?
+
Hydration is when JavaScript takes over a server rendered page to make it interactive. Done well, users and crawlers see content immediately while interactivity loads after.
Can Google render JavaScript?
+
Yes, but it can be delayed and some content may be missed.
How do I test rendering?
+
Use URL Inspection in Search Console to view the rendered HTML.
Do AI crawlers render JavaScript?
+
Many do not, so server rendered content is safer for AI visibility.
Is client side rendering always bad for SEO?
+
Not always. Google can render many JavaScript sites, but client side rendering adds risk and delay. For content that needs to rank, server rendering or static pages are safer.
Does rendering matter for small websites?
+
Most small sites built on standard CMS themes serve HTML and have few rendering issues. It matters most for JavaScript frameworks and single page apps.