This works -- but it does seem like Google has changed the way the info: command works. Even if your proxies aren't banned by Google, they still get banned from using the info: command quite quickly. I tried to check indexing on a list of 3000 URLs, with only 10 threads... and they got banned at about 50% way through.
Do you know of any available proxies that could get passed this? It's a bit tricky because all of the services saying "Google passed proxies" wouldn't work -- as they're only Google-search passed, not "Index-check passed". It's definitely more than just a changing something on their UX / needing to change SB code. It seems they've separated the info: command with other Google searches.
That happend years ago. In fact I posted a video about it 5 years ago
Published on Feb 15, 2012
This is nothing new but I also have a video on how to safely scrape google and the same applies to index checking. In fact there are many different levels, its not just the info: operator.
If you are using 10 threads you should probably have at least 500 or more like 1000 proxies that are info operator passed. Else your going way too fast. You might do ok working in small batches, getting most of your proxies burned and then waiting 48 hours to unblocked, but better to just go slow.
Its not about the proxies or SB code. Google bans ips indescrimanantly. I guess thats untrue, they do actually ban some IPs even faster, based on all sorts of things they don't disclose like how many times in the past the ip has been banned and the search query type and the ip block etc..
Anyway, here are a few videos. The first is the differece video I talked about above. You already know it, but just posting it for the sake of if you want more info or 5 year ago proof or others that may read this.
The 2nd is a custom test video that tells you how you can build a test for proxies to see if they are info: operator passed.
The last is the concept on how to safely scrape google, its service etc... this includes the concept of index checking.
Lastly this change is nothing relevant to the change in code that broke scrapebox, google has banned like this for years, as the 2012 video shows. At any rate, this most recent change was really just formatting.