dynamic rendering
Also called: prerender for bots, bot prerendering, crawler prerendering
Dynamic rendering serves prerendered static HTML to search engine crawlers while sending users the normal JavaScript version of the same page. Google now calls it a legacy workaround, not a long-term solution, and recommends server-side or static rendering instead.
Dynamic rendering sits between your app and the web. A middleware layer inspects the incoming request’s user agent. If it looks like Googlebot, Bingbot, or an AI crawler, the request is routed to a headless-browser renderer (tools like Rendertron or a prerender service) that runs your JavaScript and returns finished HTML. A human visitor hitting the same URL gets the untouched client-side app.
The point was to feed content to crawlers that historically struggled to execute JavaScript, without rebuilding the front end. Google was always careful to note this is a stopgap, and in August 2022 it added a warning bar to its docs stating dynamic rendering “is a workaround and not a long-term solution,” then later stripped out the how-to sections entirely.
Why Google backed away
Two reasons. First, Googlebot renders JavaScript reliably now, so the original problem mostly went away. Second, dynamic rendering adds real cost: an extra rendering service, cache invalidation, and two code paths that can drift apart. If the bot version and the user version diverge in substance, you cross into cloaking territory, a policy violation Google can penalize.
Google’s recommended replacements are server-side rendering (SSR), static rendering (SSG), or hydration, where the same HTML reaches everyone.
Request → UA check → bot? → renderer → static HTML → crawler
└─ no → JS bundle → browserIf you already run dynamic rendering, it is not an emergency, but treat it as tech debt to migrate off, not a pattern to build new.
How it affects your traffic
If crawlers get a stale or thin prerendered snapshot while users see a richer live page, your indexed content, and what AI engines quote, is only as good as that snapshot. Two divergent code paths are exactly where indexation silently breaks: a renderer timeout ships blank HTML, or the bot version drifts far enough from the user version to read as cloaking. A Technical SEO audit checks what Googlebot and AI crawlers actually receive versus what users get, catches rendering gaps before they cost rankings, and maps a clean path to SSR or static rendering so you stop paying for a fragile workaround.
Get Technical SEO that moves the needle
We turn terms like this into ranked pages and qualified pipeline. Start with a free Initial SEO Strategy.