Dynamic Rendering
In one line
Dynamic rendering is the workaround of serving regular JavaScript-rendered pages to users while sending pre-rendered HTML to crawlers — historically a stopgap, increasingly discouraged.
Going deeper
Dynamic rendering is the pattern of detecting the User-Agent, routing crawlers through a separate prerender service and serving them ready-made HTML, while users get the regular JavaScript app.
Google originally suggested it as a stopgap and has since steered teams toward SSR or static generation instead. If the two output paths drift apart, you risk being read as cloaking, and maintaining bot-specific branches is more operational overhead than it looks.
It deserves extra caution in a GEO context. Some AI crawlers barely execute JavaScript at all, so any drift between the user-facing render and the bot-facing HTML can cause incorrect content to be cited in AI answers. Consolidating on SSR is usually the safer move.
Related terms
SSR (Server-Side Rendering)
SSR (Server-Side Rendering) builds the page HTML on the server before responding, so crawlers and AI bots can read the content without having to execute JavaScript.
SEOJavaScript SEO
JavaScript SEO is the discipline of making sure JS-rendered pages get crawled and indexed correctly — usually via some combination of SSR, prerendering and hydration.
SEOCrawlability
Crawlability is how easily a search engine bot can reach and follow your site's pages — the precondition for indexing.
SEOIndexing
Indexing is the step where a search engine stores a crawled page in its database. If a page is not indexed, it cannot appear in search results at all.
SEOCrawling
Crawling is the act of search engine bots following links to fetch and read pages — the step that has to happen before anything can be indexed or ranked.
SEO