Daniel Micay on Twitter: "@RichFelker @saleemrash1d I think the gradual move of tons of web content to heavily depending on JavaScript has had a major impact on their search results, largely due to Googlebot being stuck at a fork of Chromium 41 for so long. It also handled modern CSS very badly so it saw even pure HTML/CSS wrong." / 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...

2

1

Replying to

and

I wonder how much of the awfulness of their search results this was responsible for.

1

Replying to

and

Honesty their results would be so much better if they used lynx to crawl.

2

Replying to

and

Too many sites are using tons of JavaScript, so they would be entirely opaque to it. There's a lot of blog and forum software that requires JavaScript to display any results at all. Earlier versions of Discourse couldn't show anything without JavaScript and it had wide adoption.

2

Replying to

and

meta.discourse.org/t/is-a-javascr So for example, when Rust moved from a mailing list to Discourse, it was depending on Googlebot being able to handle JavaScript. There are countless other examples that often hurt their search indexing like nytimes.com comments, etc.

1

Replying to

and

I think the gradual move of tons of web content to heavily depending on JavaScript has had a major impact on their search results, largely due to Googlebot being stuck at a fork of Chromium 41 for so long. It also handled modern CSS very badly so it saw even pure HTML/CSS wrong.

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

Conversation