Google is Rendering More Pages as Cheaper Resource-wise Than Running Rendering Heuristic
Google Determines if Pages Need to be Rendered by Comparing Content Found in Initial HTML & Rendered DOM
Google compares the content of the raw HTML of a page from the initial crawl to the rendered DOM after rendering to see if there is new content and to determine if it needs to be rendered going forward.
More or Less Every New Website is Rendered When Google Crawls it For the First Time
Nearly every website goes through the two waves of indexing when Google sees it for the first time, meaning it isn’t indexed before it has been rendered.
Ensure Hidden Content is Set-up With CSS Rather Than JS if You Want the Content to be Indexed
An Updated User Agent is Expected to Reflect The New Modern Rendering Infrastructure
Google has been experimenting with the current user agent settings and is re-thinking the set u. John expects some changes to be announced in the future around an updated user agent so that it reflects the new modern rendering infrastructure.
Look Into Server-side Rendering For Improved UX as Dynamic Rendering is a Temporary Workaround for Crawlers
Ensure all Key Content is Available if You Are Streaming Content
If a site is streaming content progressively to a page, John would recommend ensuring all key content is available immediately due to the method used to render content. Any additional content which is useful for users but not critical to be indexed can then be streamed progressively.