PC Robots.txt automatically creates a virtual robots.txt file for your blog. Your robots.txt file can be easily edited from the plugin settings page.
|Author:||Marios Alexandrou (profile at wordpress.org)|
|WordPress version required:||4.0|
|WordPress version tested:||5.4.1|
|Added to WordPress repository:||13-06-2009|
|Total downloads:||278 726|
|Active installs:||50 000+|
Click to start download
Virtual Robots.txt is an easy (i.e. automated) solution to creating and managing a robots.txt file for your site. Instead of mucking about with FTP, files, permissions ..etc, just upload and activate the plugin and you’re done.
By default, the Virtual Robots.txt plugin allows access to the parts of WordPress that good bots like Google need to access. Other parts are blocked.
If the plugin detects an existing XML sitemap file, a reference to it will be automatically added to your robots.txt file.
Will it conflict with an existing robots.txt file?
If a physical robots.txt file exists on your site, WordPress won’t process any request for one, so there will be no conflict.
Will this work for sub-folder installations of WordPress?
Out of the box, no. Because WordPress is in a sub-folder, it won’t “know” when someone is requesting the robots.txt file which must be at the root of the site.
Does this plugin modify individual posts, pages, or categories?
No it doesn’t.
Why does the default plugin block certain files and folders?
By default, the virtual robots.txt is set to block WordPress files and folders that don’t need to be accessed by search engines. Of course, if you disagree with the defaults, you can easily change them.
- Fix for PHP 7. Thanks to SharmPRO.
- Undoing last fixes as they had unintended side-effects.
- Further fixes to issue with newlines being removed. Thanks to FAMC for reporting and for providing the code fix.
- After upgrading, visit and re-save your settings and confirm they look correct.
- Fixed bug where newlines were being removed. Thanks to FAMC for reporting.
- Fixed bug where plugin assumed robots.txt would be at http when it may reside at https. Thanks to jeffmcneill for reporting.
- Fixed bug for link to robots.txt that didn’t adjust for sub-folder installations of WordPress.
- Updated default robots.txt directives to match latest practices for WordPress.
- Plugin development and support transferred to Marios Alexandrou.
- Now uses do_robots hook and checks for is_robots() in plugin action.
- Added support for existing sitemap.xml.gz file.
- Added link to settings page, option to delete settings.
- Initial release.