Google: Dynamic rendering is a workaround, no longer a long-term solution

Google has updated theirs dynamic rendering assist documentation “Dynamic rendering is a workaround and now not an extended-term solution to issues with JavaScript-generated content material in serps. “rather, we endorse the usage of server-side rendering, static rendering, or hydration as a workaround,” Google delivered.

Google published dynamic rendering in 2018 as a way to assist Google discover and index your JavaScript content material. For the past few years, Googlers were announcing that they likely shouldn’t cross for dynamic rendering due to the fact Google is much extra capable of rendering JavaScript nowadays.

anyhow, Google has made some sizable changes to the dynamic rendering assist documentation, particularly at the top of the web page. There’s a crimson disclaimer on the page that reads:

Dynamic rendering is a workaround, now not a protracted-term solution, to issues with JavaScript-generated content material in search engines. Instead, we suggest using server-aspect rendering, static rendering, or hydration as a workaround.

the first section of the web page has also been updated to provide an explanation for “Dynamic rendering is a solution for websites in which JavaScript-generated content material is not available to engines like google. The dynamic rendering server detects bots which can have problems with JavaScript-generated content, and serves a server-rendered model without JavaScript to those bots, even as serving customers a rendered version of the patron-facet content material.”

“Dynamic rendering is a workaround and isn’t always a recommended solution as it creates extra complexities and aid necessities,” Google introduced.

this is what the page looks as if now (click on to amplify):

that is how the web page looked earlier than (click to make bigger):

discussion board discussion at Twitter.