<?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: Google vs. Duplicate Content &#8211; The rel=&#8221;canonical&#8221; Tag</title>
	<atom:link href="http://www.sagerock.com/blog/google-duplicate-content-rel-canonical/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sagerock.com/blog/google-duplicate-content-rel-canonical/</link>
	<description>The SageRock Team Web Marketing Blog</description>
	<lastBuildDate>Fri, 10 Feb 2012 15:24:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: sdefrawi</title>
		<link>http://www.sagerock.com/blog/google-duplicate-content-rel-canonical/comment-page-1/#comment-268</link>
		<dc:creator>sdefrawi</dc:creator>
		<pubDate>Tue, 30 Jun 2009 14:45:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.sagerock.com/blog/?p=284#comment-268</guid>
		<description>What about canonicalization in sitemap.xml? Any tips on how to handle http://www.yoursite.com vs http://www.yoursite.com/index.html? Should you redirect the latter to the former and remove /index.html from sitemap.xml?</description>
		<content:encoded><![CDATA[<p>What about canonicalization in sitemap.xml? Any tips on how to handle <a href="http://www.yoursite.com" rel="nofollow">http://www.yoursite.com</a> vs <a href="http://www.yoursite.com/index.html?" rel="nofollow">http://www.yoursite.com/index.html?</a> Should you redirect the latter to the former and remove /index.html from sitemap.xml?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 5ubliminal</title>
		<link>http://www.sagerock.com/blog/google-duplicate-content-rel-canonical/comment-page-1/#comment-81</link>
		<dc:creator>5ubliminal</dc:creator>
		<pubDate>Thu, 26 Mar 2009 12:44:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.sagerock.com/blog/?p=284#comment-81</guid>
		<description>Try this Wp.Plugin: &lt;a href=&quot;http://blog.5ubliminal.com/59&quot; rel=&quot;nofollow&quot;&gt;Canonical URL Wordpress Plugin&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Try this Wp.Plugin: <a href="http://blog.5ubliminal.com/59" rel="nofollow">Canonical URL WordPress Plugin</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: greg</title>
		<link>http://www.sagerock.com/blog/google-duplicate-content-rel-canonical/comment-page-1/#comment-18</link>
		<dc:creator>greg</dc:creator>
		<pubDate>Mon, 02 Mar 2009 15:16:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.sagerock.com/blog/?p=284#comment-18</guid>
		<description>Hey guys, thanks for the comments! I&#039;m right there with you Dino. There are already ways to fix canonical issues on websites. The people who don&#039;t know about those methods aren&#039;t any more likely to learn about this method either so I can&#039;t see how it improves things for most site owners.</description>
		<content:encoded><![CDATA[<p>Hey guys, thanks for the comments! I&#8217;m right there with you Dino. There are already ways to fix canonical issues on websites. The people who don&#8217;t know about those methods aren&#8217;t any more likely to learn about this method either so I can&#8217;t see how it improves things for most site owners.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tyler</title>
		<link>http://www.sagerock.com/blog/google-duplicate-content-rel-canonical/comment-page-1/#comment-17</link>
		<dc:creator>Tyler</dc:creator>
		<pubDate>Mon, 02 Mar 2009 14:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.sagerock.com/blog/?p=284#comment-17</guid>
		<description>Thanks for highlighting this.</description>
		<content:encoded><![CDATA[<p>Thanks for highlighting this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dino Baskovic</title>
		<link>http://www.sagerock.com/blog/google-duplicate-content-rel-canonical/comment-page-1/#comment-16</link>
		<dc:creator>Dino Baskovic</dc:creator>
		<pubDate>Mon, 02 Mar 2009 14:28:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.sagerock.com/blog/?p=284#comment-16</guid>
		<description>Webmasters will argue over which canonical URL format (e.g. &quot;Should it be example.com or www.example.com) until they&#039;re blue in the face -- myself included.  There are solid arguments for and against, which I won&#039;t cover here.

I will say that the best means of dealing with SEs when it comes to this is to avoid needless markup altogther, even if it is a teensy-tiny rel=&quot;canonical&quot; attribute/value pair.  Either have your webmaster fire up mod_rewrite on the *nix side or an IIS ASAPI filter (or other module as there are several) on the Windows side to force friendly, unobtrusive URL rewriting consistently across the board.

I hope that made a shred of sense... :)</description>
		<content:encoded><![CDATA[<p>Webmasters will argue over which canonical URL format (e.g. &#8220;Should it be example.com or <a href="http://www.example.com" rel="nofollow">http://www.example.com</a>) until they&#8217;re blue in the face &#8212; myself included.  There are solid arguments for and against, which I won&#8217;t cover here.</p>
<p>I will say that the best means of dealing with SEs when it comes to this is to avoid needless markup altogther, even if it is a teensy-tiny rel=&#8221;canonical&#8221; attribute/value pair.  Either have your webmaster fire up mod_rewrite on the *nix side or an IIS ASAPI filter (or other module as there are several) on the Windows side to force friendly, unobtrusive URL rewriting consistently across the board.</p>
<p>I hope that made a shred of sense&#8230; <img src='http://www.sagerock.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

