<?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: Give Customers What They Want: Easy Site Navigation</title>
	<atom:link href="http://www.marketingautopsyblog.com/customer-facing/low-cost-marketing-easy-site-navigation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.marketingautopsyblog.com/customer-facing/low-cost-marketing-easy-site-navigation/</link>
	<description>Successful Inbound Marketing in the New Media Space</description>
	<lastBuildDate>Fri, 04 Jun 2010 08:42:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Cuong Huynh</title>
		<link>http://www.marketingautopsyblog.com/customer-facing/low-cost-marketing-easy-site-navigation/#comment-140</link>
		<dc:creator>Cuong Huynh</dc:creator>
		<pubDate>Mon, 06 Jul 2009 07:36:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.marketingautopsyblog.com/?p=610#comment-140</guid>
		<description>I think that if the navigation above the fold is doing its job, then there is no need for repeating the same nav in the footer. Things that can go well on the footer may include Terms of use and Privacy policy stuff, but there&#039;s really no hard rule. Creativity and usability are keys I think.

Yours is a good looking site. It seems to try to be both a blog and a directory, so the navigation and content will want to support both. One example is the SEO Blog. The navigation on the right column shows Computer Hardware and Computer Software, but neither should have any impact or relationship to SEO. Just my 2 cents.</description>
		<content:encoded><![CDATA[<p>I think that if the navigation above the fold is doing its job, then there is no need for repeating the same nav in the footer. Things that can go well on the footer may include Terms of use and Privacy policy stuff, but there&#8217;s really no hard rule. Creativity and usability are keys I think.</p>
<p>Yours is a good looking site. It seems to try to be both a blog and a directory, so the navigation and content will want to support both. One example is the SEO Blog. The navigation on the right column shows Computer Hardware and Computer Software, but neither should have any impact or relationship to SEO. Just my 2 cents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spunky Jones Ethical SEO Techniques</title>
		<link>http://www.marketingautopsyblog.com/customer-facing/low-cost-marketing-easy-site-navigation/#comment-139</link>
		<dc:creator>Spunky Jones Ethical SEO Techniques</dc:creator>
		<pubDate>Mon, 06 Jul 2009 05:06:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.marketingautopsyblog.com/?p=610#comment-139</guid>
		<description>I have most of this in place on my blog. However, I need to work on my custom 404 error page to monetize a bit from it. Right now, it is pretty blank, but I have a 404 page.

I try not to go more than 3 levels in my navigation, makes it easier on the search engines to spider things.

I notice that many sites have a text menu at the footer of their site. I have decided if I am going to follow suit on that one. I have to figure out the benefits, if it is needed for better navigation and/or SEO.</description>
		<content:encoded><![CDATA[<p>I have most of this in place on my blog. However, I need to work on my custom 404 error page to monetize a bit from it. Right now, it is pretty blank, but I have a 404 page.</p>
<p>I try not to go more than 3 levels in my navigation, makes it easier on the search engines to spider things.</p>
<p>I notice that many sites have a text menu at the footer of their site. I have decided if I am going to follow suit on that one. I have to figure out the benefits, if it is needed for better navigation and/or SEO.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
