There DEFINITLY is something going on.
I used to scrape (Index checking only!) at home and on a VPS, and up until recently without any problems!
(Obviously I also have a proxy subscription for google tested anonymous proxies which I used the last few months successfully).
Since about late this week, pretty much ALL index checks on whatever random proxy come back as "IP BLOCKED".
I even went through the hassles transferring Scrapebox again from my VPS here to my home PC, *assuming* that the IP Block would be gone. (Obviously my home internet has a different IP than my VPS....)
SAME THING: "IP BLOCKED"
And as said I only do simple index checking, not even extensive scraping!
I want to clarify:
Simple "index checking" worked flawlessly for me during the last months using a proxy service here on the forum which provides "google tested proxies". Looking above in this thread, I am NOT THE ONLY ONE who all-of-a-sudden sees the problem that even with many hundreds of proxies they immediately come back as "IP blocked". This is behaviour which started just last week!!
That this is not "normal" is proven that I just moved scrapebox from my VPS here to my PC and having the same problem. There is no logical reason why 90% of proxies I am using coming back as "IP blocked", not here on my home PC! (Obviously, also on my VPS nothing has changed.). I wouldn't post this if there wasn't more people like me who see "IP blocked" since mid/late this past week.
There probably is something up and that "Something" is that Google is probably going on a IP banning spree and has adjusted the rules and time frames within which some IPs/IP ranges are banned. This is nothing new, they have done this many times in the past, and will do it again in the future, they just tightened things down.
I acknowledge that nothing has changed on your end, but nothing has changed with Scrapebox either, it is Googles rules that have changed. Scrapebox still works. I just now tested and made these screenshots:
Firstly is a index run with no proxies, you can see in the lower left hand corner its 58 into the run, no instant ip blocked. This was with 1 connection, this is a dedicated server in a data center. However I also ran this at my office, which is using a comcast business connection IP here in Indiana, USA. It hammered thru 22 urls at 5 connections in about 3 seconds before I hammered the stop button. (my coworkers don't like it when I get the ip banned at the office and they have to enter captchas on google.com hehe)
Also note all these are checking google indexed
Datacenter in Capistrano Beach, Califorina USA:
Office IP (note the screen above is licensed to Matt Borden 13 and this one below is licensed to Matt Borden 14 (different PC)):
Here we have the Data Center Server again, but using 50 shared proxies from buyproxies.org:
Here we have the Data Center on a 2nd run with IP only, it got over 200 index checks done at 1 connection with the ip after having also done over 50 checks in the screen above on the same ip just 3 mins earlier:
I also watched the ones on my local machine in Debugger, they all show a 200 and are all returning normally.
It is important to note that index checking google does use the info: operator, which is an advanced operator. Google can and does perma ban IPs, and they can perma ban entire ip ranges. They also have different bans, and ban regular keyword search, advanced operators, Pr checking, keyword scraping, all separately, and they can dial in even more then that.
So I won't dispute that something changed for a bunch of people, but it didn't break Scrapebox, SB still works fine, all that changed was google decided to pick on your IP range(s) and ban you or perma ban you for the queries being used to do what you want to do.
Edit:
For kicks and giggles I hopped over to another data center, in Beauharnois Quebec Canada with Solid SEO VPS and ran 50 urls there, all of which complated:
Google knows your game, its time to deal your self a new hand, buy some good proxies and go slow, or try something like reverse connect proxies from reverse proxies, or proxy rack etc...
instant IP BLOCKED with index checking on google
^^ See above
Both simple and advanced operators searches DO NOT work in the default harvester.
Both simple and advanced operators searches DO work in the custom harvester.
I suspect that your issue is related to the index checking I just posted about above, google seems to be banning ips extremely quickly/instantly for some ip ranges. Perhaps some of the people that are having index checking issues can respond and say if they can scrape google with the regular multi harvester and the custom harvester?
Im honestly not sure why the custom harvester would work and the multi/single does not, they all pull from the same pool if user agents, although the url string may be slightly different (although in reality I would think its the same string, but google does allow some flexibility in url string construction) and I suppose google could have decided to ban the url string used in the multi harvester for some ip ranges, although Im able to scrape and index check etc with proxies and without from every location I have scrapebox installed and thats many different ips and locations. So basicaly I have no idea and Im shooting in the dark.
Without being in front of your machine I couldn't' say for sure. However, under your custom harvester settings do you have any of the use proxies boxes checked? Because if the custom harvester is auto harvesting proxies in the back ground that would explain it.
I'm having the same problem with the ip blocked. Since I'm not the only one, I guess it has something to do with scrapebox.
^^ See above
I have subscribed your marketplace but why don't you answer my question or anything. ??????
This is a sales thread for Scrapebox, you subscribed to my Scrapebox Marketplace which is auto approve lists. I don't work for Scrapebox and since this sales thread is for Scrapebox we need to take this outside this thread. None the less I did activate you and if you would have checked your email address that you paid from (instead of a random email address that I had no way of knowing that you used) you would have found the link that would let you get access without my intervention.
Further I don't live at my desk 24/7, Im already there 365 days a year, but I do have a wife and kids and a life. Also you already flooded my inbox, and I responded to you there. Anyway, please pm me or just reply to my emails, or use the contact form on the site for future responses and do not use this thread.
