How many posts per day would you do with your autoblogs and what sort of topics would you choose? I've never had good results with autoblogs.
We've done it different ways depending on the type of autoblog.
Our good ones usually are updated no more than once or twice a day and made to look like they are real blogs. We make appx. half our articles not link out in any way, and the other half will link up to a ranking site of some sort. Some of them exist solely for ranking other sites, and they are all in a broad related niche (maybe health) so that any health sites that need ranking can get relevant high quality links.
The others autoblogs that don't exist mostly to prop up other sites are in more narrow niches and post more frequently since it is a little more acceptable if they get burned. Unfortunately I can't give exact niches, but I usually look for things with as little competition as possible that still have enough volume to return a positive ROI.
We've also had some success with complete churn and burns. For these autoblogs we pick a very general topics, and spin 50+ articles per day. In one example, we had a script that pulled the most recent article on Google News every 5-10 minutes, spun it and posted it. We started actually getting listed in Google News ourselves, got mentioned on Twitter, and had a couple sites reference us that brought in 1,000+ visits at a time. In the end the site stopped ranking, but when it was ranking we made more than enough money to cover the autoblogs creation. Once you can get autoblogs to pay their own rent, it simply becomes a numbers game after that, and we've had success with all three strategies listed above.
As we get a little closer to releasing tools that will help more with autoblogging we are going to release a very detailed case study on this, and I'll be sure to update this thread when that happens.
Do I need to adhere to a particular end of line character?
If I were to throw 10K words at the Turing spinner - which I assume is probably a bit slower then the regular api, how long might the spin take?
How many versions of a sentence does setting "returnspin=true" give as a result?
For the API, I would use "\n" for a newline. 10k words right now might talk around half an hour to run in the API. For your last question, "returnspin=true" only returns one spin. If you want multiple variations I would suggest having the spintax returned and then spinning it on your end. At that point you can spin it manually however many times you want.
Issue is resolved and I just signed myself a deal for half a year after observing that the quality and readability is really good along with the uniqueness that WordAI brings. Quality is good enough because it passed copyscape while being readable but the area of improvement is the uniqueness level.
Question: Are you planning to let WordAI bring in more sentence spins? I find them to be a treat since they make the sentence structure of the output totally new but I notice a sentence spin is only added like 10% - 20% of the time.
Another question/suggestion: How about paragraph spins? Would this be possible in the future?
Glad everything got sorted out!
We are working on adding more sentence spinning and we should have a couple good improvements released over the next couple months. We have a couple sentence rewrites that are working in our development environment, however they aren't quite readable enough for us to roll them live. We are working on a couple changes that should let us do a better job figuring out whether a sentence rewrite makes sense or not. Once that is done, we will start adding a lot more different types of automatic sentence rewrites since WordAi will be able to do a much better job figuring out whether they make sense.
Paragraph spinning is something we are planning on adding very soon. We are developing an algorithm that can intelligently figure out what paragraphs can be moved around and what paragraphs can't. This feature will very likely be released in February, and should do a great job increasing uniqueness (while still having your article be readable). Stay tuned for more info!