3 ms·
> Google is already executing js Any idea then why people keep saying¹ that "Serving HTML from the server is great for search engines"? And why should we use
by y0ghur7_xxx 13y ago
> Google is already executing js
Any idea then why people keep saying¹ that "Serving HTML from the server is great for search engines"?
And why should we use this² when google is perfectly capable of executing the js and get the html output all by itself?
¹[citation needed]
²https://developers.google.com/webmasters/ajax-crawling/docs/specification https://developers.google.com/webmasters/ajax-crawling/docs/...
- augustl 13y agoThat link describes a method for translating a URL where a static version of a dynamic page can be found. So you still have to serve and generate static content yourself. So we're not quite there yet. But seems like at least Google has started executing _some_ JS. There are more search engines than Google though :)
- salman89 13y agoTime till the page is usable comes under consideration. You can load the relevant html then begin the bootstrapping of the app. If I recall correctly, Twitter had this problem. The size of their apps + templates bloated to 2MB or so - making that initial page load pretty bad.