Whenever I post something on my blog, the post title and URL gets pushed to Facebook and Twitter. The URL is shortened via bit.ly. Almost immediately, I will see a couple of tweets of the post information (not retweets of my sharing) including a shortened link to the post and a piggback link to some other website. This second URL is like a parasite attempting to leverage interest in my post to get links and clicks to the other site.
Due to the sorry behaviour of many Twitter accounts of reciprocal following, these parasite spammers can easily build up modest follower lists.
I really don't like this behaviour.
You should try playing with Google's newly minted author tags. I'm sure you know that these sites are scraping your accounts, using you as a curator to provide them with content. The author tags are a way for Google to try to start crediting the best authors and curators for their work; it's possible even now that these links actually help you, since your Tweets and blog content are presumably time stamped and spidered by Google before the scraping occurs. If the problem is serious, I suggest a slight delay be applied to the feed, a randomly embedded link to the article permalink be inserted in the body copy of each post, and use the new author tags. With those precautions in place, the echoed content would in fact be an asset.
More on the author tag (I am unaffiliated with this site):
http://searchengineland.com/google-adds-authorship-rich-snippet-markup-80455
Posted by: Clarkmackey | June 16, 2011 at 03:54 PM
Clark - it is not clear that that is the problem or that author tags are the solution. Let's imagine that the parasite tweeter is picking up my RSS feed. When they see a new post, they pull out the title and a link, bit.ly it, add another bit.ly link to their stuff and then tweet it. How will an author tag on the post prevent them from doing this?
Posted by: Matthew Hurst | June 17, 2011 at 06:54 PM
You can always remove the push notifications both in your Typepad accunt or in your Twitter/Facebook account.
Posted by: Idpage?user=vviurtjuujgv | June 26, 2011 at 03:05 PM
Two observations. Firstly any bit.ly link you can check where it's going to by adding a + on the end of the URL. The second is that you can get bit.ly to use a custom domain (unfortunally you're going to have to pay to register that domain but it's only going to be like £20 a year or so)
Posted by: SQLChap | July 13, 2011 at 09:15 AM
cheap tory burch
http://www.ustoryburchsales.com/
Posted by: Lisa Wang | September 16, 2011 at 02:37 AM