<?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"
	>
<channel>
	<title>Comments on: Blog-Tipping: Hamelife</title>
	<atom:link href="http://www.douglaskarr.com/2007/07/08/blog-tipping-7/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.marketingtechblog.com/2007/07/08/blog-tipping-7/</link>
	<description>conversation and resources on marketing, social media, development, and wordpress</description>
	<pubDate>Fri, 29 Aug 2008 03:05:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Douglas Karr</title>
		<link>http://www.marketingtechblog.com/2007/07/08/blog-tipping-7/#comment-51053</link>
		<dc:creator>Douglas Karr</dc:creator>
		<pubDate>Sun, 08 Jul 2007 21:41:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.douglaskarr.com/2007/07/08/blog-tipping-7/#comment-51053</guid>
		<description>Hi Rory,

I would recommend putting your robots.txt file in your root directory.  You could get a little fancy, though, and put a redirect in place in your root .htaccess file.

Redirect robots.txt http://hamelife.com/wpblog/robots.txt

I would still put an XML sitemap in place as well using the plugin I specified in 1.  An XML sitemap is in accordance with the Sitemap standard.  This sitemap will rebuild with every post and automatically ping the search engines as well.  It's very good.

If you put in the sitemap and it's in the wpblog directory as well, you can also put a redirect to it as well:

Redirect sitemap.xml http://hamelife.com/wpblog/sitemap.xml

Use caution and backup your htaccess file (it may be hidden so be sure to view hidden files with your FTP software) in case you hose it up!

