10 steps to a more splog-free WordPress blog
Last Thursday, I realized that this blog was being scraped. I’m sure it was being scraped before, but I never really wanted to spend time looking into it. A blog takes so much time to write and manage, that I didn’t want to add another task to my blogging plate.
But now that I have seen the sploggers in action, I realize how truly irritating and damaging sploggers are. But I guess that’s the case with all theft.
Anyways, I turned to you, my readers, to get your advice, and I got some amazing tips from the people that responded. I also did a little extra searching around, plus Darren Hoyt wrote a post with some good links in it, so here’s a summary of 10 ways to stop sploggers.
Part 1: 4 5 ways to find out if you’re being splogged
- I found out about one of the scrapers via FeedBurner’s Uncommon Use feature. When you’re checking your feed stats in FeedBurner, make sure to keep an eye on the Uncommon Uses section to see if any sites you’re not familiar with are showing up. Jonathan Bailey from Plagiarism Today also has a detailed post on this subject.
- Use the Copyfeed WordPress plugin, or any other plugin that adds a footer to your feed, and add a link back to your site in the footer. This way, if a splogger publishes your complete posts on their site, you’ll get Incoming Link notices in your WordPress dashboard.
- Lorelle has a bunch of steps and plugins that you can use to identify content theft.
- Use the Digital Fingerprint WordPress plugin. This plugin places a customized digital fingerprint into blog posts, which is only visible in the feed:”Once embedded in your post, the plugin allows you to quickly and easily search the blogosphere for references to the digital fingerprint using Google Blogsearch, BlogPulse, and Sphere…It also allows the quick and easy search for your digital fingerprint of the web itself using Google, Yahoo!, and MSN. An optional quick search can be included in the dashboard itself…Lastly, the plugin provides a few resources and links to places that will help you combat splog and spam should you find your content plagiarised or stolen on another website.”Talk about comprehensive!
- Update Jan. 23, 2008: Joost de Valk explains five more ways that you can search around the web for your URL and feed URL to find instances where your blog is being scraped.
- Update Feb. 24, 2008: Jacques left a comment here suggesting using Copyscape to track down sploggers.
Part 2: You’re being splogged? 10 ways to stop ‘em
- Alyk says to contact the sploggers and ask them to stop. This may sound simple, but it’s a great way to start…as long as the sploggers have left their email addresses or a contact form on the site. In my case, they hadn’t.
- Blaine, Jonathan and Jacob all suggested complaining to Google if the splogger is using Google Adwords to monetize the site. Jacob sent the following links:Easy: report them as spam to Google here:
https://www.google.com/webmasters/tools/spamreport?hl=enHarder: submit a dmca complaint to Google:
http://www.google.com/dmca.html - Lorelle gives six steps that you can take to stop sploggers, such as how to contact them, and who to contact if they don’t respond. She also says what NOT to do.
- Ryan pointed me to a thread on SitePoint where a guy’s whole site was being lifted, design, database and all. The guy comes up with a creative piece of code that appears on the copycat site insulting the current owner, but it’s not a perfect workaround. He explains how he found out about this:
I just noticed that a few of the pages visited were mywords.info/… rather than teleclick.ca/… If the owner of MyWords hadn’t been stupid enough to keep my StatCounter code on his copy of the site, I might not have found out about it for months.
The surest way to locate mirrors of your website, however, is simply to invest a few minutes a week Googleing selections of your own content and checking for ripoffs. You’ll likely find plenty of stolen content from your sites if they’re popular enough, and can ask the re-publishers to remove it, or give you proper credit, depending on your policy. - I checked one of my scrapers’ page source and noticed that they’re using FeedBurner to track their feeds, and scraping my FeedBurner feed (as opposed to the regular site feed). They’re also using Google Analytics to track site stats. I haven’t done this yet, but I plan on contacting FeedBurner and Google about this user. I’m guessing Google will have a particular interest in making sure that FeedBurner feeds aren’t being abused.
- A few readers suggested filing DMCA (Digital Millenium Copyright Act) notices with the host of the splogger, but aside from the fact that I suspect that this is about as effective as the paper it’s written on, it doesn’t apply to non-Americans. So if the splogger or splogee is not American, it seems this won’t apply.
- Use the Copyfeed WordPress plugin (see step 1 under Part 1 above), or any other plugin that adds a footer to your feed. I use Copyfeed, since it allows you to do a whole bunch of useful things to your feed, but most important I have put a copyright notice in my feed footer with a link back to my site. This way, at the very least, if someone finds my content elsewhere on the web and they like it, they can easily find my site. Another similar plugin that does the same thing is Joost de Valk’s RSS Footer plugin. Joost’s plugin automatically adds a link back to the original post in the footer as well. (Hat tip to Glenn Dixon for that one.)
- Some people suggest using the FeedEntryHeader WordPress plugin which adds a copyright statement and a link to the original article to the top of your feed entries. However, I’ve seen quite a few sites appear in Google Alerts where the excerpt from the post being cited is a header stating that if you’re reading this post off-site, it’s being scraped. But we want Google to scrape our sites and recommend it to others, and having that text appear in the Alert is not so user friendly.
- The AntiLeech WordPress plugin is for those of us who don’t just want to stop sploggers, but want to get back at them as well. AntiLeech doesn’t prevent sploggers from accessing your site; “it produces a fake set of content especially for them that includes links back to your site (and [his], too, ok?) and sends it only to them.”
- Only publish a partial feed. This way, if your feed is scraped, readers who want to read the whole thing will be forced to click on the “Read More” link, and will be taken to your site. The drawback? Now your feed will be a partial feed. I know that I personally don’t have patience for partial feeds, and I don’t read them, since what’s the point of having a feed if you’re forcing me to visit your site? There’s a reason I’m using feeds, and it’s because I don’t have time and patience to open up every post in its own window. Since I feel this way, I really wouldn’t want to do that to my readers. And anyway, does everyone have to suffer because of a bunch of miserable, blood-sucking sploggers?
Even with all the steps above, I suspect that the sploggers will always retain the upper hand and we will never be able to completely stop them, or any of the other dark and sleazy types lurking on the web. If we could visualize the web, I bet the dark part takes up the majority of the web, and is probably growing faster too since it’s so much easier to crank out stolen or lowest-common-denominator content than good, useful, high-quality content.
Category: Tips
First off, thank you for drawing attention to this issue and for your providing a well-rounded article on the topic. Over all, this is a great summary of many of the options have when it comes to spam blogging.
That being said, I have to post a correction to your thoughts about the DMCA.
First, the DMCA does protect those outside of the U.S. It offers the same protections to copyright holders outside the country as within. The only stipulation is that the site has to be hosted within the U.S. However, you have to work hard to find sites that are not hosted in the U.S. at this time.
It is possible for an Australian man to use the DMCA against an person in Germany so long as the hosting account involved is within the U.S.
However, even if the site is in another country, many other nations have similar takedown provisions including Australia, the EU and, soon, Canada.
As far as it not being worth the paper it is printed on, I can’t testify to your experiences, but of the over 650 plagiarists I’ve stopped, I’d say 2/3 to 3/4 were with the DMCA.
For the most part, hosts respond quickly and effectively to DMCA notices. However, they have to be submitted in the proper format to the proper agent. If you need that information, I have a template and DMCA contact information on my site.
I would say, as a percentage, it works many times more often than contacting the spam blogger. But that is just my experience.
On that note, thank you again for drawing attention to this. I’m glad to see more and more sites taking this issue up!
This is really great information! Thanks for sharing and I’m off to install the plug in now…
Jonathan – my opinion about the DMCA was just me being cynical. Many Acts are passed and then they just kind of die off, so I figured this must be the same. But I guess I’m wrong, and I’m especially glad to hear that it applies to non-Americans if their host is in the States.
By the way, I contacted the major splogger who is scraping this site, and had the chutzpah to say that what he is doing is ok because his site is simply like a giant, public RSS feed, and RSS feeds are ok, right?
Lynne – you’re very welcome. May you be blessed with much un-sploginess.
Miriam, I found your great article through the scraper’s site. It’s a sad world we live in that I’ve become an expert in telling which are scraper sites and which aren’t. Good work on putting your “signature” at the end of the post.
Every blogger, from beginner to expert, is being scraped. Unfortunately, too many feel helpless. Thanks to the work of Jonathan Bailey, many are understanding that they aren’t not helpless victims and that here are ways to fight back within the laws.
Thanks for spreading the word and setting an example!
Hi Lorelle! Sploggers are a pain. They make me lose faith in the Internet. But at least we can try to stop them. Thanks for your great posts on the subject!
[...] I discovered a great resource with steps on how to prevent splogging on your site: 10 Steps to A More Splog-Free WordPress Blog. It is quite informative and offers lots of ways to discover if you’re being splogged and methods [...]
Thanks for sharing this information. I have been a a victim of “Sploggers”, also. It’s a shame the Internet has gone down the pan to bloggers wanting to just make money.
I like the approach that Joost takes – making the scraping sploggers work for YOU!
http://www.joostdevalk.nl/make-the-scrapers-work-for-you/
Thanks Glenn! I updated the post with the link to Joost’s plugin, since his plugin also adds a link back to the original post in the RSS footer, which is really smart.
10 steps to a more splog-free WordPress blog | WordPressGarage.com…
Is your blog being scraped? Do you find your posts copied and used by splogs? Learn how to prevent this and what to do when this still happens….
I found some of my articles “stolen” like this and I was shocked at first since it was something really new to me. I’ll try to take all these tips into account so that such problems would occur less frequently.
[...] try to assess needed changes which can be remedied temporarily or you can wait for the necessary plug-in to go into circulation. unprotected blogs can get over whelmed in a few days, overwhelming the [...]