<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Blogging: Tips for a successful post</title><link>http://blogs.msdn.com/kathykam/archive/2006/04/17/576837.aspx</link><description>As a relatively new blogger, I am still learning what are good topics to blog. One of the metric I used to see how I do is the data http://blogs.msdn.com provides about how many people read my post (Aggregated and normal). Krzysztof and I had a nice long</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Blogging: Tips for a successful post</title><link>http://blogs.msdn.com/kathykam/archive/2006/04/17/576837.aspx#577798</link><pubDate>Tue, 18 Apr 2006 00:30:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:577798</guid><dc:creator>Eber Irigoyen</dc:creator><description>I look for quality and consistency on the topic</description></item><item><title>re: Blogging: Tips for a successful post</title><link>http://blogs.msdn.com/kathykam/archive/2006/04/17/576837.aspx#578008</link><pubDate>Tue, 18 Apr 2006 08:37:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:578008</guid><dc:creator>KathyKam</dc:creator><description>Hi Eber,&lt;br&gt;&lt;br&gt;I agree with quality, but I would say it more concretly like.. &amp;quot;Every post should have value.&amp;quot; However, some of the topics requires quite a bit of homework, like my string format post. An annoucment post like Rotor 2.0 ship have value, but require less homework. Do you include annoucement post as &amp;quot;quality&amp;quot; posts?&lt;br&gt;&lt;br&gt;Kathy</description></item><item><title>Interesting Finds</title><link>http://blogs.msdn.com/kathykam/archive/2006/04/17/576837.aspx#578136</link><pubDate>Tue, 18 Apr 2006 13:04:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:578136</guid><dc:creator>Jason Haley</dc:creator><description /></item><item><title>Interesting Finds</title><link>http://blogs.msdn.com/kathykam/archive/2006/04/17/576837.aspx#578206</link><pubDate>Tue, 18 Apr 2006 15:25:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:578206</guid><dc:creator>Jason Haley</dc:creator><description /></item><item><title>re: Blogging: Tips for a successful post</title><link>http://blogs.msdn.com/kathykam/archive/2006/04/17/576837.aspx#578217</link><pubDate>Tue, 18 Apr 2006 15:43:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:578217</guid><dc:creator>Kevin Daly</dc:creator><description>You're definitely right that it's all in the title.
&lt;br&gt;Although I once naively posted an entry titled &amp;quot;Fooling around with the Atom API&amp;quot; and got *way* more hits than I'd anticipated. It turns out lots of people were Googling for &amp;quot;fooling around&amp;quot;.
&lt;br&gt;
&lt;br&gt;Dirty little devils.</description></item><item><title>re: Blogging: Tips for a successful post</title><link>http://blogs.msdn.com/kathykam/archive/2006/04/17/576837.aspx#578303</link><pubDate>Tue, 18 Apr 2006 18:21:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:578303</guid><dc:creator>Eber Irigoyen</dc:creator><description>sure there is some value on announcements, but then I get another 50 blogs with the same thing, so I don't know
&lt;br&gt;
&lt;br&gt;on the other hand, if you follow up with some stuff about it, then it adds value with consistency (and hopefully quality)</description></item><item><title>re: Blogging: Tips for a successful post</title><link>http://blogs.msdn.com/kathykam/archive/2006/04/17/576837.aspx#578306</link><pubDate>Tue, 18 Apr 2006 18:24:55 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:578306</guid><dc:creator>Wes</dc:creator><description>I just try to get as many search terms as possible in my titles so people can pick them up easily on search engines. That is where I get most of my hits from, and that is my target audience. </description></item><item><title>re: Blogging: Tips for a successful post</title><link>http://blogs.msdn.com/kathykam/archive/2006/04/17/576837.aspx#578484</link><pubDate>Tue, 18 Apr 2006 22:39:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:578484</guid><dc:creator>KathyKam</dc:creator><description>Hey Kevin,&lt;br&gt;&lt;br&gt;That's really funny! :) Our blogging title should follow the spammer's tactics. &lt;br&gt;&lt;br&gt;How do you like this title?&lt;br&gt;&amp;quot;How to make $1 million dollars with BCL APIs&amp;quot;. :D&lt;br&gt;&lt;br&gt;Now seriously, I personally find it more fullfilling to establish a loyal readership rather than depending the one off &amp;quot;google keyword&amp;quot; to get me my readers. This way, we can have conversation and discussions! :)&lt;br&gt;&lt;br&gt;I think my readers will leave if I have too many post falsely promising get rich quick or diet schemes! &lt;br&gt;&lt;br&gt;Cheers,&lt;br&gt;Kathy</description></item><item><title>re: Blogging: Tips for a successful post</title><link>http://blogs.msdn.com/kathykam/archive/2006/04/17/576837.aspx#630692</link><pubDate>Wed, 14 Jun 2006 12:30:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:630692</guid><dc:creator>Kaisa M. Lindahl Lervik</dc:creator><description>Interesting titles are essential. Giving a clue what your post is about is number 1. &lt;br&gt;&lt;br&gt;But it sort of winds down to why you blog. Do you blog to have loyal readers, or to share information to people looking for answers. If you blog to share information, like Wes and me, your title needs to have some kind of hook for the search engines. When googling, I stay far away from titles saying &amp;quot;Get rich using SQL Express&amp;quot;. (Or maybe not, I might get curious, and read the post.)&lt;br&gt;&lt;br&gt;I try to add at least the product name of things I blog about, to give people a chance to know what I'm writing about. Makes picking up my posts. I also try to include error messages and event IDs when writing about how I've solved tricky things, and link to resources for solutions. This is what I like to find in other people's blog posts when I'm searching for solutions.&lt;br&gt;&lt;br&gt;I try to write a techie blog. But the blog post I've got most hits on, is the one called &amp;quot;Standing in line to see FC Barcelona vs. Chelsea FC&amp;quot;. It was popular around February 2005, and became even more popular in January 2006... So much for writing about techie stuff. ;)</description></item><item><title> Kathy Kam Blogging Tips for a successful post | Paid Surveys</title><link>http://blogs.msdn.com/kathykam/archive/2006/04/17/576837.aspx#9661884</link><pubDate>Sat, 30 May 2009 03:47:46 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9661884</guid><dc:creator> Kathy Kam Blogging Tips for a successful post | Paid Surveys</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://paidsurveyshub.info/story.php?title=kathy-kam-blogging-tips-for-a-successful-post"&gt;http://paidsurveyshub.info/story.php?title=kathy-kam-blogging-tips-for-a-successful-post&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Kathy Kam Blogging Tips for a successful post | Green Tea Fat Burner</title><link>http://blogs.msdn.com/kathykam/archive/2006/04/17/576837.aspx#9706298</link><pubDate>Mon, 08 Jun 2009 05:06:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9706298</guid><dc:creator> Kathy Kam Blogging Tips for a successful post | Green Tea Fat Burner</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://greenteafatburner.info/story.php?id=2031"&gt;http://greenteafatburner.info/story.php?id=2031&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>