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.
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.
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.
What can I do with this plugin?
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.
What ideas is this plugin based on?
None. We needed a fast solution to add these lines to the robots.txt file and this was the solution we coded.
What is the robots.txt file?
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.
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 WordPress recommends PHP 7.4 or higher.
How to get this plugin in your Language!
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 native WordPress Translation functionality.
New to Translating a plugin? First read through the Translator Handbook, then select your locale at Translating WordPress and finally go to the translation page for this plugin to translate it.
You can access the description of the plugin in Spanish at: Block WooCommerce Assets via robots.txt en español.
For further information please send us an email.
- First you will have to upload the plugin to the
- Then activate the plugin in the plugin panel. There are no settings.
Why did you make this plugin?
We created this plugin to be able to append the lines to block some WooCommerce assets via robots.txt without having to upload a robots.txt file.
Does Block WooCommerce Assets via robots.txt make changes to the database?
No. The plugin doesn’t write any options or settings to the database.
How can I check out if the plugin works for me?
Install and activate. Have a look at the content of the robots.txt file in root of the domain.
How can I remove Block WooCommerce Assets via robots.txt?
You can simply activate, deactivate or delete it in your plugin management section. There are no options stored in the database so you can delete it also via FTP and everything will be removed.
What happens if there is a physical robots.txt file on the server?
This plugin makes changes to the virtual robots.txt file generated automagically by WordPress and doesn’t work with a physical robots.txt file. In order to use this plugin you need to remove the physical robots.txt file from your server. Please delete the robots.txt file via FTP or Server Panel before using this plugin. We check this on activation (and only on activation). If we find a physical robots.txt file the plugin can’t be activated until the file is removed. Please keep in mind that we only check it on plugin activation and after activation we don’t check it any more; so if you upload a robots.txt file to the root of the domain once the plugin is activated, the plugin will have no effects but you will not receive a warning.
What happens if WordPress is installed in a subdirectory?
WordPress must be installed in top-level directory of the web server. Please note that the robots.txt must be in the top-level directory of your web server. If WordPress is installed in a subdirectory this plugin will not be effective because the robots.txt file generated by WordPress in the subdirectory will be ignored by the bots. Please note that we don\’t check this. You can read more about the robots.txt standard here robotstxt.org: How to create a /robots.txt file and Where to put it.
Are there any known incompatibilities?
Please don’t use it with WordPress MultiSite, as it has not been tested.
The plugin has similar functionality as the Virtual Robots.txt and the Better Robots.txt – Index, Rank & SEO booster plugin; both are not compatible with our plugin as they remove all the virtual WordPress robots.txt content and create their own. The directives our plugin creates are not added to the robots.txt file these plugins generate as they don’t use the standard functions of WordPress to append information to them.
What WooCommerce relatead pages does this plugin block?
Are there any server requirements?
Yes. The plugin requires a PHP version 7.1 or higher and we recommend using PHP version 7.4 or higher. The plugin has been tested with PHP up to 7.4. When releasing this plugin WordPress recommends PHP 7.4 or higher.
Do you make use of Block WooCommerce Assets via robots.txt yourself?
Of course we do. That’s why we created it. ðŸ˜‰
There are no reviews for this plugin.
Contributors & Developers
“Block eCommerce Assets via robots.txt” is open source software. The following people have contributed to this plugin.Contributors
Translate “Block eCommerce Assets via robots.txt” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
- Updated translation text domain to match plugin slug (“Since WordPress 4.6 the Text Domain header is optional because it must be the same as the plugin slug” – More info at Text Domains).
- First official release.