apasionados

<p>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.</p>
<blockquote>
<p>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 <strong>not to crawl and index</strong> parts of this website.</p>
</blockquote>
<p>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.</p>
<p>This plugin also blocks the search pages from WordPress from getting indexed.</p>
<p><strong>Please only activate this plugin if you know what you’re doing</strong>.</p>
<h4>What can I do with this plugin?</h4>
<p>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.</p>
<h4>What ideas is this plugin based on?</h4>
<p>None. We needed a fast solution to add these lines to the robots.txt file and this was the solution we coded.</p>
<h4>What is the robots.txt file?</h4>
<p>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.</p>
<p>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.</p>
<h4>System requirements</h4>
<p>PHP version 7.1 or greater.<br />
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>.</p>
<h4>How to get this plugin in your Language!</h4>
<p>The first release is avaliable in English and Spanish. In the “languages” folder we have included the necessary files to translate this plugin.</p>
<p>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.</p>
<p>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.</p>
<h4>Further Reading</h4>
<p>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>.</p>
<h3>Contact</h3>
<p>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>.</p>


Block eCommerce Assets via robots.txt

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

Matthew Batchelder

<p>Have you ever wanted to get debug output sent to you from WordPress without interrupting the flow of the page?<br />
Do you ever wish you could get debug output from <em>other users’</em> sessions so you don’t have to:</p>
<ul>
<li>Log in as them</li>
<li>Asking them to look at debug output themselves (bleh)</li>
<li>Or try in vain to re-create their issue</li>
</ul>
<p>This plugin allows you to send debug messages via UDP to a <a href="https://github.com/borkweb/jabberbot" rel="nofollow ugc">Jabber Bot</a> that can then route<br />
the debug information to your IM client.</p>
<p><em>Note: This plugin sends the messages via UDP.  The receiving end doesn’t necessarily need to be a Jabber bot…it could be anything you want<br />
(e.g. email bot, logger, whatever).  My implementation is a Jabber Bot on my local dev environment 🙂</em></p>
<h4>Usage</h4>
<p>To send debug messages, simply call:</p>
<pre><code>do_action( 'debug_robot', $message [, $target ]);
</code></pre>
<ul>
<li><strong>$message</strong>: Message to send to your jabber bot.</li>
<li><strong>$target</strong>: <em>(optional)</em> Email address that your jabber bot will route the message to.</li>
</ul>
<p>To receive debug messages, you will need to have:</p>
<ul>
<li>Your <a href="https://github.com/borkweb/jabberbot" rel="nofollow ugc">Jabber Bot</a> installed and configured.</li>
<li>The Jabber Bot must be running.</li>
<li>You must have friended your robot’s jabber account with another jabber account (e.g. your Google account).</li>
<li>You must be signed into Google Talk in some way shape or form so that your jabber bot can IM you.</li>
</ul>
<p><em>Note: If your Jabber Bot isn’t running, no worries.  UDP doesn’t wait for a response so it won’t impact your WordPress instance…you just won’t get the messages that<br />
are sent until your bot is running 🙂</em></p>
<h3>Credits</h3>
<p>This code was largely written by <a href="https://github.com/abackstrom" rel="nofollow ugc">@abackstrom</a> with some additions by me while we worked at <a href="https://github.com/PlymouthState" rel="nofollow ugc">@PlymouthState</a>. I then ported it into a WordPress plugin.</p>


WP Debug Robot

An unobtrusive debugging tool for WordPress

Block eCommerce Assets via robots.txt vs WP Debug Robot