Specify your canonical. You can now use a link rel=“canonical” to tell Google that a page has a canonical URL elsewhere. I’ve run in to this problem a bunch of times—in some sites it really does make sense to have the same content shown in two different places—and this seems like a neat solution that could apply to much more than just metadata for external search engines.
Sign in with 
OpenID
This is interesting, but makes me sad on two counts:
* It's specific to HTML, with no alternative specified for other document formats. It's a shame the "Link" HTTP header hasn't made it to RFC yet.
* It's another thing that's going to turn into SEO snake-oil and make life harder for web developers who have to implement all of their crazy, misinformed recommendations.
Martin: Having HTTP header support wouldn't really make a difference. In this case, this is actually an html equivalent of an already-existing http header, Content-Location.
But google have created this new standard because the existing one is apparently poorly supported on servers, and used incorrectly by content authors. It follows that if an http equivalent of html link headers existed, it too would be poorly implemented in servers and incorrectly configured by authors, and would have to be ignored like Content-Location.
Which field is required -- this one? - 17th February 2009 01:34 - #