A blog post linking to one of my blog posts has been scraped dozens of times. Recently, it was scraped by eight different sites in the same day. The eight trackbacked sites turned out to have a single owner/webmaster using their auto-blogging scraper across multiple splog sites. I’ve let the blogger know – after the second time it happened – and now that it’s happened multiple times, it’s time to change strategies.
It’s now time to work together.
Have you received multiple trackbacks over time from an blog post with a link to yours and the investigation finds that it isn’t the original site but a scraper? What do you do?
When a trackback to a blog post shows up for the first time in my Comments Panel, I check it out to see what they are saying about my blog and blog post. Trackbacks are a great way of learning what others are saying about what you say, connecting us all together within this so called “web” world we live in.
The second time a trackback appears that looks like the first, I’m suspicious. While we are all known to be redundant from time to time, I don’t think we are that bad at it. I check it out and if it is not on the original site, I check the article for intrasite links to the original source. It only takes a few seconds to spot a fake.
An intrasite link is any link to the original blog that the blogger put into their post such as a link to a reference article they wrote or a direct link to their own blog’s URL, which some WordPress Plugins for feeds and copyrights inject automatically into blog feeds. Including at least one intrasite link in every blog post is a good habit to get into, even if it is to reference another of your blog posts and increase exposure of your own blog posts. It also helps track trackbacking scrapers.
If I find an intrasite link, then I assume that the blogger has received a trackback and will take care of the matter of the copyright infringement.
If a third, fourth or more trackback appears from the same or multiple splogger/scrapers, then I notify the blog author that their content is being ripped off and ask if they need help responding to these copyright infringements.
Most of the time, the authors are either working on responding and taking action, or welcome the alert, thrilled to be warned.
When the tenth or more trackback appears over time, then I start responding myself in the comments requesting the scraper remove the copyright violating content and warn them that the original author has been contacted, and forward the new scraper site URL to the original author.
Why Bother Warning Fellow Bloggers?
Jonathan Baliey of Plagiarism Today, my friend and fellow blogger here on the Blog Herald, and I agree that we have to all work together to stop copyright infringement and the abuse of our content by scrapers and sploggers using auto-feed scraping tools to take our blog posts and put them on their income generating sites without our permission – or a piece of the pie. If we all work together to educate and stop the abuse, and to control the usage of our content, the web will be a much nicer place.
I warn fellow bloggers because I know I would want to know. I also warn them because I know we can work together to stop copyright infringement. I also warn them because it’s a great way to get to know fellow bloggers.
By reporting scrapers, I’ve met some wonderful bloggers I wouldn’t ordinarily have time to meet. Over time, some have even become friends. We trade war stories, tips for blogging, and even have guest blogged on each other’s blogs. Overcoming adversity is a great way to build relationships.
It’s also a good practice. It’s nice. It’s kind. It’s also supportive.
Wouldn’t you want to know if someone is abusing your content? Do you?
The author of Lorelle on WordPress and the fast-selling book, Blogging Tips: What Bloggers Won't Tell You About Blogging, as well as several other blogs, Lorelle VanFossen has been blogging for over 15 years, covering blogging, WordPress, travel, nature and travel photography, web design, web theory and development extensively as web technologies developed.