New 'Dynamic Rendering' to Solve JavaScript Indexing Issues
If you have a site that heavily uses JavaScript, Google might have some good news for you. As you probably know, when googlebot visits your site it instantly crawls, renders, indexes, and follows links, repeating the process 120 billion times a day.
And even though Google has immense resources, there are over 130 Trillion documents on the web. Crawling the web is so resource intensive that googlebot defers fully rendering a site's JavaScript driven client side content until they have the available resources to do so.
This means that JavaScript heavy sites that employ client side rendering cannot expect to be fully indexed without delay. That's a problem for large rapidly changing sites (i.e. news) or sites with a strong social media presence, each of which are presumed to use modern (>Chrome41) JavaScript features.
To solve this problem Google made a major concession by introducing what SEO veterans might recognize as a form of cloaking (aka, IP delivery). Why? ...because Google wants your JavaScript powered website to be search friendly. And, probably, so do you. So this is a good thing if the shoe fits.
They're calling it Dynamic Rendering. And rather than show you a bunch of slides and try to explain it, we'll let John Mueller tell you all about it in the video below.
It's set to begin at the 20:55 mark where John introduces Dynamic Rendering. However, we suggest that you watch the entire video (scroll it back to the beginning). This will give you a solid understanding of who needs this and why there's a need for a solution in the first place.
New Features Added to Mobile Friendly & Rich Results tools
