1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Scrapebox Proxy Harvester Setting..

Discussion in 'Black Hat SEO Tools' started by askcookingtips, Feb 9, 2012.

  1. askcookingtips

    askcookingtips Newbie

    Joined:
    Jan 14, 2010
    Messages:
    45
    Likes Received:
    20
    Occupation:
    communications
    Location:
    USA
    Hi All...

    Quick questions with Scrapebox and the built-in proxy harvester.

    Using the cleanup button, I clean all duplicate proxies and then also filter out proxies by access time.

    What is the best or avg time set??

    I've looked around but haven't found this answer.. maybe it's not a big deal, but I figure it's best not to set the bar to high or low and filter out workable proxies.

    Thanks for any comments or suggestions!
    Eddie
     
  2. loreit

    loreit Registered Member

    Joined:
    May 3, 2011
    Messages:
    51
    Likes Received:
    5
    Occupation:
    Support Engineer
    Location:
    Northern Europe
    I'm a newb on Scrapebox myself.

    I never got the proxie harvester to work efficiently. 99% of the proxies i found (tried various methods) did not work.

    I ended up buying 20 private proxies. The cheapest I could find ($1 each).

    The best time on those is 260ms, and the worst is close to 1000ms.

    Now I manage to harvest/post/verify as I want. Only using my private proxies (not using Google when harvesting).

    Still trying to learn tho...
     
  3. askcookingtips

    askcookingtips Newbie

    Joined:
    Jan 14, 2010
    Messages:
    45
    Likes Received:
    20
    Occupation:
    communications
    Location:
    USA
    Gotcha, I use it alittle differently so need alot of different proxies all the time, using it to ping links from twitter posts. It works how I'm going about it now, but think there is a better way of doing it... managing the proxies that get harvested vs success rate/proxy time-out.

    I'm thinking I get alot of failed pings is due to the slow times on some of the proxies...

    Anyway, thanks for your reply!