Then be sure to add the sitemap line to your robots.txt file.  If you've got the redirect line in you htaccess file, you could use either URI... I would probably default to the literal, though:
Sitemap: http://hamelife.com/wpblog/sitemap.xml</description>
		<content:encoded><![CDATA[<div class="KonaBody">Hi Rory,</p>
<p>I would recommend putting your robots.txt file in your root directory.  You could get a little fancy, though, and put a redirect in place in your root .htaccess file.</p>
<p>Redirect robots.txt <a href="http://hamelife.com/wpblog/robots.txt" rel="nofollow">http://hamelife.com/wpblog/robots.txt</a></p>
<p>I would still put an XML sitemap in place as well using the plugin I specified in 1.  An XML sitemap is in accordance with the Sitemap standard.  This sitemap will rebuild with every post and automatically ping the search engines as well.  It&#8217;s very good.</p>
<p>If you put in the sitemap and it&#8217;s in the wpblog directory as well, you can also put a redirect to it as well:</p>
<p>Redirect sitemap.xml <a href="http://hamelife.com/wpblog/sitemap.xml" rel="nofollow">http://hamelife.com/wpblog/sitemap.xml</a></p>
<p>Use caution and backup your htaccess file (it may be hidden so be sure to view hidden files with your FTP software) in case you hose it up!</p>
<p>Then be sure to add the sitemap line to your robots.txt file.  If you&#8217;ve got the redirect line in you htaccess file, you could use either URI&#8230; I would probably default to the literal, though:<br />
Sitemap: <a href="http://hamelife.com/wpblog/sitemap.xml" rel="nofollow">http://hamelife.com/wpblog/sitemap.xml</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rory</title>
		<link>http://www.marketingtechblog.com/2007/07/08/blog-tipping-7/#comment-51052</link>
		<dc:creator>Rory</dc:creator>
		<pubDate>Sun, 08 Jul 2007 21:19:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.douglaskarr.com/2007/07/08/blog-tipping-7/#comment-51052</guid>
		<description>I've just implemented your 404.php, Doug. 

Try this: &lt;a href="http://hamelife.com/child/" rel="nofollow"&gt;hamelife.com/child&lt;/a&gt;

Now, &lt;em&gt;that's&lt;/em&gt; a better 404 page!

Again - Many Thanks.</description>
		<content:encoded><![CDATA[<div class="KonaBody">I&#8217;ve just implemented your 404.php, Doug. </p>
<p>Try this: <a href="http://hamelife.com/child/" rel="nofollow">hamelife.com/child</a></p>
<p>Now, <em>that&#8217;s</em> a better 404 page!</p>
<p>Again - Many Thanks.</p></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rory</title>
		<link>http://www.marketingtechblog.com/2007/07/08/blog-tipping-7/#comment-51051</link>
		<dc:creator>Rory</dc:creator>
		<pubDate>Sun, 08 Jul 2007 21:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.douglaskarr.com/2007/07/08/blog-tipping-7/#comment-51051</guid>
		<description>&lt;em&gt;Thanks for letting me tip your blog, Rory.&lt;/em&gt;

Are you kidding, Doug? I am so thankful to you for casting a helpful eye over the site. I need all the advice I can get, and I really appreciate the pointers you have given.

First off, I am blown away by your compliments. Thank you so much - they are enormously encouraging.

Now, I wonder if you could help me with your further tips:
Point #1 - The M of hamelife takes a visitor to a sitemap. I used the &lt;a href="http://cutline.tubetorial.com/use-this-simple-plug-and-play-sitemap-for-cutline/" rel="nofollow"&gt;Sitemap designed for Cutline&lt;/a&gt;. Do I have this configured correctly? Or should I move directly to Point #2 and configure my robots.txt correctly?

My robots.txt actually reads:

User-agent: *
Disallow: /wp-content/
Disallow: /wp-admin/
Disallow: /wp-includes/
Disallow: /wp-
Disallow: /feed/
Disallow: /trackback/
Disallow: /cgi-bin/

and I have it located in &lt;a href="http://hamelife.com/wpblog/robots.txt" rel="nofollow"&gt;hamelife.com/wpblog/robots.txt&lt;/a&gt;. Something doesn't seem right with this - I feel like it should be located elsewhere, but I'm not sure how to do it. I could use the help.

My set up is to have the blog in hamelife.com/wpblog, so I don't have it in the root directory. You can see how confused this is getting me!

Point #3 - Thank you for your suggestion, I'll have to think more about it. I'm leaning more towards a second blog. I know it means keeping two lots of content, but I'm learning to be a bit more laid back about this blogging thing - not be so stressed.

Point #4 - I'm looking at your Wordpress 404 article as we speak. It is excellent advice and I will implement it as soon as possible.

Thanks again, Doug. Your help is much appreciated.</description>
		<content:encoded><![CDATA[<div class="KonaBody"><em>Thanks for letting me tip your blog, Rory.</em></p>
<p>Are you kidding, Doug? I am so thankful to you for casting a helpful eye over the site. I need all the advice I can get, and I really appreciate the pointers you have given.</p>
<p>First off, I am blown away by your compliments. Thank you so much - they are enormously encouraging.</p>
<p>Now, I wonder if you could help me with your further tips:<br />
Point #1 - The M of hamelife takes a visitor to a sitemap. I used the <a href="http://cutline.tubetorial.com/use-this-simple-plug-and-play-sitemap-for-cutline/" rel="nofollow">Sitemap designed for Cutline</a>. Do I have this configured correctly? Or should I move directly to Point #2 and configure my robots.txt correctly?</p>
<p>My robots.txt actually reads:</p>
<p>User-agent: *<br />
Disallow: /wp-content/<br />
Disallow: /wp-admin/<br />
Disallow: /wp-includes/<br />
Disallow: /wp-<br />
Disallow: /feed/<br />
Disallow: /trackback/<br />
Disallow: /cgi-bin/</p>
<p>and I have it located in <a href="http://hamelife.com/wpblog/robots.txt" rel="nofollow">hamelife.com/wpblog/robots.txt</a>. Something doesn&#8217;t seem right with this - I feel like it should be located elsewhere, but I&#8217;m not sure how to do it. I could use the help.</p>
<p>My set up is to have the blog in hamelife.com/wpblog, so I don&#8217;t have it in the root directory. You can see how confused this is getting me!</p>
<p>Point #3 - Thank you for your suggestion, I&#8217;ll have to think more about it. I&#8217;m leaning more towards a second blog. I know it means keeping two lots of content, but I&#8217;m learning to be a bit more laid back about this blogging thing - not be so stressed.</p>
<p>Point #4 - I&#8217;m looking at your Wordpress 404 article as we speak. It is excellent advice and I will implement it as soon as possible.</p>
<p>Thanks again, Doug. Your help is much appreciated.</p></div>
]]></content:encoded>
	</item>
</channel>
</rss>
