<?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: Internal Architecture SEO : Navigation Menu Versus In-Content&#160;Links</title>
	<atom:link href="http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/</link>
	<description></description>
	<lastBuildDate>Wed, 15 Feb 2012 00:21:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Thien Nhan</title>
		<link>http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/comment-page-1/#comment-1153576</link>
		<dc:creator>Thien Nhan</dc:creator>
		<pubDate>Tue, 01 Dec 2009 03:51:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/#comment-1153576</guid>
		<description>Get the best of Vietnamses art works</description>
		<content:encoded><![CDATA[<p>Get the best of Vietnamses art works</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Momchil Milev</title>
		<link>http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/comment-page-1/#comment-1110639</link>
		<dc:creator>Momchil Milev</dc:creator>
		<pubDate>Wed, 16 Sep 2009 10:54:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/#comment-1110639</guid>
		<description>Yeah, great post.
But won&#039;t we make a great mistake taking the main navigation out of the picture. After all it&#039;s so user-friendly and we should optimize for the user, not for search engines? 
What are your thoughts about this, Ann, or enyone?
Thanks in advance!</description>
		<content:encoded><![CDATA[<p>Yeah, great post.<br />
But won&#8217;t we make a great mistake taking the main navigation out of the picture. After all it&#8217;s so user-friendly and we should optimize for the user, not for search engines?<br />
What are your thoughts about this, Ann, or enyone?<br />
Thanks in advance!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Bell</title>
		<link>http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/comment-page-1/#comment-1084704</link>
		<dc:creator>Chris Bell</dc:creator>
		<pubDate>Mon, 01 Sep 2008 12:42:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/#comment-1084704</guid>
		<description>Hey,

Thanks for sharing.

I am always on a look for such a good &amp; useful resource.</description>
		<content:encoded><![CDATA[<p>Hey,</p>
<p>Thanks for sharing.</p>
<p>I am always on a look for such a good &amp; useful resource.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carrie Hill</title>
		<link>http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/comment-page-1/#comment-1081506</link>
		<dc:creator>Carrie Hill</dc:creator>
		<pubDate>Mon, 23 Jun 2008 13:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/#comment-1081506</guid>
		<description>Great post Ann - 

One thing we have been experimenting with is NOT relying on navigation to SEO a site.  Instead we are completely separating our SEO concerns from our navigation.  We still build them in CSS, but we dont RELY on them to pass &quot;Juice&quot; so our navigation doesnt have to link to every page on the site - from every page - ICK!  The other downfall we run into when trying to use nav to pass &quot;juice&quot; is you cant use great keywords in the nav links for the most part.  We work in travel and the phrases are somewhat long tail and a bit long for a navigation menu.  &quot;Gulf Shores Vacation Rentals&quot; is too verbose to fit nicely in a navigation - but I can for sure get this in a text link on the page.

Instead we build 2nd and 3rd tier navigation so related pages are linked together via navigation for the user.  In a way this is SEO friendly as we&#039;re grouping pages of a site togther that are related.  

For most of our SEO concerns we&#039;re relying on contextual links and our sitemap to move juice around the page.

Like I said, we&#039;re experimenting - but it seems to be working quite well.  Thanks for the post!

~Carrie</description>
		<content:encoded><![CDATA[<p>Great post Ann &#8211; </p>
<p>One thing we have been experimenting with is NOT relying on navigation to SEO a site.  Instead we are completely separating our SEO concerns from our navigation.  We still build them in CSS, but we dont RELY on them to pass &#8220;Juice&#8221; so our navigation doesnt have to link to every page on the site &#8211; from every page &#8211; ICK!  The other downfall we run into when trying to use nav to pass &#8220;juice&#8221; is you cant use great keywords in the nav links for the most part.  We work in travel and the phrases are somewhat long tail and a bit long for a navigation menu.  &#8220;Gulf Shores Vacation Rentals&#8221; is too verbose to fit nicely in a navigation &#8211; but I can for sure get this in a text link on the page.</p>
<p>Instead we build 2nd and 3rd tier navigation so related pages are linked together via navigation for the user.  In a way this is SEO friendly as we&#8217;re grouping pages of a site togther that are related.  </p>
<p>For most of our SEO concerns we&#8217;re relying on contextual links and our sitemap to move juice around the page.</p>
<p>Like I said, we&#8217;re experimenting &#8211; but it seems to be working quite well.  Thanks for the post!</p>
<p>~Carrie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry Van Horne</title>
		<link>http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/comment-page-1/#comment-1081504</link>
		<dc:creator>Terry Van Horne</dc:creator>
		<pubDate>Mon, 23 Jun 2008 12:46:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/#comment-1081504</guid>
		<description>One way to manage the PR inheritance and maximize the value passed is through a navigation menu. If you have only a little to start using only contextual you will have exhausted that quickly. The biggest mistakes SEO make is they get stuck on this idea that they must get IBLs to increase PR. That is a complete fallacy as with a few IBL you can generate a lot of internal PR if the PR managed within the site. The only reason to remove navigation menus is because you think you are decreasing the PR passed with more links on the page. True, but having the nav menu on a few thousand pages sure makes up for a slight savings from eliminating the nav links.</description>
		<content:encoded><![CDATA[<p>One way to manage the PR inheritance and maximize the value passed is through a navigation menu. If you have only a little to start using only contextual you will have exhausted that quickly. The biggest mistakes SEO make is they get stuck on this idea that they must get IBLs to increase PR. That is a complete fallacy as with a few IBL you can generate a lot of internal PR if the PR managed within the site. The only reason to remove navigation menus is because you think you are decreasing the PR passed with more links on the page. True, but having the nav menu on a few thousand pages sure makes up for a slight savings from eliminating the nav links.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Ellsworth</title>
		<link>http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/comment-page-1/#comment-1081419</link>
		<dc:creator>Matt Ellsworth</dc:creator>
		<pubDate>Fri, 20 Jun 2008 22:23:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/#comment-1081419</guid>
		<description>good ideas here.  we use a combination of both on most sites.</description>
		<content:encoded><![CDATA[<p>good ideas here.  we use a combination of both on most sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BottomTurn</title>
		<link>http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/comment-page-1/#comment-1081406</link>
		<dc:creator>BottomTurn</dc:creator>
		<pubDate>Fri, 20 Jun 2008 15:05:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.searchenginejournal.com/internal-architecture-seo-navigation-menu-versus-in-content-links/7157/#comment-1081406</guid>
		<description>I think that you can use the header menu for the top pages, e.g. French wines, and have some words in the content like Bordeaux, which could be located under the index.html/frenchwines/bordeaux.
Your anchor text goes more specific while the links in the menus are more generic.
Ann ?!</description>
		<content:encoded><![CDATA[<p>I think that you can use the header menu for the top pages, e.g. French wines, and have some words in the content like Bordeaux, which could be located under the index.html/frenchwines/bordeaux.<br />
Your anchor text goes more specific while the links in the menus are more generic.<br />
Ann ?!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

