[SB Case Study] Starting with nothing, taking it to the top

I think I'll lay off of the pinging of my backlinks for a little bit. The index rate is fine as it goes now but any faster I wouldn't feel comfortable with:
kbwyab.png


Also, I uploaded a part of my 1 mill list:
[Download]
 
Last edited:
Interesting re: Unique Domains.

So, do you use a tool such as Loopline's to remove the root, followed by leaving just 1 random URL on that domain?

Then post to it and if it sticks, then do a site:domain.com and post to the rest?

I had a list of something like 250,000+ shrunk to about 1034 doing that method so can only assume that's how many different domains were in the list.

Or do you use a different method?

No I don't know what you just described :p

I scrape about 10 million urls and then merge the files with either the SB addon or TXTcollector. Then I remove domain dupes with the SB addon.
This leaves me with one urls per domain to post to.

[edit]
Ah I re-read your comment. Yes that is how I do it except for the site: scraping part. Usually I don't bother but sometimes I do.
 
Is that backlink checker using yahoo sitexplorer to check backlinks?
 
No I don't know what you just described :p

I scrape about 10 million urls and then merge the files with either the SB addon or TXTcollector. Then I remove domain dupes with the SB addon.
This leaves me with one urls per domain to post to.

Haha. Yeah, I meant a similar thing.

The problem with the domain dup remover is that it'll sometimes keep the root.

Let's say you had

domain.com/blog1
domain.com
domain.com/blog2

it'll sometimes keep domain.com and remove the 2 blogs, which isn't what you want.

The loopline tool first removes the root from the entire list and then does what the SB tool you mentioned, does.

It's just to make sure you are only left with blogs and not roots.

Does that make sense? :o

Do you find the list is significantly reduced when you remove duplicates? Like 1% of the original size?
 
Haha. Yeah, I meant a similar thing.

The problem with the domain dup remover is that it'll sometimes keep the root.

Let's say you had

domain.com/blog1
domain.com
domain.com/blog2

it'll sometimes keep domain.com and remove the 2 blogs, which isn't what you want.

The loopline tool first removes the root from the entire list and then does what the SB tool you mentioned, does.

It's just to make sure you are only left with blogs and not roots.

Does that make sense? :o

Do you find the list is significantly reduced when you remove duplicates? Like 1% of the original size?
Ah yes that makes sense.

Well with WP blogs the reduce is not that bad, usually I am left with about 10% but with any other platform you might get less than %1
 
You were right Maruk, the blogengine yielded 89 backlinks out of 550k harvested haha!

But, I did find something great, of the failed posted, I did a pagerank check and have a bunch of great blogs to comment manually on. The first one list is a PR4 with only 2 comments and without a nofollow tag
 
Last edited:
Just to test I imported a harvested list of exactly 150k.

I then selected the 'Remove Duplicate Domains' and it resulted in a compressed list of 57866.

I tried the Loopkine SB Helper Tool (with the 150k) and selected to remove root > then imported back to SB and selected the 'Remove Duplicate Domains' and it resulted in a compressed list of 46721.

So I assume this means the original list had 11145 (57866 - 46721) URLs which was only a root domain.
These domains had 0 sub pages listed, so wasn't removed in the first removal.

I guess it comes down to whether it's worth the extra time using the tool vs posting to the root domains in your blast.
 
You were right Maruk, the blogengine yielded 89 backlinks out of 550k harvested haha!

But, I didnt find something great, of the failed posted, I did a pagerank check and have a bunch of great blogs to comment manually on. The first one list is a PR4 with only 2 comments and without a nofollow tag

Hmm, interesting.

I sometimes do the first (and sometimes second) run via a made up website and then once I've found out the AA run (after a link check) I use my actual sites.

It's all about time - finding the time to run a PR check for what you describe above.
 
Hmm, interesting.

I sometimes do the first (and sometimes second) run via a made up website and then once I've found out the AA run (after a link check) I use my actual sites.

It's all about time - finding the time to run a PR check for what you describe above.

Well you can run a second instance of scrapebox, it is perfectly capable of that.(You have to copy the scrapebox folder to do it)

