FeedBurner Steals CommentLuv Links
CommentLuv is one of the best plugins available for WordPress. It allows any blog owner to reward the people who comment with a direct link back to one of their own blog articles.
CommentLuv is growing in popularity and many large well known blogs are starting to jump on, but there’s a major hiccup that’s still not very well known:
Feedburner Steals Every CommentLuv Backlink
Yes, that’s right. I hate to be the bearer of bad news, but if you haven’t changed the FeedBurner default settings, then every one of your CommenLuv links points to Google.
Don’t Worry too much though because it’s not all doom and gloom. The problem is surprisingly easy to check for and fix. Here are the steps you’ll need to take:
How to Check CommentLuv
First you can either jump back to a comment you’ve made in the past or simply comment on this post directly below. Once the comment is submitted, scroll your mouse over the CommentLuv link. Check the bottom left-hand corner of your browser and the link should appear.
There’s a second option in case your current browser doesn’t support this feature. Use your mouse to right-click on the link and then click “Copy Link Location”.
Paste the link into any word processor to see where it points. If it’s a direct link back to your site then you’re in the clear, but if it says “http://feedproxy.google.com/……” then you’ve been losing all your linkjuice to Google.
How to Fix FeedBurner
In order to fix this issue you’ll need to log into FeedBurner. Once your account is open, click on “Configure Stats”.
You will then uncheck the box named “Item Link Clicks”. The last thing is to make sure the setting has been saved.
That’s it! You are now all set to receive real backlinks for the time you spend leaving thoughtful comments on other blogs.
One last note. Once the setting has been fixed there will most likely be a slight lag before implementation. So it’s completely normal if you go to test out the changes and you still see the feedproxy link showing up. As soon as FeedBurner’s cache is updated (normally less than 24hrs) you’ll be all set to go.
Sep 03, 2010 | Comments: 5