WordPress.org

Plugin Reviews

ScrapeBreaker

A combination of frame-breaker and scraper protection. Protect your website content from both frames and server-side scraping techniques.

9 reviews
Average Rating
4.4 out of 5 stars
recomended!
By , for WP 4.2.4

this is important and recomended plugin that every webmaster should have it

No problems so far
By , for WP 4.2.3

So far so good, when we are scraped at least it appends the true author name and original site link.

Has worked very well
By , for WP 4.2.3

Since I have had no trouble with any party trying to pirate my site it must be working very well.

Don't like the guilt message on rating
By , for WP 4.2.3

I like the plugin and it seems to be working for most scraper sites but there are some it does not work on.

What I really don't like it the message about using the plugin and rating it that can't be closed unless you say you have already rated the plugin. Not nice.

Disappointed
By , for WP 4.1.1

I believe this plugin destroys Google indexing due to redirection inserted in header. Google webmaster tools reports only 1 indexed page out of several hundred crawled because of a permanent 301 redirect.

<script type="text/javascript">
// <![CDATA[
function strpos (haystack, needle, offset) { var i = (haystack+'').indexOf(needle, (offset || 0)); return i === -1 ? false : i; }
var thispage = "http://somedomain.com/";
if (strpos(top.location,thispage)!==0||window!=top){top.location.href=thispage;window.open(thispage,'_top');}
// ]]>
</script>

This plugin breaks multisites and will send all visitors to any domain to the main site.

Excellent tool to protect your work!
By , for WP 4.1

Thank you so much for this important plugin that provies a mush have functionality!

The best
By , for WP 4.1

I tried an other one until I saw this one and I must say I'm glad I did cause I think this one may be the best.

We built this plugin with a lot of love, and hope you enjoy it too!
By Plugin Author, for WP 4.2.3

Hi, my name is Scott Allen and I proudly voted for my own plugin!

Yes, full disclosure, I'm the plugin developer. (Notice the awesome green bar by my name!)

We built this plugin with a lot of love, and hope you enjoy it too! :)

This plugin is one we developed to help client sites deal with other sites that try to frame theirs. We had tried every other frame breaker out there and we felt they all were lacking, which is why we built this one. Eventually we added capabilities to prevent much scraping as well. Unfortunately nothing can do this perfectly. So, yes, it's not perfect unfortunately, but we still believe this does as good a job as possible with the right balance of feature and speed.

Like you, we and our clients are real-life users of the plugin too. We are definitely partial to it. The good thing about knowing that the plugin author (and company, and clients...) is also a plugin user, is that if you experience issues, we experience them too, so we will definitely be motivated to fix them quickly!

Try it out and cast your own vote!

Sidenote: Should plugin authors be allowed to vote?
Sometimes people ask if a plugin developers should be allowed to vote for their own plugin. It's a good question. I think of it this way...WordPress.org is a democratic forum, and the whole point of a rating system is that it's a democratic process. Each person gets a vote, just like in an election, a presidential candidate (or any other elected official) is allowed to vote for himself. Why shouldn't they be? Plugin developers also put in a lot of time and energy into a plugin that they (hopefully) really believe in. In our case, we really believe in this plugin, which we hope you see from the positive responses about the plugin's performance and the quality of our support. (Which is all provided fro free by the way. We work hard to solve all issues within 24 hours if possible. A plugin author's 1 single vote is not going to skew the plugin's rating in the overall scheme of things, just like that elected official's 1 vote is not going to skew the overall election results. If people disagree with their rating, then they need to get out there and vote...give their own rating. That's how it works.

Another thing to consider, is that statistically for online rating systems, more people rate when they are dissatisfied than when they are satisfied, so ratings often tend toward the negative. Happy users or customers tend not to rate services. You can read up on this as Amazon, ebay, and Yelp have had to deal with this a lot. There are many trolls out there who give plugins 1 star reviews without ever reading the documentation or submitting support requests. This is something that all plugin authors understand and have to deal with...patiently, as frustrating as it is.

With Amazon and ebay, they have a system that, when a user is about to post a negative review, reminds them to get in touch with the vendor and try to resolve things first. WordPress.org would do well to have a system that requires a user post a support thread and wait 48 hours for a response before being allowed to post a 1 or 2 star review. In the end, that has much greater effect than a plugin author rating their plugin.

So, in the end, yes, I think plugin authors should be allowed to vote for their plugin.

Does Not Work on Bilingual Websites (using qTrnslate)
By , for WP 3.8.1

I have a bilingual site that uses qTranslate for creating additional language pages on the site. Every page and post has a equivalent post and page in the second.

After installing ScrapeBreaker all the pages in the second language get redirected to the first language. The problem is caused by this Javascript that is inserted into the page by the plugin:

<script type="text/javascript" async >
	// <![CDATA[
	var thispage = "http://shahrefarang.com/";
	if (top.location!=thispage){top.location.href=thispage}
	// ]]>
	</script>

Apparently the plugin does not work with qTranslate. I have not tried it with WPML but I think it might have the same problem there.

Note: The problem does not happen when you are logged in as Admin so you might not notice it when you are logged in but your website's visitors see the problem.

You must log in to submit a review. You can also log in or register using the form near the top of this page.