While I was harvesting the 550k I was also using the pinger to ping a forum I just opened to get hits and appear active. There's no reason why you could have a second list of proxies checking pagerank and filtering lists separately in another instance.


The only limitations are bandwidth. I'm on 50mb and I found it fine.
 
Well you can run a second instance of scrapebox, it is perfectly capable of that.(You have to copy the scrapebox folder to do it)

While I was harvesting the 550k I was also using the pinger to ping a forum I just opened to get hits and appear active. There's no reason why you could have a second list of proxies checking pagerank and filtering lists separately in another instance.


The only limitations are bandwidth. I'm on 50mb and I found it fine.


Yeah I do have 2 instances running. I've read not to harvest and post at the same time, but 2 harvest sessions is ok.

So just trying to work out what each instance can be doing whilst I'm away. I'm using a VPS so want to get it in such a way I can just log off and let it run during the night.

At this moment I have Instance 1 harvesting and Instance 2 checking the links from my previous blast.
 
Last edited:
Okay guys if you don't mind I would like to keep this thread about the casestudy and not general SB thingies.

Thanks!

Mark
 
Think this is a bit over the top to be honest.

Sorry to burst your bubble but this thread shows why Scrapebox isn't a good tool anymore.

Your #17 after almost 10 days? For a 2900 search keyword??? Sorry but that sucks. You can get to #1 in a few days on such a low competition KW if you just spam Xrumer.

The problem with Scrapebox and what you're doing is:

1. You're using names, you need anchor text as the name to increase serps for that keyword.
2. No follow links suck balls now. Google has clearly put the KO to blog comments.

I really think a shitty do-follow link will out perform a high PR nofollow link in serps now...

Sorry to burst your bubble but this thread shows why Scrapebox isn't a good tool anymore.

Sorry but I don't think you are busting anyones bubble here. This is one case study ( and a very good one ) that is actually testing something out. The value is in what it shows, the OP is not making any claims one way or the other, just showing results.

Your #17 after almost 10 days? For a 2900 search keyword??? Sorry but that sucks. You can get to #1 in a few days on such a low competition KW if you just spam Xrumer.


It doesn't suck, is there an easier ways to get there ?, maybe, but that is still not bad. As for making a claim you can get to #1 in a few days , frankly you can't make that claim, it has nothing to do with the low comp, if no1 is the brand , or a as we often find wikipedia, you don't knock them out in a few days. If you mean page 1, then maybe. I can give you a case study where Xrumer did nothing for a term of similar competition, but I am not going to come here and say Xrumer is a waste of time, each test always depends on so many variables, which includes the on page content, age of domain and current link profile. But with recent tests I have done , my view is certainly different to yours. Again I measure time of getting those xrumer links indexed, and the number it takes to move the site and now more than ever , on the my very latest tests, I don't agree with what you have said.

The problem with Scrapebox and what you're doing is:

1. You're using names, you need anchor text as the name to increase serps for that keyword.
2. No follow links suck balls now. Google has clearly put the KO to blog comments.

Isn't this one of the things he is trying to show ? the point of the case study is to look at it and debate it, again, you seem to be saying it without anything showing why you are right. I think a better question is to ask Mark how many of these backlinks he has now are no follow, as that would show these links maybe don't " suck balls " as much as you think they do ?

I really think a shitty do-follow link will out perform a high PR nofollow link in serps now...

Well that is what were trying to get an idea of, but he's doing it, rather than thinking it.

Mark great case study pal, keep it coming.
 
Last edited:
Can SB only scrape 1million URLS at a a time? I just scraped 3.5m and it only placed 1 mil in the url box -_-
 
Very interesting thread. I bought SB a while ago, just because my harvester got broken and have never used it for commenting. Now I am thinking about using it for it too.
 
great case study, i am planning to buy scrapebox and move on from auto blogs to micro niche sites after our family vacation and this is really informative and encouraging for me
 
I've got four domains to the top pages of Google using Scrapebox, so I know that this method works and keeps on working. Not got any $$ yet but I am working on raising my CTR at the moment. I think my theme is the problem so I purchase CTR Theme AND Socrates theme and will be testing between them. (Bought 100 domains on the strength).

It's just work, time and patience........the main factor being work.....:P
 
Back
Top