Google has updated the dynamic rendering help documentation and Google no longer recommends using dynamic rendering. This is a workaround, not a long-term solution to Google Search crawling and indexing issues with JavaScript.
The truth is, Google always said this was a workaround, but now with advances in web and crawling technology, Google is urging developers, webmasters, and SEOs to avoid using dynamic rendering. I’m looking for
What is dynamic rendering? Google says that dynamic rendering means “switching between client-side rendered content and pre-rendered content for a given user agent”. Optionally, you can serve the HTML version of the page to Google while serving the JavaScript version to your users. Google says that at this time, “JavaScript is difficult to process and not all search engine crawlers can handle it successfully or quickly.” The company says it hopes the issue will be fixed eventually, but “in the meantime, we recommend dynamic rendering as a workaround for this issue.”
what changed Google has updated its help documentation for dynamic rendering to state, “Dynamic rendering is a workaround, not a long-term solution to problems with JavaScript-generated content in search engines. Instead, use server-side rendering. , static rendering, or hydration as solutions.”
Also, Google has added and updated the following sections at the top of the page:
Some websites generate additional content on the page by running JavaScript in the browser. This is called client-side rendering. Google Search runs JavaScript, but Google Search has limited JavaScript capabilities that can cause problems with some pages not displaying content in the rendered HTML. Other search engines may choose to ignore JavaScript and not display content generated by JavaScript.
Dynamic rendering is a workaround for websites where JavaScript-generated content is not available to search engines. The dynamic rendering server detects bots that may have problems with JavaScript-generated content and provides these bots with a server-rendered version without JavaScript and a client-side rendered version. display the modified version of the content to the user.
Dynamic rendering is a workaround, not a recommended solution. Because of the increased complexity and resource requirements.
Before screenshot. Here’s a screenshot of the previous page:
After screenshot. Below is a screenshot of the later page.
why you care. If you’re using dynamic rendering, or considering using it in the future, try server-side or static rendering, or hydration as an alternative going forward. It’s not always common for Google to be outspoken about discouraging a particular technique. Google says so here.
What’s New in Search Engine Land
About the author
Barry Schwartz is a contributing editor for Search Engine Land and a member of the programming team for SMX events. He owns his RustyBrick, his New York-based web consulting firm. He also runs the Search Engine Roundtable, a popular search blog on highly advanced He SEM topics.You can follow Barry Twitter is here.
