It turned out that Google couldn’t find and follow links placed within content injected with JavaScript, regardless of the framework used to build the test pages. johnmu is not a chatbot yet □ September 13, 2018Ī year before, in 2017, Bartosz Góralewicz, the CEO of Onely, conducted research that showed how Google was struggling with crawling and indexing JavaScript content, and it took many SEOs by surprise. If your site produces new / updated content frequently & you want it indexed quickly, you need that content in the HTML. Yeah, there's no fixed timeframe - the rendering can happen fairly quickly in some cases, but usually it's on the order of days to a few weeks even. Then John Mueller, Webmaster Trends Analyst at Google, confirmed this in a tweet: So Googlebot might index a page before rendering is complete and the final render can actually arrive several days later, and when that final render does arrive, then we perform another wave of indexing on that client-side rendered content. “So if the page has JavaScript in it, the rendering is actually deferred until we have the resources ready to render the client-side content, and then we index the content further. In May 2018 during the Google I/O conference, Tom Greenaway, a developer advocate at Google, said: Onely’s research reveals that the delay in indexing JavaScript content is still very much there.
0 Comments
Leave a Reply. |