To get a batch of good working public proxies you have to harvest the proxies test them, delete the bad ones, then test the good ones again and delete the bad ones.

Its a double process.

You should then have a batch of public proxies that will work for a few hours for what ever task you are doing.

If you dont plan on using the submitting feature and only plan on scraping/harvesting, getting proxybonanza proxies is pretty affordable.

Also the reason you are not getting good results is the keyword or footprint you are scraping for may be too small.

Hey, when harvesting I would suggest you to use Paid proxies since free proxies are already being used by many many if not hundreds of people worldwide. I have used both free and paid proxies. Not to mention free proxies are really slow compared to paid ones. keep in mind, if you are thinking of doing anything big then you will need at least few hundreds of proxies. I have scrapebox, but I havent used it much since I am doingtotally whitehat seo these days.

As RealEcon said, it could also be the footprint you're using.

That being said... Yes! Private proxies will increase ScrapeBox's speed with every task ten-fold. I was using free proxies up until about a month ago and my efficiency with ScrapeBox has just shot-up because everything gets done so much more quicker. (I have the 10 proxy package from yourprivateproxy).

Also, I've seen people advising against using your private proxies for harvesting, and only use them for posting, so as not to get blacklisted with the search engines... but my thinking is what am I paying for if I can't use them to the full extent. So far I haven't had any issues with getting blacklisted, and if I do, I'll just get new ones.

In a nutshell, everything in ScrapeBox can be done with free proxies. It will just get done alott slower.

With free proxies, you'll need to repeat tasks over and over again. With paid, they're usually done on the first or second run.

However, I usually harvest with public proxies and have no problem generating tons of results. So something sounds off. Like Real said, maybe your footprint is too specific?

Try changing your footpring, lower the connections, and increase the timeout.