<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>ejcross.com &#187; PayPerPost</title>
	<atom:link href="http://ejcross.com/category/payperpost/feed" rel="self" type="application/rss+xml" />
	<link>http://ejcross.com</link>
	<description>Uncommon Sense and Thoughts</description>
	<pubDate>Wed, 12 Nov 2008 15:39:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
	<language>en</language>
			<item>
		<title>My PayPerPost Experience</title>
		<link>http://ejcross.com/2007/11/13/my-payperpost-experience/</link>
		<comments>http://ejcross.com/2007/11/13/my-payperpost-experience/#comments</comments>
		<pubDate>Wed, 14 Nov 2007 02:10:38 +0000</pubDate>
		<dc:creator>elliott</dc:creator>
		
		<category><![CDATA[PayPerPost]]></category>

		<category><![CDATA[blogging]]></category>

		<category><![CDATA[integrity]]></category>

		<category><![CDATA[review]]></category>

		<guid isPermaLink="false">http://ejcross.com/2007/11/13/my-payperpost-experience/</guid>
		<description><![CDATA[A couple of weeks ago, Darren Rowse of problogger.net wrote an article about how <a href="http://www.problogger.net/archives/2007/11/01/payperpost-inc-changes-its-name-to-izea/">PayPerPost is changing it's name to Izea</a> and it got me thinking about trying out PayPerPost.

I had thought about trying it out before, but with a PR 0, I knew I didn't stand a chance.  Now that I have a PR4, I thought I would look into it a little more and let you know what I have learned, what I like and don't like, and how I think it will work for this site.]]></description>
			<content:encoded><![CDATA[<p>A couple of weeks ago, Darren Rowse of problogger.net wrote an article about how PayPerPost is changing it&#8217;s name to Izea and it got me thinking about trying out PayPerPost.</p>
<p>I had thought about trying it out before, but with a PR 0, I knew I didn&#8217;t stand a chance.  Now that I have a PR4, I thought I would look into it a little more and let you know what I have learned, what I like and don&#8217;t like, and how I think it will work for this site.</p>
<h3>What I have learned so far</h3>
<p>When I first signed up and submitted my blog, I was impressed with the interface of the PayPerPost site.  It was relatively simple and easy on the eyes.  The areas of importance were easily identifiable and you can quickly navigate around the site.</p>
<p>After being rejected on the first submission, I followed the directions that were sent in the email and resubmitted my blog for review again.  I was accepted this time, so I would consider it a relatively minor bump in the road.</p>
<p>PayPerPost is looking for sites that have an appeal to their advertisers, have some traffic (the more the better) and have a good Page Rank and Alexa score.  I would not recommend this for someone with a relatively new blog as it would probably be rejected.  I would suggest that if you aren&#8217;t sure how your site would do with PayPerPost that you submit it anyways, the worse being that they would reject it and you can try again later.</p>
<h3>What I like so far</h3>
<p><img src='http://ejcross.com/wp-content/uploads/2007/11/pppsite.jpg' alt='payperpost site image' width="450" height="67" /></p>
<p>The interface, as I said earlier, is clean and simple to navigate around.  The site loads quickly between pages and has simple and easy to understand layouts.  Overall, a very nice and easy site to get around on.</p>
<p>There are three primary areas to the site when you log in.  </p>
<p>You have the &#8220;Dashboard&#8221; which is your main page with summary information on it, the &#8220;Opportunities&#8221; tab which has posts that are available to you if you meet the qualifications, and then the &#8220;My Account Settings&#8221; tab which controls your blogs, submitted posts and other tools for your use.</p>
<h3>What I haven&#8217;t liked so far</h3>
<p>The one thing that annoyed me about PayPerPost so far is they use &#8220;tickets&#8221; to track your issues when you contact customer support.  I didn&#8217;t know this, and after my blog was rejected the first time, I wasn&#8217;t aware of this fact.  </p>
<p>So, after not hearing anything from them, I sent three messages through the contact form for customer service before I realized that they were responding to me and I just didn&#8217;t know it.  I hope someone from PayPerPost reads this and can maybe make a site change to help make it easier to get to your tickets.</p>
<h3>In conclusion</h3>
<p>So, this is my first post for PayPerPost.  I want each of you that read this to understand one simple thing from me.  I will not sell out and write about things that I don&#8217;t believe in, that would violate my morals or integrity, or that I haven&#8217;t reviewed and feel it is worthy to write about.</p>
<p>I feel strongly about blogging with integrity and would not do anything to trash my reputation or to make you feel that I have cheated you.  If I ever do, please let me know.  I feel that good, honest reviews of products are worth the time, especially if it helps someone else.</p>
<p>With that said (steps down from soapbox), I&#8217;m not sure how active I will be with PayPerPost, but I figure I will try it out and see what happens.  Why don&#8217;t you check it out if you are interested and <a href="http://payperpost.com/bloggers/get-paid-to-blog.html" rel="nofollow">get paid to blog</a> on your site.</p>
<p><a href="http://www.payperpost.com/?utm_source=opportunity&#038;utm_medium=disclosure%2Bbadge" rel="nofollow"><img src="http://tinyurl.com/2er3eu" border="0"/></a></p>
<p><img src="http://tinyurl.com/2bvqr8" /></p>
        <p style="text-align:center;">&copy; ejcross.com - visit <a href="http://ejcross.com">ejcross.com</a> for more great content.</p>   <br />
                                 ]]></content:encoded>
			<wfw:commentRss>http://ejcross.com/2007/11/13/my-payperpost-experience/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
