<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How To Get Your Ezine Articles Accepted In 30 Minutes!</title>
	<atom:link href="http://kickbuttmarketing.com/blog/25/articlez/feed/" rel="self" type="application/rss+xml" />
	<link>http://kickbuttmarketing.com/blog/25/articlez/</link>
	<description></description>
	<lastBuildDate>Mon, 07 Jun 2010 10:52:33 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Matt \\&#34;Wiggy\\&#34; Wiggins</title>
		<link>http://kickbuttmarketing.com/blog/25/articlez/comment-page-1/#comment-14</link>
		<dc:creator>Matt \\&#34;Wiggy\\&#34; Wiggins</dc:creator>
		<pubDate>Sun, 13 Dec 2009 20:24:01 +0000</pubDate>
		<guid isPermaLink="false">http://kickbuttmarketing.com/blog/?p=25#comment-14</guid>
		<description>What else does the Premium Membership do for you outside of getting your articles accepted quickly?

I ask b/c ezine seems to have to be approached one of 2 ways - you either have to treat an article as if it\\\&#039;s a property (for lack of a better term).  In other words, you want that specific ezine article to rank well in the SEs itself.  Which means applying off-page SEO (to a certain extent) to that article.  A great way to do that (something I\\\&#039;m testing) is that I have one batch of articles I submit to ezine.  I have another batch I submit to a whole bunch of other articles directories.  

In my resource box for each submission to the other directories, I link not only back to my site, but also to the ezine article I want to rank high.  Of course, links are anchor text appropriate.

The other method is that you pretty much have to continually carpet bomb ezine with tons of articles so that you\\\&#039;re consistently in the \\\&#039;recently submitted\\&quot; section, as well as on the main page of ezine itself.  I\\\&#039;ve read some grey/black hat ways of getting your articles in the \\\&#039;most viewed\\\&#039; section as well, but I won\\\&#039;t talk about that kinda stuff here...

Wiggy
http://www.workingclasscardioworkout.com
http://www.workingclassfitness.com</description>
		<content:encoded><![CDATA[<p>What else does the Premium Membership do for you outside of getting your articles accepted quickly?</p>
<p>I ask b/c ezine seems to have to be approached one of 2 ways &#8211; you either have to treat an article as if it\\\&#8217;s a property (for lack of a better term).  In other words, you want that specific ezine article to rank well in the SEs itself.  Which means applying off-page SEO (to a certain extent) to that article.  A great way to do that (something I\\\&#8217;m testing) is that I have one batch of articles I submit to ezine.  I have another batch I submit to a whole bunch of other articles directories.  </p>
<p>In my resource box for each submission to the other directories, I link not only back to my site, but also to the ezine article I want to rank high.  Of course, links are anchor text appropriate.</p>
<p>The other method is that you pretty much have to continually carpet bomb ezine with tons of articles so that you\\\&#8217;re consistently in the \\\&#8217;recently submitted\\&amp;quot; section, as well as on the main page of ezine itself.  I\\\&#8217;ve read some grey/black hat ways of getting your articles in the \\\&#8217;most viewed\\\&#8217; section as well, but I won\\\&#8217;t talk about that kinda stuff here&#8230;</p>
<p>Wiggy<br />
<a href="http://www.workingclasscardioworkout.com" rel="nofollow">http://www.workingclasscardioworkout.com</a><br />
<a href="http://www.workingclassfitness.com" rel="nofollow">http://www.workingclassfitness.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
