all my proxies are testing fine.. I even tried harvesting public and scraping yahoo..
I have tons of domains (400k) that I know target AA blogs. I want to do a linkdomain: search to get all their AA backlinks. Is their an alternative method to this?
The only way to pull a link domain is with the backlink checker addon, but its built specifically for that, so it does a good job.
Hi
I am not sure if this is answered already, if so forgive me for repeating the question.
How do i remove the limit that is set for Rapid Indexer. I want it to have no limit on number of links that can be entered
As mentioned above it can't be removed. You have to remember that scrapebox is a 32bit app, as such it can't use more then 1.8GB of RAM and the rapid indexer does everything in memory. So the reason the limit is there in the first place is that if you load more then that its likely to go over the memory limit imposed by windows and 32bit apps and it will crash with an out of memory error. So I promise, using smaller lists is easier then having it crash every single time you load a big list, and crash in the middle. It will drive you mad. Limits are there for a reason, to protect you and save you hassle.

Just like the speed limit when driving a car.
Hi, I have 2 problems with scrapebox so far. I'd like to ask you guys what would be the best practices on these issues.
1) the backlink checker - how to work this out with a huge list of URLs to get backlinks for. For instance right now I have a 1 mil long list of URLs to get the backlinks for. If I process the whole of it at one time, the number of backlinks would be huge. What's the best way to handle this? Especially in regards to the proxies, which burn out very fast when running the backlink checker. What do you advanced users do for this? Buy a hundred private proxies, or scrape public ones, or just split your big URL list and run the chunks with breaks in-between?
2) the link checker - I seem to get fewer found results if I increase the number of connections. The default 30 connections came up with most founds, then increasing to 300 and 200 brought in much fewer numbers. The program didn't hang or crash, just results were significantly fewer.
I'd appreciate your sharing your experience with this.
I would split the list and run chunks. I mean pulling backlinks for 1mil urls could me that you could wind up with as much as 1 billion ulrs+ Its unrealistic to try and work with that many urls in even a semi timely manner. Just split the list and work thru it. I would put it in 1000 or maybe 2500 chunks cause even with 1000 X 1000 possible backlinks your looking at a million ulrs. Then you have to work thru those.
Sure the link checker is going to give less found results with higher connections, just like posting will. You only have so much resources with your processor and memory and you only have so much bandwidth. If you bandwidth pipe is full from too many connecitons, then many more of the connections will timeout. You have to play with it to get a rough idea. Rasing your timeouts can help, but at some level your just chasing your tail.
I run on 1000Mbit connections and often use as much as 300-400Mbit at once. I still don't turn my connections for link checker past 200. I have on occasion turned it to 500, but knowing with speed you lose accuracy. If you rush thru anything in life its at sacrificing accuracy. So you have find find a level where you are comfortable with the loss of accuracy vs the time spent working against over all volume of results. And you thought that math class in school was pointless.
This is really getting irritated... I had been using ScrapeBox on Xsserver.eu from past 6 months now. I never had problem until past few weeks. I all of a sudden started getting success rate as less as 3-5% and sometime when i restarted ScrapeBox i get a error telling "It almost looks like something is blocking ScrapeBox, or is modifying the tcp data received from the server".
I thought the problem was with my Squid Private Proxies then i sent them a mail and requested for new set of proxies who ms was less then 400. But, the problem still remand even after changing the proxies. So, i got my whole windows server 2008 OS re-installed, applied for license transfer i see the same error that something is blocking ScrapeBox.
To do the above i wasted 5days and all my work is at halt. This is really getting irritating so please someone tell me what i have to do to solve this issue that i am facing.
I found there are few people here who facing the same problem
Looking forward for quick reply...
Thanks in advance...
Version .21 is supposed to fix the "modifying the tcp data received from the server". that some people were having. So if you haven't updated to that, then you should do so.
Success is relative, very relative. How are you getting your success numbers, from scrapebox?
The dissertation:
Firstly scrapebox receives a header reply from the blog that tells it if it was "successful" often the blog will not return a proper header, due to server failure or whatever, next the proxy can also not pass along the right header etc... Whenever scrapebox doesn't get a 100% "yes it worked" it assumes it failed. So having too many connecitons going, not a high enough timeout, slow DNS, bad proxies or simply blogs that aren't returning the headers due to X modification they have done will decrease what scrapebox says was successful.
I have auto approve lists in the hundreds of thousands of urls that if you run them thru scrapebox they will show as failed due to the way the blog works, but when you run the link checker they show found live links that succeeded.
So the only way to know true success is to check for how many links are actually found, which again is subject to you understandig conneciton, timeout and bandwidth limitations so the link checker doesn't timeout on tons of urls.
If we are talking Auto approve urls its easy enough to check true success, just link check the whole list. If we are talking about non auto approve then you are going to need to wait 3-6 weeks and run the link checker then for an accurate success rate.
Else its highly relative. I love the success/failed feature in sbox, but it is in no way an accurate measurement of how many links actually stick. Since the links that are live and google can see is what we are after, link checking is the only real way to determine success rate.
So in short your problems could include any or all of:
Too High of connections - turn them down.
To low timeouts - turn them up.
Proxies that when tested show good results but when hammered can't handle the stress - turn your connections down. Look thru the eerror messages after posting and use those to determine whats wrong.
A bad list - either blogs that aren't doing their part on returning a success header or flatly a bad list thats comprised of urls that can't be commented on or aren't successful with sbox in the first place.
Overall looking at the error codes on the failed urls after posting is completed and then studying what those error codes mean will give you a great insight into solving your own problem.
I can tell you the problem is not scrapebox, the poster hasn't changed recently. The problem is most definitely how You are Using scrapebox. Save the "modifying the tcp data received from the server". error anyway.
I need license transfer in less than month.
THIS IS A DISASTER
Hope it will be transfered in next 30 days. I would **** their support sometime. NOREPLY, many times lost message, they did not replied.
I have never not had a message answered in almost 2 years. Their support is quite possibly the best of any black hat product on the market, and considering they charge much much less then products that aren't even as good as theirs I would dare say it is single handedly the best support I have ever had black or white hat product.
If you transferred more then 1 time in the month its not their fault you used up your free transfers. Its clearly stated what the policy is, you can read it before you buy scrapebox. If you want more transfers pay the $10 fee.
http://www.scrapebox.com/policy
Its not hard. The policy is straight forward. Its just like going to the store. If you want to buy bread, pay the price or don't, but don't get mad at the store for not giving you 2 loaves for the price of 1.