ScrapeBox Help please?

floflo89

Regular Member
Joined
Jun 28, 2010
Messages
419
Reaction score
464
I just got scrape box 48 hr ago, but I ran into a little problem.

I want to use SB only for custom footprint scrape..

I use the SB proxy's and some proxy that I find on the internet, I get around 15-20 working proxy's but when i try to scrape I get nothing..

Please help me whit a FIX.

Thanks.
 
You can go through the below video from Loopline

Code:
http://www.blackhatworld.com/blackhat-seo/black-hat-seo-tools/227788-scrapebox-videos-faqs-troubleshooting-addons-tips-more.html
 
I only what to scrape I dont what to post.

As I said, I use public proxy's but that damn thing wont work..
 
I recommend you to buy some private proxies. You can get 10 proxies for $20-$30/month.
 
It seems like if I use site: inurl: etc, sb does not harvest anything, if I look normal whit out any footprints it harvests.
 
usually if the public proxy is tested with sb for google and it give a positive then it has to work , Coz I am using SB to harvest and only use public proxy for that and private proxy for commenting .

try checking custom foot print in the sb
then use
inurl:"keyword"
or
intitle:"keyword"

just check it with a more common generic keyword and see if it is working

hope this helps
 
Yes, actually I'm using the same number and till now I don't have problems. Harvesting is very fast. You can search the forum for reviews of the proxy services.

You can try also shared proxies but I don't know what will be the effect. I think their quality is close to the public proxies.
 
I've been coming across threads like this more and more lately and in fact I started my own thread where I was having problems and SweetFunny, the creator, contacted me directly and gave me a Debug version of SB. Found out that it was my proxies that were causing all my problems.

If you use heavily laced footprints (i.e Inurl:"keyword" intitle:"keyword" AND...") it's more work on Google's servers and so they pay close attention (from my experience) to the proxies that are accessing this information. They will ban your proxies much faster if you are scraping alot, and if you are using public ones, like I was, you will constantly have to scrape proxies to keep things flowing.

What I have learned is that you really need to get some dedicated private proxies.

I have searched all over BHW for providers and have used them all.

If you want to see my reviews I recommend that you checkout my site: http://www.scrapeboxproxiesx.com/
 
I second that. I find that recently google has gone smarter when dealing with these tools..heavily capitalized search footprints like inurl, etc are becoming more restrictive and short intervals between the searches would results in a short ban of IP..

I would usually harvest 100+ public proxies and let them die while harvesting using these intensive footprints. They should be sufficient to fetch enough results.

Moreover, the footprints are the not only way you can harvest links. :)
 
I have experienced this in my short time with the software, and I know run 260 shared proxies and 50 private and fingers crossed I have not had this issue since.
 
Back
Top