Google start’s supporting canonical supporting HTTP header’s.Google made the change’s according to the webmaster’s feedback.The HTTP header’s syntax is described in details here:section 5 of IETF RFC 5988. On a WebmasterCentral Blogpost Pierre Far, Webmaster Trends Analyst, notified this enhanced addition.He wrote†To see the rel=â€canonical†HTTP header in action, let’s look at the scenario of a website offering a white paper both as an HTML page and as a downloadable PDF alternative, under these two URLs: http://www.example.com/white-paper.html http://www.example.com/white-paper.pdf In this case, the 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; for example: GET /white-paper.pdf HTTP/1.1 Host: www.example.com (...rest of HTTP request headers...) HTTP/1.1 200 OK Content-Type: application/pdf Link: <http://www.example.com/white-paper.html>; rel="canonical" Content-Length: 785710 (... rest of HTTP response headers...) Another common situation in which rel=â€canonical†HTTP headers may help is when a website serves the same file from multiple URLs (for example when using a content distribution network) and the webmaster wishes to signal to Google the preferred URL.†To know more about canonical link element,watch this video: [video=youtube;Cm9onOGTgeM]http://www.youtube.com/watch?v=Cm9onOGTgeM&feature=player_embedded[/video] Published by Anirban Das,Zebra Techies,India
Be careful with this, I've heard that it can be used to redirect your traffic if your site is hacked.