error

Welcome to a whole new way of keeping your blog, forum, guestbook, wiki or 
content management system free of link spam. Bad Behavior is a PHP-based 
solution for blocking link spam and the robots which deliver it.
Thousands of sites large and small, like SourceForge, GNOME, the U.S. 
Department of Education, and many more, trust Bad Behavior to help reduce 
incoming link spam and malicious activity.
Bad Behavior complements other link spam solutions by acting as a gatekeeper, 
preventing spammers from ever delivering their junk, and in many cases, from 
ever reading your site in the first place. This keeps your site’s load down, 
makes your site logs cleaner, and can help prevent denial of service 
conditions caused by spammers.
Bad Behavior also transcends other link spam solutions by working in a 
completely different, unique way. Instead of merely looking at the content of 
potential spam, Bad Behavior analyzes the delivery method as well as the 
software the spammer is using. In this way, Bad Behavior can stop spam attacks 
even when nobody has ever seen the particular spam before.
Bad Behavior is designed to work alongside existing spam prevention services 
to increase their effectiveness and efficiency. Whenever possible, you should 
run it in combination with a more traditional spam prevention service.
Bad Behavior works on, or can be adapted to, virtually any PHP-based Web 
software package. Bad Behavior is available natively for WordPress, MediaWiki, 
Drupal, ExpressionEngine, and LifeType, and people have successfully made it 
work with Movable Type, phpBB, and many other packages.
Installing and configuring Bad Behavior on most platforms is simple and takes 
only a few minutes. In most cases, no configuration at all is needed. Simply 
turn it on and stop worrying about spam!
The core of Bad Behavior is free software released under the GNU Lesser General 
Public License, version 3, or at your option, any later version.
<h3>Release Notes</h3>
<h4>Bad Behavior 2.2 Known Issues</h4>
<ul>
<li>
Bad Behavior 2.2 requires MySQL 5.0 or later and PHP 5.2 or later.
</li>
<li>
CloudFlare users must enable the Reverse Proxy option in Bad Behavior’s 
settings. See the documentation for further details.
</li>
<li>
Bad Behavior is unable to protect internally cached pages on MediaWiki. 
Only form submissions will be protected.
</li>
<li>
When upgrading from version 2.0.19 or prior on MediaWiki and WordPress, 
you must remove the old version of Bad Behavior from your system manually 
before manually installing the new version. Other platforms are not 
affected by this issue.
</li>
<li>
Bad Behavior on WordPress requires version 3.1 or later. Users of older 
versions should upgrade WordPress prior to installing Bad Behavior.
</li>
<li>
On WordPress when using WP-Super Cache, Bad Behavior must be enabled in 
WP-Super Cache’s configuration in order to protect PHP Cached or Legacy 
Cached pages. Bad Behavior cannot protect mod_rewrite cached (Super Cached) 
pages.
</li>
<li>
When using Bad Behavior in conjunction with Spam Karma 2, you may see PHP 
warnings when Spam Karma 2 displays its internally generated CAPTCHA. This 
is a design problem in Spam Karma 2. Contact the author of Spam Karma 2 for 
a fix.
</li>
</ul>

Bad Behavior

Although sometimes it can be tricky if you get a false positive, those are pretty rare (haven't seen one in a couple years). Works well to keep bad actors off your site.

works nicely

Bad Behavior prevents spammers from ever delivering their junk, and in many
cases, from ever reading your site in the first place.

apasionados

This plugin adds lines to the virtual robots.txt file that WordPress creates automagically if the file is not present physically on the server to block some WooCommerce assets and Search pages that should not be indexed.
<blockquote>
Please be aware of what this plugin does exactly: If you activate the plugin it will add some lines to the robots.txt file to tell search engine bots to not to crawl and index parts of this website.
</blockquote>
This plugin blocks certain pages from WooCommerce (“add-to-cart”, “orderby”, “filter”, cart, account, checkout, …) from being crawled by search engines. Crawling these links normally requires a lot of CPU, memory and bandwidth because they are not cacheable and/or create crawling loops (while they are useless). Optimizing your robots.txt when running a WooCommerce online store allocates more processing power for pages that really matter.
This plugin also blocks the search pages from WordPress from getting indexed.
Please only activate this plugin if you know what you’re doing.
<h4>What can I do with this plugin?</h4>
This plugin adds the necessary lines to the virtual robots.txt file that WordPress creates automagically to block to block WooCommerce assets that should not be indexed and the Search pages.
<h4>What ideas is this plugin based on?</h4>
None. We needed a fast solution to add these lines to the robots.txt file and this was the solution we coded.
<h4>What is the robots.txt file?</h4>
The robots.txt file is a plain text file located at the root folder of a domain (or subdomain) which tells web crawlers (like Googlebot) what parts of the website they should access and index.
The first thing a search engine crawler looks at when it is visiting a page is the robots.txt file and it controls how search engine spiders see and interact with the web pages.
<h4>System requirements</h4>
PHP version 7.1 or greater. 
We require 7.1 or higher because we believe that everybody should be running a modern PHP version. When releasing this plugin <a href="https://wordpress.org/about/requirements/" rel="ugc">WordPress recommends PHP 7.4 or higher</a>.
<h4>How to get this plugin in your Language!</h4>
The first release is avaliable in English and Spanish. In the “languages” folder we have included the necessary files to translate this plugin.
If you would like the plugin in your language and you’re good at translating, please use the <a href="https://translate.wordpress.org/projects/wp-plugins/block-ecommerce-assets-via-robots-txt/" rel="nofollow ugc">native WordPress Translation</a> functionality.
New to Translating a plugin? First read through the <a href="https://make.wordpress.org/polyglots/handbook/tools/glotpress-translate-wordpress-org/" rel="nofollow ugc">Translator Handbook</a>, then select your locale at <a href="https://translate.wordpress.org/" rel="nofollow ugc">Translating WordPress</a> and finally go to the <a href="https://translate.wordpress.org/projects/wp-plugins/block-ecommerce-assets-via-robots-txt/" rel="nofollow ugc">translation page for this plugin</a> to translate it.
<h4>Further Reading</h4>
You can access the description of the plugin in Spanish at: <a href="https://apasionados.es/blog/" rel="nofollow ugc">Block WooCommerce Assets via robots.txt en español</a>.
<h3>Contact</h3>
For further information please send us an <a href="https://apasionados.es/contacto/index.php?desde=wordpress-org-block-woocommerce-assets-robots-txt" rel="nofollow ugc">email</a>.

Block eCommerce Assets via robots.txt

Blocks some WooCommerce assets and Search pages that should not be indexed through robots.txt

Bad Behavior vs Block eCommerce Assets via robots.txt