Constant-Content.com announced today that its “writer pool” is now available to customers. Make sure to check out the Constant-Content Writer Pool Announcement in the forum and apply for those pools that you’re interested in. It could be a fantastic opportunity to get private requests for a variety of project types.
I’m attempting to give Facebook a go. I have created a fan page and have installed a Facebook plugin. I’m hoping that I can use Facebook comments rather than the WordPress comment facility. We’ll see how it works.
It’s officially frustrating – the plugin isn’t working so well. I’m adding a code directly from Facebook that will add comments to this post only. Anyone know of a reliable WordPress plugin for Facebook comments where you don’t have to enter a code manually each time?
Constant-Content recently added “writers pools” to the site and is currently accepting applications from writers to be considered for several different pools:
In addition to the categories above, Constant-Content needs writers for pools covering different languages including: English, French, Spanish, and German. It also has pools dedicated to regional writing for the following regions: Canada, UK and Europe, and Australia.
I don’t expect this to replace the request system though it could affect whether or not a writer is considered for private requests. For example, newer Constant-Content customers may not know which writers to request articles from while long-time customers will already have their favorites based on past experiences. By creating writers pools, Constant-Content will be able to help newer customers find writers who specialize in a given area, are currently active, and who have demonstrated that they can consistently meet Constant-Content’s strict requirements.
In order to be featured in a Constant-Content writers pool, you must apply, send a relevant sample of your writing, and have a 60 percent article approval rating. The application process is straightforward in that it involves clicking the Apply button, filling out a Web form with your details, and waiting to hear back from Constant-Content.
As far as I can tell, the writers pool hasn’t been rolled out officially to customers. This makes sense as they must first fill the pools with writers. Have you applied?
Looks like Constant-Content.com has been busy adding some new features. For example, did you know that when Constant-Content rejects an article for revisions, it’s no longer “purged from the system”? Here’s a quick snapshot of some of the changes I’ve noticed lately:
Article Revisions
In the past, if an article was rejected it was completely deleted from the Constant-Content servers. This meant that not only did you have to correct whatever mistakes the article may have had, you’d also need to recreate the short summary, article excerpt, word count, prices, keywords, and other details. Now, most of the information remains. From what I understand, you need to correct the document and reupload it to the server.
Summaries of Current Requests
Constant-Content now sends an email detailing the latest public requests along with “good opportunities.” It looks like CC defines good opportunities as requests that are over a week old with few articles submitted to them.
Customers Can Now Add Attachments
I like this one! Oftentimes customers will have documents (such as writers guidelines or source information) that aren’t appropriate to post on the Web or too big to copy and paste into the request form. Now, they can attach the files to the request.
I noticed a few interesting public requests on Constant-Content.com today. If you saw them too but are hesitant to write for them, let me ask you this: What’s the worst that can happen?
One: Your article might not be accepted by Constant-Content.
Two: The customer might not buy it.
Sure, there’s a risk in writing for a public request on Constant-Content. The editors may reject it for typos, grammar errors, spelling mistakes, and so on. If the article isn’t acceptable as is, then it’s not ready for sale. Make the changes and resubmit. If you still can’t get the article approved by CC’s editorial team but feel it’s good enough to use elsewhere such as your personal blog or one of the revenue share sites, your efforts haven’t been completely wasted.
Because of the nature of Constant-Content’s public request system, there’s always a risk that the customer won’t buy your article no matter how well written or affordably priced it may be. When this happens, you can either leave the article for sale (other buyers do come around so all is not lost) on CC or you can remove it and submit it somewhere else. You could even offer if for usage rights on CC and then use it elsewhere under a non-exclusive license. For example, you could use it on EzineArticles, post it to Associated Content, use it as a newsletter article, or use it on your blog.
Successfully selling articles to a public request means money in your PayPal account! Not only that, you’ve just made an initial impression on a person that buys content which could lead to future sales. Some of my best, regular customers are people who placed public requests and liked my submissions. Five years later, I’m still writing articles for them. In my opinion, that’s the best and well worth the risk!
