WORDPRESS https://anythingseo .wordpress.com/201 8/11/08/the-newlazy-loadingdocumentationfrom-google/
As webmasters and developers look for more ways to defer initialisation of non-critical or non-visible content on their page until needed later, the more this technique becomes a concern for SEOs to ensure that Google can crawl and index those content. Implementing lazy-loading techniques without thinking if Google can discover content within a lazy-loading mechanism, then that risks your content not to be found which, on the other hand, can significantly affect your page’s performance and rank. What does this mean for me? Lazy-loading is a design pattern used in web developing to defer the loading of non-critical content until which point it is needed. It can contribute to the efficiency of content if used appropriately.
And because this has been a concern for the SEO community, Google finally decided to release a new help document to aid SEO and Webmasters and make sure that their lazyloading web pages can still function and rank in the Google search results. According to Google’s Martin Splitt, the release of these new developer documents is an early look of the first version of the system. Both Splitt and John Mueller gave a hint about this when they first mentioned in a webmaster hangout that they were working on such documents, and made some discussions about it. So what can this do for me? Crawling and indexing contents are standard practices in web developing and SEO, and are crucial for a website’s performance, therefore resulting in better ranking in the search engine. Google explained that one has to make sure the content is loaded within the viewport because, without that, GoogleBot won’t detect the content as well. Providing a unique link for each shareable and loadable page is also necessary so that Google can support infinite scrolling or paginated loading. And for this, they recommended the History API to update the URL especially when the content loads in a dynamic process.
But of course, the best advice we can get from Google is not to forget to test using a Puppeteer script and check its implementation. Do not forget to test. Google also recommends reading their dynamic rendering documents. Best to follow them than to cause problems that will only affect your SEO ranking.