<?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: 10 Reasons To Edit Your Published Blog Posts	</title>
	<atom:link href="https://www.searchenginepeople.com/blog/10-reasons-for-editing-your-published-blog-posts.html/feed" rel="self" type="application/rss+xml" />
	<link>https://www.searchenginepeople.com/blog/10-reasons-for-editing-your-published-blog-posts.html?utm_source=feed&#038;utm_medium=feed&#038;utm_campaign=feed</link>
	<description>Canada&#039;s Search and Social Media Authority</description>
	<lastBuildDate>Sat, 28 Jan 2017 01:39:28 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Pozycjonowanie		</title>
		<link>https://www.searchenginepeople.com/blog/10-reasons-for-editing-your-published-blog-posts.html/comment-page-1#comment-32900</link>

		<dc:creator><![CDATA[Pozycjonowanie]]></dc:creator>
		<pubDate>Tue, 05 Oct 2010 23:02:05 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=3941#comment-32900</guid>

					<description><![CDATA[Your blog was the first place that told me the answer for what I was looking for. Thanks.]]></description>
			<content:encoded><![CDATA[<p>Your blog was the first place that told me the answer for what I was looking for. Thanks.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Cool Gifts		</title>
		<link>https://www.searchenginepeople.com/blog/10-reasons-for-editing-your-published-blog-posts.html/comment-page-1#comment-9360</link>

		<dc:creator><![CDATA[Cool Gifts]]></dc:creator>
		<pubDate>Thu, 25 Jun 2009 02:28:18 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=3941#comment-9360</guid>

					<description><![CDATA[I think it&#039;s also good to go back and edit your older posts. You might find many of them are still very relevant. You may just need to update a few things or give a new example.]]></description>
			<content:encoded><![CDATA[<p>I think it&#8217;s also good to go back and edit your older posts. You might find many of them are still very relevant. You may just need to update a few things or give a new example.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ejvind		</title>
		<link>https://www.searchenginepeople.com/blog/10-reasons-for-editing-your-published-blog-posts.html/comment-page-1#comment-9320</link>

		<dc:creator><![CDATA[Ejvind]]></dc:creator>
		<pubDate>Mon, 22 Jun 2009 10:03:03 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=3941#comment-9320</guid>

					<description><![CDATA[I feel like Tony that we are &quot;Writing history&quot; Sometimes it is not in the best interest of the user to have corrcted information, since this may confuse (if I have read the &quot;old&quot; blog post first) In that case I would prefer to be able to see the corrections made.   

On the other hand I have deleted a blog post once, because I had written it while being very angry, and after cooling down could see that I was doing both me and my target a disfavor.

Thanks for a great topic.]]></description>
			<content:encoded><![CDATA[<p>I feel like Tony that we are &#8220;Writing history&#8221; Sometimes it is not in the best interest of the user to have corrcted information, since this may confuse (if I have read the &#8220;old&#8221; blog post first) In that case I would prefer to be able to see the corrections made.   </p>
<p>On the other hand I have deleted a blog post once, because I had written it while being very angry, and after cooling down could see that I was doing both me and my target a disfavor.</p>
<p>Thanks for a great topic.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Tvents		</title>
		<link>https://www.searchenginepeople.com/blog/10-reasons-for-editing-your-published-blog-posts.html/comment-page-1#comment-9318</link>

		<dc:creator><![CDATA[Tvents]]></dc:creator>
		<pubDate>Mon, 22 Jun 2009 05:53:38 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=3941#comment-9318</guid>

					<description><![CDATA[The blog editing is needed. Of course, this is related to the readers. They will continue visiting the blog with regular editions. I hope I can continually implement the blog editing.]]></description>
			<content:encoded><![CDATA[<p>The blog editing is needed. Of course, this is related to the readers. They will continue visiting the blog with regular editions. I hope I can continually implement the blog editing.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: The Agra Indian		</title>
		<link>https://www.searchenginepeople.com/blog/10-reasons-for-editing-your-published-blog-posts.html/comment-page-1#comment-9314</link>

		<dc:creator><![CDATA[The Agra Indian]]></dc:creator>
		<pubDate>Mon, 22 Jun 2009 01:24:27 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=3941#comment-9314</guid>

					<description><![CDATA[Your advice is really great Barry.

I have noticed many times that comments on posts have something that might be added to the post content but seriously I have never thought of re editing it.

Now I have taken your words will do when ever I will find any valued additions. I am sure search engine bots will also love it.]]></description>
			<content:encoded><![CDATA[<p>Your advice is really great Barry.</p>
<p>I have noticed many times that comments on posts have something that might be added to the post content but seriously I have never thought of re editing it.</p>
<p>Now I have taken your words will do when ever I will find any valued additions. I am sure search engine bots will also love it.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: MyTechnologyGuide		</title>
		<link>https://www.searchenginepeople.com/blog/10-reasons-for-editing-your-published-blog-posts.html/comment-page-1#comment-9311</link>

		<dc:creator><![CDATA[MyTechnologyGuide]]></dc:creator>
		<pubDate>Sun, 21 Jun 2009 20:38:31 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=3941#comment-9311</guid>

					<description><![CDATA[Great tips! Thanks this will definitely help me as a blogger to keep my blog shining! :-)]]></description>
			<content:encoded><![CDATA[<p>Great tips! Thanks this will definitely help me as a blogger to keep my blog shining! 🙂</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: SpokaneREMarketing		</title>
		<link>https://www.searchenginepeople.com/blog/10-reasons-for-editing-your-published-blog-posts.html/comment-page-1#comment-9283</link>

		<dc:creator><![CDATA[SpokaneREMarketing]]></dc:creator>
		<pubDate>Fri, 19 Jun 2009 14:25:47 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=3941#comment-9283</guid>

					<description><![CDATA[Great write up.  I have always avoided making changes to my blog posts once published but I have never had a good reason for belief. I appreciate you taking the time to give me a reason to change my ways.]]></description>
			<content:encoded><![CDATA[<p>Great write up.  I have always avoided making changes to my blog posts once published but I have never had a good reason for belief. I appreciate you taking the time to give me a reason to change my ways.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: DansMuayThaiMMA		</title>
		<link>https://www.searchenginepeople.com/blog/10-reasons-for-editing-your-published-blog-posts.html/comment-page-1#comment-9267</link>

		<dc:creator><![CDATA[DansMuayThaiMMA]]></dc:creator>
		<pubDate>Fri, 19 Jun 2009 01:34:16 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=3941#comment-9267</guid>

					<description><![CDATA[I tried to edit to incorporate feedback from my comments all the time.  I also make sure I always comment back to my readers to make them feel like it&#039;s an interactive experience to visit my blog.

Great post man.

Dan]]></description>
			<content:encoded><![CDATA[<p>I tried to edit to incorporate feedback from my comments all the time.  I also make sure I always comment back to my readers to make them feel like it&#8217;s an interactive experience to visit my blog.</p>
<p>Great post man.</p>
<p>Dan</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Barry Welford		</title>
		<link>https://www.searchenginepeople.com/blog/10-reasons-for-editing-your-published-blog-posts.html/comment-page-1#comment-9264</link>

		<dc:creator><![CDATA[Barry Welford]]></dc:creator>
		<pubDate>Thu, 18 Jun 2009 22:08:28 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=3941#comment-9264</guid>

					<description><![CDATA[That&#039;s an interesting viewpoint, Tony.  I do not feel I am creating history.  Rather I&#039;m creating something that should be the best it can be for future visitors.  Some even suggest that blog posts should not carry dates since they should be, in a sense, timeless.]]></description>
			<content:encoded><![CDATA[<p>That&#8217;s an interesting viewpoint, Tony.  I do not feel I am creating history.  Rather I&#8217;m creating something that should be the best it can be for future visitors.  Some even suggest that blog posts should not carry dates since they should be, in a sense, timeless.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Tony Lawrence		</title>
		<link>https://www.searchenginepeople.com/blog/10-reasons-for-editing-your-published-blog-posts.html/comment-page-1#comment-9259</link>

		<dc:creator><![CDATA[Tony Lawrence]]></dc:creator>
		<pubDate>Thu, 18 Jun 2009 18:12:49 +0000</pubDate>
		<guid isPermaLink="false">https://www.searchenginepeople.com/?p=3941#comment-9259</guid>

					<description><![CDATA[Yeah, correcting typos is fine, but when correcting true mistakes, I prefer to do that with a comment.  Sometimes, if it&#039;s particularly important that people not be misled, I will make that an in-line comment or if it&#039;s really critical I might use strikethrough on the original text and then add my new text in bold.

The only time I&#039;ll actually edit is when the mistake was a mistake of communication - where I didn&#039;t express myself clearly and therefor apparently gave wrong information.  Even then I hesitate because I just don&#039;t feel right &quot;rewriting history&quot;.   Annotating, fine, but rewriting makes me uncomfortable.]]></description>
			<content:encoded><![CDATA[<p>Yeah, correcting typos is fine, but when correcting true mistakes, I prefer to do that with a comment.  Sometimes, if it&#8217;s particularly important that people not be misled, I will make that an in-line comment or if it&#8217;s really critical I might use strikethrough on the original text and then add my new text in bold.</p>
<p>The only time I&#8217;ll actually edit is when the mistake was a mistake of communication &#8211; where I didn&#8217;t express myself clearly and therefor apparently gave wrong information.  Even then I hesitate because I just don&#8217;t feel right &#8220;rewriting history&#8221;.   Annotating, fine, but rewriting makes me uncomfortable.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
