\n on what they achieved this year, what went wrong, and how they could improve. We’re no different,
\n but instead of choosing what went well or wrong ourselves, we picked the
\n announcements on our
\n @GoogleWMC<\/a> Twitter account that
\n users interacted with the most, and decided to reflect on those.\n<\/p>\n
\n We had launches that you appreciated a lot. For example, we \n Speaking of robots, together with the \n Like \n But we haven’t stopped there with touching ancient protocols: we also rethought how we need to treat \n One of the most tweeted \u2013 and also most humbling \u2013 moments this year was when we \n We do like to communicate, in general: \n We hope you had a fantastic year and the new year will bring you even more success. If you need
\n announced at Google I\/O<\/a>
\n that
\n Googlebot is becoming evergreen<\/a>,
\n meaning that it’s always going to use an up-to-date version of Chromium for rendering. We hope
\n that this will make it easier for developers to create stunning, modern, and snappy JavaScript
\n experiences, by tapping onto the power of over 1000 new features and interfaces that are now
\n supported.\n<\/p>\n
\n original author of the Robots Exclusion Protocol<\/a>,
\n other search engines, and input from webmasters, we submitted an
\n Internet Draft<\/a>
\n to the IETF in order to start standardizing the 25-year-old protocol.\n<\/p>\n![\"Googlebot](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-670251fa16c7.png\")
<\/p>\n
\n Twitter users<\/a>,
\n we also thought it’s an
\n exciting project<\/a>
\n which lays down the rules of crawling for good, although it doesn’t change anything for most.\n<\/p>\n
\n nofollow<\/code> links<\/a>
\n to keep up with the evolution of the web. It was an announcement that seemed to be welcomed by
\n most Twitter users, and for a good reason: having a
\n “hint” model for rel=\"nofollow\"<\/code><\/a>
\n may help us reward those who create high quality content more, by serving even better results to our users.\n<\/p>\n
\n lost a part of our index<\/a>,
\n which caused Search Console to misbehave, and also had rendering failures roughly the same time.
\n Since Google Search works like a well oiled machine most of the time, we didn’t have processes to
\n quickly communicate issues to those who should know about them: webmasters. Lacking a proper
\n process and channel to communicate these issues was a mistake and we are still working hard to
\n rectify it, however one thing is clear: we need to do more on the critical communication side of
\n things.\n<\/p>\n
\n we shoot videos<\/a>, we go to
\n conferences, big and small, where we reach thousands of webmasters and SEOs, and in 2019 we
\n extended our reach with the
\n Webmaster Conference<\/a>, which
\n landed in 35 locations around the world in 12 languages. Not to mention the
\n weather reports<\/a> on our
\n YouTube channel<\/a>.\n<\/p>\n
\n help with the latter, you can follow our blogs<\/a>,
\n @googlewmc<\/a> on Twitter, or you
\n could join us at a
\n Webmaster Conference<\/a> near you!\n<\/p>\n