Tweet button count does not increment - Is it due to HEAD request returning 301?


#1

The FAQ (https://dev.twitter.com/docs/tweet-button/faq) suggests that the tweet button counter will only increment if the HEAD request is successful. Here is the result of a HEAD request to the URL that I am tweeting. Will the 301 prevent my counter from incrementing?

bporter@bporter:~$ curl -I http://reviews.testcustomer.bazaarvoice.com/bvstaging/50test/Product1/reviews.htm
HTTP/1.1 301 Moved Permanently
Location: http://reviews.testcustomer.bazaarvoice.com/bvstaging/50test/Product1/bazaarvoice-tm-test-product-1-reviews/reviews.htm
Content-Type: text/html; charset=UTF-8
Cache-Control: no-cache, no-store
Expires: Fri, 14 Oct 2011 19:24:30 GMT
Date: Fri, 14 Oct 2011 19:24:30 GMT
Connection: keep-alive


#2

It depends on what you’re offering as the parameters for the Tweet Button –

Would “http://reviews.testcustomer.bazaarvoice.com/bvstaging/50test/Product1/bazaarvoice-tm-test-product-1-reviews/reviews.htm” be the canonical URL to reach your content? What values do you have for data-url versus datacount-url?


#3

In my case, it looks like data-url and data-counturl both specify the same URL. My guess is that this is the cause of the problem. To tweet a URL that redirects to another location, I probably need to specify the tweeted URL (i.e. the canonical URL) as the data-url and the final, fully resolved URL as the data-counturl. Is this right?


#4

can anyone confirm/deny @bentonporter’s response? Having a similar issue.


#5