What Is Dynamic Rendering?

• Client-side rendering (CSR) means your website’s JavaScript loads extra content after the initial HTML loads in the browser.
  
• Google Search can see this JavaScript-generated content but has some limitations—some content might not appear in the rendered HTML Google indexes.
  
• Other search engines might not run JavaScript at all, so they won’t see content generated by JavaScript.
  

Dynamic rendering is a workaround for these issues: #

• Your server detects when a crawler (like Googlebot) with limited or no JavaScript support requests a page.
  
• Instead of serving the normal JavaScript-heavy page, your server sends a pre-rendered static HTML version of the content to that crawler.
  
• Regular users still get the full JavaScript-powered client-side experience.
  

When Should You Use Dynamic Rendering? #

• When your site’s content changes frequently and
  
• When the JavaScript used is complex or uses features that crawlers don’t support well.
  
• When you want to ensure all crawlers can see your content even if they don’t fully run JavaScript.
  

Note:
Dynamic rendering adds extra server and maintenance overhead, so it’s not the preferred or long-term solution.

How Does Dynamic Rendering Work? #

1. User or crawler makes a request to your website.
   
2. Your server checks if the request is from a bot that might have trouble with JavaScript (by inspecting the user-agent or other signals).
   
3. For such bots, your server routes the request to a rendering server that executes the JavaScript and generates static HTML.
   
4. The crawler receives the static HTML version (easier to crawl and index).
   
5. Regular users get the usual JavaScript version.

Is Dynamic Rendering Cloaking? #

• No, as long as the content served to crawlers and users is substantially the same.
  
• Google considers it cloaking only if you serve completely different content to users vs crawlers (e.g., cats content to users and dogs content to crawlers).

Summary #