Post by account_disabled on Mar 10, 2024 8:11:20 GMT
The well. Split tests show SEO improvements from removing a reliance on JS Although we would like to do a lot more to test the actual realworld impact of relying on JavaScript we do have some early results. At the end of last week I published a post outlining the uplift we saw from removing a sites reliance on JS to display content and links on category pages. odn_additional_sessions.png A simple test that removed the need for JavaScript on of pages showed a uplift in organic traffic worth thousands of extra sessions a month.
While we havent proven that JavaScript is always bad nor understood the exact Europe Cell Phone Number List mechanism at work here we have opened up a new avenue for exploration and at least shown that its not a settled matter. To my mind it highlights the importance of testing. Its obviously our belief in the importance of SEO splittesting that led to us investing so much in the development of the ODN platform over the last months or so. Conclusion How JavaScript indexing might work from a systems perspective Based on all of the information we can piece together from the external behavior of the search results public comments from Googlers tests and experiments and first principles heres how I think JavaScript indexing is working at.
Google at the moment I think there is a separate queue for JSenabled rendering because the com@#!*tional cost of trying to run JavaScript over the entire web is unnecessary given the lack of a need for it on many many pages. HTML and core resources regularly Heuristics and probably machine learning are used to prioritize JavaScript rendering for each page Some pages are indexed with no JS execution. There are many pages that can probably be easily identified as not needing rendering and others which are such a low priority that it isnt worth the computing resources. Some pages get immediate rendering.
While we havent proven that JavaScript is always bad nor understood the exact Europe Cell Phone Number List mechanism at work here we have opened up a new avenue for exploration and at least shown that its not a settled matter. To my mind it highlights the importance of testing. Its obviously our belief in the importance of SEO splittesting that led to us investing so much in the development of the ODN platform over the last months or so. Conclusion How JavaScript indexing might work from a systems perspective Based on all of the information we can piece together from the external behavior of the search results public comments from Googlers tests and experiments and first principles heres how I think JavaScript indexing is working at.
Google at the moment I think there is a separate queue for JSenabled rendering because the com@#!*tional cost of trying to run JavaScript over the entire web is unnecessary given the lack of a need for it on many many pages. HTML and core resources regularly Heuristics and probably machine learning are used to prioritize JavaScript rendering for each page Some pages are indexed with no JS execution. There are many pages that can probably be easily identified as not needing rendering and others which are such a low priority that it isnt worth the computing resources. Some pages get immediate rendering.