Dynamic Rendering

Dynamic rendering is the process of serving content based on the user agent that calls it. This means serving a client-side rendered version of your site for human users and a separate, server-side version for search engines.

Dynamic rendering is good for indexable, public JavaScript-generated content that changes rapidly, or content that uses JavaScript features that aren't supported by the crawlers you care about. Not all sites need to use dynamic rendering, and it's worth noting that dynamic rendering is a workaround for crawlers.

Dynamic rendering requires your web server to detect crawlers (for example, by checking the user agent). Requests from crawlers are routed to a renderer, requests from users are served normally. Where needed, the dynamic renderer serves a version of the content that's suitable to the crawler, for example, it may serve a static HTML version. You can choose to enable the dynamic renderer for all pages or on a per-page basis.

Dynamic rendering is a hybrid of client-side and server-side rendering.

How Dynamic Rendering works

When a search engine bot tries to access a page, the website sends over a fully-rendered page. But when a human tries to access a page, their browser has to render the page.

This Google-approved rendering option is preferred by many because:

• It is cheaper and easier to implement than server-side rendering
• Solves speed-related crawl budget issues
• Solves partial indexing issues
• Lets human visitors enjoy the interactivity that JavaScript provides