Skip to main content

Search Engine Optimization (SEO),Social Media, Article Submission

Loading...

Google testing tools now support evergreen Googlebot


After three months, the Google testing tools are now using the latest version of Googlebot.

Google announced that many of the testing tools available within Google Search Console or the Google developer portal are now using the new evergreen Googlebot for crawling.

Evergreen Googlebot. Three months ago, Google launched what is being called evergreen Googlebot. In short, it means that Googlebot, Google’s web crawler, will crawl the web using the latest version of Chromium – basically what you and I see when we launch Chrome and browse the web. Googlebot and Chrome will be using the same rendering engine.

Tools gain support. Now, three months after this launch, the tools Google have now support and will continue to support the latest version of Chrome. That means what you see in Chrome, what Googlebot sees and what Google shows you in its testing tools should all match.

Which tools? Which tools currently support the evergreen Googlebot? Google listed these:

Search Console‘s URL inspection tool
Mobile-friendly test
Rich results test
AMP test
The useragent is the same. But you are looking at your log files and you see that Googlebot’s useragent still references the old Chrome version number? That is true but Google did not want to change the useragent yet. They will in the future but for now, the useragent is the same to not cause issues for those who hardcoded in specific commands for Googlebot based on the current useragent.

Google wrote “The new Googlebot still uses the same user agent as before the update. There will be more information about an update to the user agent in the near future. For now, Googlebot’s user agent and the user agent used in the testing tools does not change.”

What does it look like? Here is a screen shot of the mobile-friendly testing tool showing you what one site might look like before and after this update


Comments

Post a Comment

Popular posts from this blog

Google Image Search updates guidelines, adding structured data, speed and more

Google updated the Google Image Publishing Guidelines document today, adding more details around structured data, page speed, title management and user experience details. The old documentation can be viewed in this screen shot I captured previously. The new guidelines have updated content around creating a better user experience with your images, including adding good context, optimizing placement, embedding tips, device-friendly sites and good URL structure for your images . In addition, Google has explained how the image titles work since the change. Google also added sections for adding structured data for product, video and recipe markup. There is a new section for speed, including information about their PageSpeeds Insights tool, AMP and responsive image techniques. You can check out the new guidelines over here and compare them to the old guidelines over here .
Post a Comment
Read more

How to recover from a negative SEO attack

Welcome to the next-to-the-last article in our six-part series on negative SEO . If you’ve been following along, you understand what negative SEO is. You’ve audited your situation to know whether or not you were hit, and you know how to reduce your likelihood of being a target in the future. You even know how to try and defend yourself from an ongoing negative SEO campaign. Now, it is time to clean up the mess. This article is meant to serve as a companion piece to the previous articles in the series. As such, we will once again segment the recovery process into three main areas: links, content and user signals. The good news is that you can recover from attacks in any of those areas; the bad news is that, depending on what type of negative activity you’re attempting to recover from, it could be a lengthy process. Inbound links The first step is to build a disavow file of the most toxic links you have identified in your analysis of the attack. You can find more about how to structure ...
Post a Comment
Read more

Google Search Console reporting currently delayed

Google posted on Twitter Friday morning that some of their reports within Google Search Console are currently delayed more than their normal two-days. “Some Search Console reports are currently a bit more delayed due to issues in the reporting pipeline,” the company said. This has no impact on your search rankings, this is just a reporting issue. Which reports are delayed?  Specifically, the AMP, Rich Results / Structured Data, Hreflang, Index Coverage, and Mobile Usability reports are all delayed according to Google. I will say that I did check several of these reports, and not all of them are delayed. For example, while the mobile usability and AMP reports are both a week old, the index coverage report is only two days delayed, which is the normal expected reporting delay you would see in Google Search Console. Should I worry?  No, this is just a reporting issue which Google said doesn’t affect your site in search. So your rankings should not be impacted by this issue. When ...
Post a Comment
Read more