Timeline for Does heavy JavaScript use adversely impact Googleability?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 4, 2012 at 14:39 | comment | added | shabunc | this is not 100% true nowadays. Actually, at least google do some experimenting with indexing ajax content. | |
| Jun 4, 2012 at 14:32 | comment | added | jfrankcarr | It's been hard to tell exactly how far they go since this part of their algorithm has been seeing a lot of updates. It does look at DOM element insertion but much of the initial focus was to deal with web spam techniques (ad insertion overlays, keyword stuffing/redirecting, etc). More recent updates seem to be doing more content analysis but exactly how much is unclear still. | |
| Jun 4, 2012 at 12:05 | comment | added | Pete | Ok, it has gotten more advanced. But how far does it go? If the page retrieves data asynchronously through AJAX and then inserts the retrieved data in the DOM, will Google be able to see that data as part of the original URL? | |
| Jun 4, 2012 at 11:48 | comment | added | jfrankcarr | They do evaluate it these days. See forbes.com/sites/velocity/2010/06/25/… This is from 2010 and their ability to execute, statistically evaluate and other analyze Javascript has only continued to be improved and refined. | |
| Jun 4, 2012 at 6:23 | history | answered | Pete | CC BY-SA 3.0 |