<?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&#039;s New Canonical Option</title> <atom:link href="http://brenelz.com/blog/googles-new-canonical-option/feed/" rel="self" type="application/rss+xml" /><link>http://brenelz.com/blog/googles-new-canonical-option/</link> <description>a winnipeg website design company.</description> <lastBuildDate>Mon, 06 Feb 2012 15:07:39 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" /> <item><title>By: Bold Endeavours</title><link>http://brenelz.com/blog/googles-new-canonical-option/comment-page-1/#comment-689</link> <dc:creator>Bold Endeavours</dc:creator> <pubDate>Thu, 26 Mar 2009 10:14:19 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=651#comment-689</guid> <description>Yes it is better to avoid duplicate content and generate the unique content for the site. It will take time and money but still it is worth doing it.</description> <content:encoded><![CDATA[<p>Yes it is better to avoid duplicate content and generate the unique content for the site. It will take time and money but still it is worth doing it.</p> ]]></content:encoded> </item> <item><title>By: Brian</title><link>http://brenelz.com/blog/googles-new-canonical-option/comment-page-1/#comment-691</link> <dc:creator>Brian</dc:creator> <pubDate>Tue, 17 Feb 2009 21:23:04 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=651#comment-691</guid> <description>This is a new standard that has been agreed on by the three major search engines (Google, Yahoo!, and Live) and was announced recently at SMX West.  Live&#039;s announcement: http://blogs.msdn.com/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx</description> <content:encoded><![CDATA[<p>This is a new standard that has been agreed on by the three major search engines (Google, Yahoo!, and Live) and was announced recently at SMX West.  Live&#8217;s announcement: <a href="http://blogs.msdn.com/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx" rel="nofollow">http://blogs.msdn.com/webmaster/archive/2009/02/12/partnering-to-help-solve-duplicate-content-issues.aspx</a></p> ]]></content:encoded> </item> <item><title>By: James</title><link>http://brenelz.com/blog/googles-new-canonical-option/comment-page-1/#comment-690</link> <dc:creator>James</dc:creator> <pubDate>Sun, 15 Feb 2009 22:58:38 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=651#comment-690</guid> <description>Thanks for the info Brenelz. I agree with you on the fact it&#039;s best to avoid duplicate content altogether. With the example you used (different color schemes) it would be quite easy to get the GET data, set the cookie, and then redirect back to index.php - this way no duplicate content is created...I&#039;m always a bit skeptical about this though - Google and other search engines seem quite sensitive. I mean, if I created a link to this site but added a random query string like ?blah=22938 then Google would see it as an entirely different page; duplicate content. There should really be a better system in place for this type of scenario.</description> <content:encoded><![CDATA[<p>Thanks for the info Brenelz. I agree with you on the fact it&#8217;s best to avoid duplicate content altogether. With the example you used (different color schemes) it would be quite easy to get the GET data, set the cookie, and then redirect back to index.php &#8211; this way no duplicate content is created&#8230;</p><p>I&#8217;m always a bit skeptical about this though &#8211; Google and other search engines seem quite sensitive. I mean, if I created a link to this site but added a random query string like ?blah=22938 then Google would see it as an entirely different page; duplicate content. There should really be a better system in place for this type of scenario.</p> ]]></content:encoded> </item> <item><title>By: Brian Cray</title><link>http://brenelz.com/blog/googles-new-canonical-option/comment-page-1/#comment-688</link> <dc:creator>Brian Cray</dc:creator> <pubDate>Sun, 15 Feb 2009 03:37:27 +0000</pubDate> <guid isPermaLink="false">http://www.brenelz.com/blog/?p=651#comment-688</guid> <description>Great dig up on this! There are so many Web sites suffering from diluted page ranks due to this. I usually handle this kind of stuff with .htaccess hacks :)</description> <content:encoded><![CDATA[<p>Great dig up on this! There are so many Web sites suffering from diluted page ranks due to this. I usually handle this kind of stuff with .htaccess hacks <img src='http://brenelz.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (User agent is rejected)
Database Caching 25/35 queries in 0.007 seconds using disk: basic
Object Caching 539/540 objects using disk: basic

Served from: brenelz.com @ 2012-02-09 04:32:34 -->
