A few questions:
1. How many unique forums in the service?
2. Have all the forums been checked that they have publicly viewable and crawlable profiles?
3. Any idea of what percentage of the forum profiles are dofollow?
4. Could you explain what the backblaster does?
1) currently 20k or so with some more being added later today, though I am not sure what the rate of duplication will be between my current list and the one I am going to merge with it (which is 25k).
2) All verified with scrapebox with user agent set to that of a popular search engine
3) Not sure, the vast majority are do follow, but I really cannot quantify it
4) It creates backlinks in forum profiles, but gives a lot more control and flexibility than other services. Keyword targeting is very different from other services having originally been designed for mass secondary linking or backlink boosting.
How I use it is like this:
- Set up blog with plugin
- Add plugin into BB project
- Set to "import trackbacks daily"
- Set up keyword filters (which can map as yet UNKNOWN urls)
- Deep link by blog using blog networks, article marketing robot / demon etc
What happens then is:
- Blog networks / AMA runs send trackbacks to my posts
- BackBlasts imports these URLs via the Wordpress plugin each day and adds them to its list
- BackBlasts maps the keywords onto these urls according to the filters I defined
- BackBlasts sends links out to the blog networks / AMA runs to help with indexing etc
That is one way to use the service.
Another is to drip links into micro sites slowly, or promote other sites directly.
Where the service differs in this regard is the level of granularity.
With BackBlasts you control how many links you sent to each project on each day of the week. The constraints are that you must send between 100 and 2000 per project (assuming you have 2k account)
So, if you have a 500 per day account, you can do up to 5 x 100 links per project per day, and if you want to a different set of 5 projects each day, making 35 different projects per week.
Each project gets its own report each time it is run.
This gives a more even spread, a "true drip" effect. Other services force you to send all your daily quota in a single "blast", so you either have to roll all your projects together into one big spin mangler (which is hard to edit afterwards), or send site specific blasts very infrequently. For example, say you have a 2k account and want to send 100 links per day to a given site in isolation from your other projects... in other systems you would have to send 2k every 20 days, this one lets you send 100 per day evenly.
If you are using LinkLicious integration (which we just added) a 2k blast every 20 days is perhaps not the best approach.
What this system does lack, due to this approach is long term calendar scheduling, which makes "velocity" hard to set going out into the future. This system uses a "rolling week". If you want velocity then you would have to log in once a week to tweak your schedule.
Its a different approach, one that suits the way I work (it was originally a private tool that grew). If you work the same way as me you will like it, but, there are many different approaches to this stuff, its by no means a "one size fits all" kind of scenario.