GOOGLE’S JAVASCRIPT DRIVE BY
Google raised the lid on its JavaScript travel method and the way Googlebot struggles to render great deal of JavaScript quickly. What this suggests is that Google effectively takes a primary pass at the site; rolling on past, having a glance, taking within the basic details.
Google raised the lid on its JavaScript travel method and the way Googlebot struggles to render great deal of JavaScript quickly. What this suggests is that Google effectively takes a primary pass at the site; rolling on past, having a glance, taking within the basic details. Then once it’s a lot of rendering resources obtainable, it takes a more in-depth pass and makes positive it takes down all the small print.
So, if you’re employing a heap of client-side JavaScript, it might take longer for your web site to be absolutely indexed and Google may miss some details on the primary crawl – notably canonicals and meta information. What will that mean? Well, might take a moment for your content to be indexed, leading to less visibility in search and, probably, lost earnings. Moreover, if Google misses canonical tags, it might find yourself having serious consequences for your organic visibility.
Google did propose a solution called ‘Dynamic Rendering’ which is a method to show server-side rendered content to Google while showing client-side content to users. Implementation details were fairly light on the ground, but there are two tools to help you implement Dynamic Rendering:
Puppeteer and Rendertron
The crux is that if you decide to take up on this, you need to get this process done else it will damage your performance in organic search and dissuade people using Java Script.
