We are currently getting a lot of reports regarding the Tweetmeme button being inaccurate across different pages of a website.

By default the button will pick up the address of the page it is on, it will then work out the the tweet count for that URL. For example if you show a button on your home page and on the main story page, these pages have two separate URL’s and thus will gain two separate tweet counts. This also causes a problem if you append anything onto your URL such as page numbers, Facebook connect settings or comment numbering.

We also see issues with sites that include the button on each blog post and then have all the posts shown on the home page. In this case, unless action is taken, when viewing the home page each button will have the same tweet count, as it will  be using the URL for the homepage itself, not the indivual post URL.

You can easily solve this problem by specifying the URL for the correct page in JavaScript. An optional tweetmeme_url parameter is available, which overrides the buttons ability to pick up the URL of that page.

The best example of this is on the main Tweetmeme site. In the sidebar on every page we have the current number of tweets the URL http://tweetmeme.com has. We maintain a constant and accurate count by specifying the tweetmeme_url to be http://tweetmeme.com.

<script type="text/javascript">
	tweetmeme_url = 'http://tweetmeme.com';
</script>
<script src="http://tweetmeme.com/i/scripts/button.js" type="text/javascript"/>

If your site is a blog, it may be possible to have the tweetmeme_url set automatically. This is the main purpose of our WordPress plugin, and we also have an example of how it can be setup on Blogger.

You can find more information on the button and how to fully implement the tweetmeme_url on the Tweetmeme help site. If you are still having problems please refer to the discussion on our forums.