Serving a rendered version to crawlers and a JavaScript-driven version to users. Content should remain equivalent.
Dynamic rendering sends a pre-rendered version of a page to selected crawlers while ordinary visitors receive a JavaScript-driven version. It was used as a workaround when search engines had difficulty processing an application. The defining feature is the separate delivery treatment, not simply that a website’s content changes over time.
Google no longer recommends dynamic rendering as a long-term approach. Its guidance favors server-side rendering, static rendering or hydration-based solutions instead. A separate crawler version introduces additional work: identifying requests, generating the representation, keeping it fresh and ensuring it reflects the version people actually use.
Content equivalence is essential. A crawler should not receive invented services, extra keyword passages or claims hidden from users. Even without deliberate manipulation, stale snapshots can misrepresent prices, availability or instructions. A setup that solves an initial rendering problem can create an ongoing maintenance problem if nobody owns its refresh and failure behavior.
Takeaway: Treat dynamic rendering as a specific legacy workaround to evaluate, not a default SEO upgrade. Ask whether a shared, reliably delivered representation can meet the site’s needs with less duplication.
Example
A training provider’s older application serves a generated course snapshot to crawlers. The live interface removes a cancelled class, but the snapshot still lists it. The team investigates the refresh process and a more maintainable delivery approach rather than accepting the crawler snapshot as correct because it contains readable HTML.
What to check
If a site already uses dynamic rendering, compare representative crawler and user outputs, including important details and status responses. Plan any replacement carefully; removing the workaround before the new approach is verified could make previously accessible content unavailable.
For more detail, see Google dynamic rendering guidance.