Let's see if we are a good fit. Schedule a time to chat that works best for you
Google officially “divorced” Robots.txt noindex and will no longer endure its caprices. For all the remaining procedures they gave each other time till September 1, 2019. But it’s obvious that they will definitely get divorced. It’s all because Google wants to focus on looking at unsupported implementations of the internet draft; that includes crawl-delay, nofollow and noindex. Moreover, there is one more equally important reason for this kind of divorce: being unofficial.
All knew that robots.txt directive was not an official one. Google also knew and for a long time it was preparing us for the bad news. Nevertheless, they continued to live in peace until July 2, 2019, when there was the official announcement, saying: “Since these rules were never documented by Google, naturally, their usage in relation to Googlebot is very low,” Google said. “These mistakes hurt websites’ presence in Google’s search results in ways we don’t think webmasters intended.” Besides the announcement, Google released its robots.txt parser as an open source project.
By divorcing robots.txt Google will not leave its “kids” without a shelter. Here are the official alternative options:
It’s simple. It just needs some time and a little effort. As it’s mentioned above there are 5 main options serving as alternatives. To be shortly speaking you must know the follwing: if the page is already indexed, then use meta noindex. If the page is still not indexed, you can disallow the robots from crawling it.
Google still cares as it is important to make sure we do not the noindex directive in the robots.txt file. If still we do, it’s better for us to fix our robots.txt files before September 1. Otherwise there will be a lot of penalties.
If you have more free time read the official announcement document here.