Google has up to date its assist documentation on dynamic rendering to say “dynamic rendering is a workaround and never a long-term resolution for issues with JavaScript-generated content material in search engines like google and yahoo. “As an alternative, we advocate that you just use server-side rendering, static rendering, or hydration as an answer,” Google added.

Google introduced dynamic rendering in 2018 as a manner to assist Google to crawl and index your JavaScript content material. For the previous few years, Googlers have been saying it’s best to seemingly not go the dynamic rendering route as a result of Google is rather more able to rendering JavaScript nowadays. Observe, Google has all the time mentioned this was a workaround however made giant changes to the docs to induce this now.

In any occasion, Google made some important adjustments to the assist documentation on dynamic rendering, particularly on the prime of the web page. The web page has a purple disclaimer that reads:

Dynamic rendering is a workaround and never a long-term resolution for issues with JavaScript-generated content material in search engines like google and yahoo. As an alternative, we advocate that you just use server-side rendering, static rendering, or hydration as an answer.

The primary part of the web page was additionally up to date to elucidate “Dynamic rendering is a workaround for web sites the place JavaScript-generated content material is just not accessible to search engines like google and yahoo. A dynamic rendering server detects bots that will have issues with JavaScript-generated content material and serves a server-rendered model with out JavaScript to those bots whereas exhibiting the client-side rendered model of the content material to customers.”

“Dynamic rendering is a workaround and never a beneficial resolution, as a result of it creates extra complexities and useful resource necessities,” Google added.

Here’s what the web page appears like now (click on to enlarge):