Public
Don't forget to use rel=canonical (or specify the page's URL in the widget code) when using social widgets & hash marks (#) to jump to sections of a page. Using canonicalization helps to keep the counts of most widgets (including the +1 button) focused on pages' your main URL, not on the hash mark. (Thanks for the write-up, +Dan Petrovic!)
More on the rel=canonical is at http://support.google.com/webmasters/bin/answer.py?hl=en&answer=139394
More on the +1 button is at https://developers.google.com/+/plugins/+1button/
More on the rel=canonical is at http://support.google.com/webmasters/bin/answer.py?hl=en&answer=139394
More on the +1 button is at https://developers.google.com/+/plugins/+1button/
John. Could I make a comment that the Google owned property Feedburner adds a lot of extra params to URLs for tracking. More really needs to be done at Google's end to help solve that particular canonical problem, with UTM source making its way to other social networks automatically. e.g see Twitter: https://twitter.com/#!/search/utm_source%3Dfeedburner
There's no way that I can see of turning it off. I've no idea if there's an active development team working on that product, but any guidance the webmaster team could provide is appreciated.Jun 4, 2012
+Paul Anthony, we try to catch those when crawling & indexing, but if you want to be safe, the easiest way to handle that for indexing is also to just use rel=canonical. Some people prefer to use the hash-mark version of these tagged URLs (eg http://yoast.com/canonical-urls-social-media-campaign-tracking/ ) or redirect away from the tracking URLs ( http://jasoncodes.com/posts/clean-google-analytics-tracking-urls uses a client-side URL rewrite), both of which can also make sense.Jun 4, 2012
Add a comment...