<?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: Improve SEO with Google&#8217;s New Canonical Element</title>
	<atom:link href="http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Fri, 19 Mar 2010 02:31:55 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jtresidder</title>
		<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/comment-page-1/#comment-880944</link>
		<dc:creator>jtresidder</dc:creator>
		<pubDate>Fri, 20 Feb 2009 10:37:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=5682#comment-880944</guid>
		<description>@brothercake: It&#039;s Microsoft&#039;s fault that early IE doesn&#039;t implement the box model correctly, etc. - should we make a stand against them too, or work around it to ensure that our clients&#039; sites render properly in both models?

You&#039;re right of course, but at the end of the day that&#039;s irrelevant. The bottom line is that if you don&#039;t avoid what Google considers to be duplicate content, your site will suffer.</description>
		<content:encoded><![CDATA[<p>@brothercake: It&#8217;s Microsoft&#8217;s fault that early IE doesn&#8217;t implement the box model correctly, etc. &#8211; should we make a stand against them too, or work around it to ensure that our clients&#8217; sites render properly in both models?</p>
<p>You&#8217;re right of course, but at the end of the day that&#8217;s irrelevant. The bottom line is that if you don&#8217;t avoid what Google considers to be duplicate content, your site will suffer.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: shoebox</title>
		<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/comment-page-1/#comment-880286</link>
		<dc:creator>shoebox</dc:creator>
		<pubDate>Wed, 18 Feb 2009 20:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=5682#comment-880286</guid>
		<description>So what&#039;s better? A meta description rich url or one with a permanent id number in it?</description>
		<content:encoded><![CDATA[<p>So what&#8217;s better? A meta description rich url or one with a permanent id number in it?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Buckler</title>
		<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/comment-page-1/#comment-880252</link>
		<dc:creator>Craig Buckler</dc:creator>
		<pubDate>Wed, 18 Feb 2009 19:10:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=5682#comment-880252</guid>
		<description>Google&#039;s tag might be reasonable, but what about &lt;a href=&quot;http://www.sitepoint.com/blogs/2009/02/19/ie8-standards-mode-opt-in/&quot; rel=&quot;nofollow&quot;&gt;the latest idea from Microsoft for Internet Explorer 8.0&lt;/a&gt;...</description>
		<content:encoded><![CDATA[<p>Google&#8217;s tag might be reasonable, but what about <a href="http://www.sitepoint.com/blogs/2009/02/19/ie8-standards-mode-opt-in/" rel="nofollow">the latest idea from Microsoft for Internet Explorer 8.0</a>&#8230;</p>]]></content:encoded>
	</item>
	<item>
		<title>By: brothercake</title>
		<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/comment-page-1/#comment-880183</link>
		<dc:creator>brothercake</dc:creator>
		<pubDate>Wed, 18 Feb 2009 16:45:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=5682#comment-880183</guid>
		<description>Yeah maybe I overreacted a little, on further reading it seems fairly reasonable.

I just get mighty suspicious at anything that forces one group of people to take responsibility for another group of people&#039;s problems, and in essence that&#039;s what we have here. It&#039;s all very well for google to play the &quot;let&#039;s all pull together for the good of the internet&quot; card, but we know perfectly well that google isn&#039;t concerned with the good of the internet, it&#039;s concerned with its own interests, which may or may not co-incide.</description>
		<content:encoded><![CDATA[<p>Yeah maybe I overreacted a little, on further reading it seems fairly reasonable.</p>
<p>I just get mighty suspicious at anything that forces one group of people to take responsibility for another group of people&#8217;s problems, and in essence that&#8217;s what we have here. It&#8217;s all very well for google to play the &#8220;let&#8217;s all pull together for the good of the internet&#8221; card, but we know perfectly well that google isn&#8217;t concerned with the good of the internet, it&#8217;s concerned with its own interests, which may or may not co-incide.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Buckler</title>
		<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/comment-page-1/#comment-880120</link>
		<dc:creator>Craig Buckler</dc:creator>
		<pubDate>Wed, 18 Feb 2009 13:43:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=5682#comment-880120</guid>
		<description>Amazingly, plugins have already appeared for WordPress, Drupal and Magento. &lt;a href=&quot;http://yoast.com/canonical-url-links/&quot; rel=&quot;nofollow&quot;&gt;Grab them from Yoast.com&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Amazingly, plugins have already appeared for WordPress, Drupal and Magento. <a href="http://yoast.com/canonical-url-links/" rel="nofollow">Grab them from Yoast.com</a>.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: cranial-bore</title>
		<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/comment-page-1/#comment-880107</link>
		<dc:creator>cranial-bore</dc:creator>
		<pubDate>Wed, 18 Feb 2009 13:11:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=5682#comment-880107</guid>
		<description>This brings to mind tags and categories within Wordpress (or any blog/CMS with those features I guess), where a tag may be identical to a category name. The same content will be delivered if requested by clicking on a link from a tag cloud, as by choosing a category. This could be a reasonable solution to direct one such page to the other.

I just need someone &lt;em&gt;else&lt;/em&gt; to write a WP Plugin to do this :)</description>
		<content:encoded><![CDATA[<p>This brings to mind tags and categories within Wordpress (or any blog/CMS with those features I guess), where a tag may be identical to a category name. The same content will be delivered if requested by clicking on a link from a tag cloud, as by choosing a category. This could be a reasonable solution to direct one such page to the other.</p>
<p>I just need someone <em>else</em> to write a WP Plugin to do this :)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/comment-page-1/#comment-880103</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 18 Feb 2009 12:58:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=5682#comment-880103</guid>
		<description>&lt;blockquote&gt;So Google now wants us to take responsibility for their inability to tell the difference between natural duplication and spamming? They expect us to provide the manpower that they’re not prepared to?&lt;/blockquote&gt;
That seems like a bit of an overreaction!
Through accidents of history and changing practices, most pages on my website have multiple URLs. In some cases, it&#039;s because there are links from outside that have www. on them (although no internal links do), in many cases it&#039;s because Google uses the old .htm extension rather than the current canonical .shtml extension, and in some cases it is because the page has been renamed. The old links always send users to the right page, but it would be very useful to be able to set a definitive link on each page so that Google is referencing the correct URL - that will help users, by ensuring that SERPs are not duplicated, and it will help me when analysing my logs.

It is also very handy for anyone whose site generates print-friendly or text-only pages to ensure that search engines don&#039;t send users to these pages, which won&#039;t be as helpful for them as the &#039;proper&#039; version of the page.

I welcome this move - it is very little effort for web designers, and if it improves the way the search engine understands your website, what&#039;s the problem with that?</description>
		<content:encoded><![CDATA[<blockquote><p>So Google now wants us to take responsibility for their inability to tell the difference between natural duplication and spamming? They expect us to provide the manpower that they’re not prepared to?</p></blockquote>
<p>That seems like a bit of an overreaction!<br />
Through accidents of history and changing practices, most pages on my website have multiple URLs. In some cases, it&#8217;s because there are links from outside that have www. on them (although no internal links do), in many cases it&#8217;s because Google uses the old .htm extension rather than the current canonical .shtml extension, and in some cases it is because the page has been renamed. The old links always send users to the right page, but it would be very useful to be able to set a definitive link on each page so that Google is referencing the correct URL &#8211; that will help users, by ensuring that SERPs are not duplicated, and it will help me when analysing my logs.</p>
<p>It is also very handy for anyone whose site generates print-friendly or text-only pages to ensure that search engines don&#8217;t send users to these pages, which won&#8217;t be as helpful for them as the &#8216;proper&#8217; version of the page.</p>
<p>I welcome this move &#8211; it is very little effort for web designers, and if it improves the way the search engine understands your website, what&#8217;s the problem with that?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Tyssen</title>
		<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/comment-page-1/#comment-879993</link>
		<dc:creator>Tyssen</dc:creator>
		<pubDate>Wed, 18 Feb 2009 09:22:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=5682#comment-879993</guid>
		<description>&lt;blockquote&gt;However, you and your clients need a good position in search results.&lt;/blockquote&gt;

Yes, I don&#039;t think too many clients are going to support you taking a moral stand if no-one visits their site because they&#039;ve been penalised.</description>
		<content:encoded><![CDATA[<blockquote><p>However, you and your clients need a good position in search results.</p></blockquote>
<p>Yes, I don&#8217;t think too many clients are going to support you taking a moral stand if no-one visits their site because they&#8217;ve been penalised.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Buckler</title>
		<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/comment-page-1/#comment-879990</link>
		<dc:creator>Craig Buckler</dc:creator>
		<pubDate>Wed, 18 Feb 2009 09:20:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=5682#comment-879990</guid>
		<description>You have a valid point. Google should not penalise natural duplication, especially if it&#039;s within the same domain. To be fair to Google, they try and cater for that situation. 

The canonical element could certainly help when you publish two or more versions of the same article, e.g. a normal version, a text-only version, and a mobile version. Whether Google realise those pages are inexact replicas is another matter.

Does Google have too much power? Probably. Is the search engine broken? Nothing is ever perfect. However, you and your clients need a good position in search results. It&#039;s difficult to ignore a known indexing problem especially when a workaround is available.</description>
		<content:encoded><![CDATA[<p>You have a valid point. Google should not penalise natural duplication, especially if it&#8217;s within the same domain. To be fair to Google, they try and cater for that situation. </p>
<p>The canonical element could certainly help when you publish two or more versions of the same article, e.g. a normal version, a text-only version, and a mobile version. Whether Google realise those pages are inexact replicas is another matter.</p>
<p>Does Google have too much power? Probably. Is the search engine broken? Nothing is ever perfect. However, you and your clients need a good position in search results. It&#8217;s difficult to ignore a known indexing problem especially when a workaround is available.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: brothercake</title>
		<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/comment-page-1/#comment-879774</link>
		<dc:creator>brothercake</dc:creator>
		<pubDate>Wed, 18 Feb 2009 01:33:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=5682#comment-879774</guid>
		<description>So Google now wants us to take responsibility for their inability to tell the difference between natural duplication and spamming? They expect us to provide the manpower that they&#039;re not prepared to?

This reminds me of the brief hysteria that arose around content designed for screenreaders - content that is invisible to screen users using offleft positioning, but still there in the source so that screenreaders hear it. To some this was a great concern that google would view it as spamming. And my reply to that was the same as to this - that&#039;s google&#039;s problem, not mine. If google penalises me for doing this then google is broken; period.

Any company that would expect us to take this seriously has way, way to much power.</description>
		<content:encoded><![CDATA[<p>So Google now wants us to take responsibility for their inability to tell the difference between natural duplication and spamming? They expect us to provide the manpower that they&#8217;re not prepared to?</p>
<p>This reminds me of the brief hysteria that arose around content designed for screenreaders &#8211; content that is invisible to screen users using offleft positioning, but still there in the source so that screenreaders hear it. To some this was a great concern that google would view it as spamming. And my reply to that was the same as to this &#8211; that&#8217;s google&#8217;s problem, not mine. If google penalises me for doing this then google is broken; period.</p>
<p>Any company that would expect us to take this seriously has way, way to much power.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: samanime</title>
		<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/comment-page-1/#comment-879599</link>
		<dc:creator>samanime</dc:creator>
		<pubDate>Tue, 17 Feb 2009 20:34:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=5682#comment-879599</guid>
		<description>This is great news. I plan to implement this immediately. I&#039;m so glad they did it in a standards-compliant manner as well. When I read &quot;canonical element&quot; I was thinking  and I was worried, but I think they figured out a great solution.</description>
		<content:encoded><![CDATA[<p>This is great news. I plan to implement this immediately. I&#8217;m so glad they did it in a standards-compliant manner as well. When I read &#8220;canonical element&#8221; I was thinking  and I was worried, but I think they figured out a great solution.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Mihaela Lica</title>
		<link>http://www.sitepoint.com/blogs/2009/02/18/improve-seo-google-canonical-element/comment-page-1/#comment-879598</link>
		<dc:creator>Mihaela Lica</dc:creator>
		<pubDate>Tue, 17 Feb 2009 20:29:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=5682#comment-879598</guid>
		<description>I think you meant duplicate content can have an adverse effect on SERPs rather than page rank. Other than that the information is gold :)</description>
		<content:encoded><![CDATA[<p>I think you meant duplicate content can have an adverse effect on SERPs rather than page rank. Other than that the information is gold :)</p>]]></content:encoded>
	</item>
</channel>
</rss>
