Daniel Micay on Twitter: "https://t.co/ecAejBv4A8 This issue was finally resolved after Googlebot being stuck on Chromium 41 since 2015. Finally not going see errors in their webmaster tools from modern Content-Security-Policy, CSS, ES6, etc. https://t.co/sO022xiyus (pointed out to me by @saleemrash1d)" / Twitter

twitter.com/DanielMicay/st This issue was finally resolved after Googlebot being stuck on Chromium 41 since 2015. Finally not going see errors in their webmaster tools from modern Content-Security-Policy, CSS, ES6, etc. webmasters.googleblog.com/2019/05/the-ne (pointed out to me by

@saleemrash1d

)

Quote Tweet

Daniel Micay

@DanielMicay

Apr 28, 2019

developers.google.com/search/docs/gu > Googlebot uses a web rendering service (WRS) that is based on Chrome 41 (M41). So that's why it's incapable of handling grapheneos.org/releases.js for grapheneos.org/releases. Rendering with Chrome 41 in 2019 embarrassingly bad. It's from early 2015...

4:13 PM · May 8, 2019Twitter Web Client

Replying to

I'd expect this is going to substantially improve their search results since it can finally cope with sites using modern HTML, CSS, JavaScript and other features. I'm not sure how they failed so badly at maintaining their main product properly but at least the annoyance is gone.