Fat Pings, What Are They, Why You Need Them As A Webmaster
Content scraping is a big issue on today's Internet, and a challenge for search engines to get it right. It basically comes down to the question of attribution: who is the original author of a piece of content and on which website was it published first. Search engines get that right most of the time. Sometimes though they fail and it hurts the original content creator badly when that happens.
Why is it bad? Because search engines rank content in their search results. If they believe you are the creator you are usually ranked higher than a site that has copied the content, if such a site is ranked at all.
The reality is this. Sites that scrape contents are easy to setup (using RSS feed mostly), require barely any maintenance and earn good money when done in bulk. These sites publish copied contents shortly after they have been published on the original website. As long as people can make money from this method, they will use it to do just that.
Fat Pings are one way to resolve the situation. The idea is simple: when you publish an article you ping a trusted source to confirm that you site is the original location of that article. It does not really matter if you do it 10 seconds before the scraper does the same or one hour, it is only important that you do it before the scraper does. This obviously has consequences for original content creators who do not make use of Fat Pings, as it is quite possible that scraper sites may make use of Fat Pings for an extra advantage.
How do you cope with that situation? You configure all of your sites to support Fat Pings. Here is how that is done.
If your blog is hosted on WordPress.com or Blogger, then you do not need to do anything. Fat Pings are automatically sent out. If you are running a self hosted WordPress blog, you can install the free PubSubHubbub extension to inform search engines when they blog has been updated.
The suggestion to use Fat Pings comes directly from Google. You can read up more about it on Search Engine Journal and Labnol.
That is the awesome and valuable information you have provided Martin thanks a lot.
Doesn’t require any effort so whether the benefit is big or small, it’s a no brainer.
Besides the push notification of the news, I don’t see how much this is different from an Atom Feed or and RSS feed.
Thanks for the pointer Martin. Looking through the article links, WordPress default pings aren’t ‘fat’ and relying on Feedburner to do it leaves a window of time free for site scrapers to do their dirty work (as Feedburner doesn’t continually poll your site).
The WordPress extension seems to work fine with no additional configuration required – just plugin and play.
Yep that’s it. Just install the plugin and activate it, that’s it. You can add additional hubs if you have any, but that’s not required. I personally would still prefer an internal WordPress solution without plugin.
That is a good point Martin, but do you know that some of the sites that scrape content are actually run by people who are good in coding? like for example I have seen sites that pull content from various rss feeds and render those content on their own sites.
Anyway, that is just my own opinion. Talking about blogging, do you still remember I have mentioned about Java the other day before, well, I have finally decided to give a full tutorial about this language on my blog so if you have time do stop by and leave a comment on how can I improve on my tutorial. Thanks! :)