Google Is Going To Update GoogleBot’s User-Agent 

Ensure you are set up for the new GoogleBot user agent, which introduces this December. 

Google reported that beginning in December, Google would refresh Google’s user agent to show the version of Chrome that GoogleBot is running. It is imperative to update any code you may have that may take a glance at the user agent of GoogleBot to help this change going ahead. 

New user agent. At the point when Google introduced the Evergreen GoogleBot, Google purposefully kept the old user agent. It was done so any individual who may have hard-coded any identification strategies for GoogleBot wouldn’t have any problems with the latest Evergreen GoogleBot.

The new user agent will immediately change to demonstrate the present version of Chrome that GoogleBot is utilizing when crawling your site. 

Earlier. currently this is what GoogleBot’s user agent resembles on desktop and mobile: 

Mobile: 

Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.96 Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) 

Desktop:

Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)

Or then again 

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Googlebot/2.1; +http://www.google.com/bot.html) Safari/537.36 

Later: This is the way GoogleBot’s user agent will resemble after this adjustment in December. In the accompanying user agent strings, “W.X.Y.Z” will be replaced with the Chrome version Google is utilizing. For instance, rather than W.X.Y.Z, you’ll see something like “76.0.3809.100”: 

Mobile: 

Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 (compatible; Googlebot/2.1; +http://www.google.com/bot.html) 

Desktop:

Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html

OR

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Googlebot/2.1; +http://www.google.com/bot.html) Chrome/W.X.Y.Z Safari/537.36

What to pay attention to. If you have any user-agent identification contents that are hardcoded for GoogleBot, you have to try to help this new user agent design. Google stated, “We’ve run an assessment, so are certain that the change won’t influence most sites.” “If your site searches for a particular user agent, it might be influenced. You should utilize feature identification rather than user-agent sniffing. If you can’t utilize highlight location and need to distinguish Googlebot using the user agent, at that point, search for “Googlebot” inside the user agent,” Google included. 

Step by step instructions to test it. Here is the way to test to ensure your pages support this after you roll out the improvement to your code or while being developed mode. You can supersede your user agent in Chrome utilizing these instructions

Why we give it a second thought, Googlebot is getting another user agent, and that is energizing. But, it can affect your site if you had any user agent discovery techniques for GoogleBot. Make a point to test your site to check whether it underpins the new user agent. Most sites presumably don’t have to stress over this yet you have done any advice GoogleBot recognition, you may need to find a way to update those scripts.

About Syeda Khadeer Sultana

My urge to learn something new and passionate attitude changed my interest in being a professional content writer. My constant efforts and experience in the marketing field have built a first-rate conception of Martech, Adtech and digital marketing in me. Currently, I'm putting my efforts in delivering content on advanced marketing & technology techniques to confer a benefit to entrepreneurs.

Leave a Comment