4 ms·

Their support for rendering JavaScript is, IMO, that they have turned Chrome's engine into their web crawler. We see some signs of this with the chrome headles

Their support for rendering JavaScript is, IMO, that they have turned Chrome's engine into their web crawler. We see some signs of this with the chrome headless project and with the fact that Chrome, masquerading as a mobile viewport, can be used as an effective mobile crawler, even when the mobile UX is provided primarily by JavaScript. I think they still use a plain HTTP request based crawler for "most" sites (mainly for speed), but then flip on Chrome-based crawling for popular sites and for sites that seem to be JS-heavy. I see no reason why, long term, Chrome wouldn't become the primary crawl/render engine for Google.

thoop 9y ago
It looks like they are currently using Chrome 41 (https://developers.google.com/search/docs/guides/rendering https://developers.google.com/search/docs/guides/rendering) when rendering pages. I agree that with all of the work on headless Chrome, they should move towards using headless Chrome in the future.
- exikyut 9y ago
  Iiiiinteresting. I wonder if all. the. security. patches. from every subsequent Chrome milestone regularly get backported to M41? Obviously it's sandboxed to the hit. Poking the sandbox and seeing what it was made of would be VERY interesting though.