Google announced they are now supporting the rel=”canonical” attribute within HTTP headers.
This enables webmasters to set up a canonical for linking to or from PDF files or other non-HTML based files.
One of the examples given by Google is that a “webmaster can signal to Google that the canonical URL for the PDF download is the HTML document by using a rel=”canonical” HTTP header when the PDF file is requested.”
This also comes in handy when you use a CDN (content delivery network) and the content is being served from many different URLs. You can now use the rel=”canonical” within the HTTP header to set up those redirects for that type of content.
Related Stories:
- Google, Yahoo & Microsoft Unite On “Canonical Tag” To Reduce Duplicate Content Clutter
- Canonical Tag 2.0: Google To Add Cross Domain Support
- Google Supports Cross-Domain ‘Canonical Tag’
Related Topics: Google: SEO | Google: Web Search | Google: Webmaster Central | SEO: Redirects & Moving Sites | SEO: Tagging









History:
September 2009: tweeted https://twitter.com/ianmacfarlane/status/4499303411 by Ian Macfarlane
December 2009: outlined http://sebastians-pamphlets.com/x-canonical-uri-http-header/
April 2010: considered http://maileohye.com/rel-canonical-non-html-files/
June 2011: launched http://googlewebmastercentral.blogspot.com/2011/06/supporting-relcanonical-http-headers.html
But what are the benefits of using the rel=”canonical” HTTP header? Is that solution really useful you think?
I’d be interested in hearing any discussion of any possible linkages between this move (relative to CDNs) and Google’s Panda offensive against content farms. I haven’t had enough coffee yet to get my head around this :P
Barry, excellent point about content going different places. I’m always amazed at the number of people who don’t know the power of canonicalization. Great article – thanks for posting!