Replaces the default virtual robots.txt generated by WordPress with an editable one, and deletes any physical robots.txt file that may already exist.<\/p>\n\n
Virtual Robots.txt is a simple WordPress plugin for easily editing the robots.txt content on your website. Because the goal of any CMS is to be as self-contained as possible, and because WordPress itself contains a default \"virtual\" robots.txt file generated by the Instead of simply using the built-in robots_txt filter, however, this plugin creates a new hook for the main parse_query action to ensure that no other WordPress plugin (or theme) can alter the contents of robots.txt after it has been edited. Although the current version does not directly \"disable\" the robots_txt filter, in effect that filter is completely ignored by ending the hook sequence before robots_txt can be called.<\/p>\n\n Unlike similar plugins (or WordPress itself), it includes a default \"allow all\" ruleset upon activation. The theory behind this is that playing things safe is always the best course of action for inexperienced webmasters; allowing all robots to access all site content is not only recommended by Google but also makes sense in the vast majority of cases. While the form value will persist on plugin deactivation, the option value will be completely deleted in the case of the plugin being removed from your site, in an effort at clean code and to avoid any confusion or conflicts.<\/p>\n\n The plugin disables 100% the robots_txt filter because stops execution before this filter is triggered. It uses a very early hook \"parse_query\" that contains the context and, for a \/robots.txt request, echoes the form content and ends execution of PHP.<\/p>\n\n The normal load sequence for When using this plugin, the sequence changes:<\/p>\n\n This plugin has been designed for use on LEMP (Nginx) web servers with PHP 7.0 and MySQL 5.7 to achieve best performance. All of our plugins are meant for single site WordPress installations only; for both performance and security reasons, we highly recommend against using WordPress Multisite for the vast majority of projects.<\/p>\n\n This plugin generates multiple Admin Notices<\/a> in the WP Admin dashboard. The first is a notice that fires during plugin activation which recommends several related free plugins that we believe will enhance this plugin's features; this notice will re-appear approximately once every 6 months as our code and recommendations evolve. The second is a notice that fires a few days after plugin activation which asks for a 5-star rating of this plugin on its WordPress.org profile page. This notice will re-appear approximately once every 9 months. These notices can be dismissed by clicking the (x)<\/strong> symbol in the upper right of the notice box. These notices may annoy or confuse certain users, but are appreciated by the majority of our userbase, who understand that these notices support our free contributions to the WordPress community while providing valuable (free) recommendations for optimizing their website.<\/p>\n\n If you feel that these notices are too annoying, than we encourage you to consider one or more of our upcoming premium plugins that combine several free plugin features into a single control panel, or even consider developing your own plugins for WordPress, if supporting free plugin authors is too frustrating for you. A final alternative would be to place the defined constant mentioned below inside of your Note: This defined constant will only affect the notices mentioned above, and will not affect any other notices generated by this plugin or other plugins, such as one-time notices that communicate with admin-level users.<\/p>\n\n This plugin was partially inspired either in \"code or concept\" by the open-source software and discussions mentioned below:<\/p>\n\n We invite you to check out a few other related free plugins that our team has also produced that you may find especially useful:<\/p>\n\n We invite you to check out a few premium plugins that our team has also produced that you may find especially useful:<\/p>\n\n We thank the following groups for their generous contributions to the WordPress community which have particularly benefited us in developing our own free plugins and paid services:<\/p>\n\n We released this plugin in response to our managed hosting clients asking for better access to their server, and our primary goal will remain supporting that purpose. Although we are 100% open to fielding requests from the WordPress community, we kindly ask that you keep the above mentioned goals in mind, thanks!<\/p>\n\n\n For Nginx servers (without Apache in front) make sure location = \/robots.txt {\n try_files $uri $uri\/ \/index.php?$args;\n allow all;\n log_not_found off;\n access_log off;\n}<\/p><\/li>\n<\/ol>\n\n\n For Nginx servers (without Apache in front) make sure location = \/robots.txt {\n try_files $uri $uri\/ \/index.php?$args;\n allow all;\n log_not_found off;\n access_log off;\n}<\/p><\/li>\n<\/ol><\/dd>\n Yes. Currently its a totally virtual robots.txt solution that will \"delete\" any physical robots.txt that exists. The reason for this is to make WordPress as self-contained as possible, and since there is no real downside to managing robots.txt in such a virtual fashion. In future versions, we may create the option to switch between either a virtual or physical file, but for now its totally virtual as explained.<\/p><\/dd>\n This plugin will NOT edit a physical robots.txt file and only offers a virtual robots.txt content via the wp_options table.<\/p><\/dd>\n Under the Settings menu on the left hand site, a new link is generated called Robots.txt<\/p><\/dd>\n Absolutely not. All wp_options are cached by default in WordPress and loaded prior to other data. In a theoretical world, a physical robots.txt file may in fact load more quickly, but all purposes both humans and robots wouldn't notice a difference when using a virtual file. Please note that if you are using CloudFlare or other special cache systems, you may need to clear those to see your robots.txt update correctly. However, traditional caches such as page cache plugins or oboject caching (i.e. Memcached or Redis) should not effect the content of this plugin.<\/p><\/dd>\n Make sure you are sending requests for the static file robots.txt via your PHP proessor such as PHP-FPM:<\/p>\n\n Please avoid leaving negative reviews in order to get a feature implemented. Instead, we kindly ask that you post your feedback on the wordpress.org support forums by tagging this plugin in your post. If needed, you may also contact our homepage.<\/p><\/dd>\n\n<\/dl>\n\n\nwp_options<\/code> table, it makes sense to maintain a virtual robots.txt whenever possible to make site management and migration more controlled.<\/p>\n\n\/robots.txt<\/code> requests:<\/p>\n\n1. (load plugin hooks)\n2. init\n3. wp\n4. parse_query\n5. template_redirect\n6. robots_txt <- filter\n<\/code><\/pre>\n\n1. (load plugin hooks)\n2. init\n3. wp\n4. parse_query <- detect context via WP is_robots method, show the form content and ends execution.\n<\/code><\/pre>\n\nCompatibility<\/h4>\n\n
Plugin Features<\/h4>\n\n
\n
\n
WP Admin Notices<\/h4>\n\n
wp-config.php<\/code> file to manually hide this plugin's nag notices:<\/p>\n\ndefine('DISABLE_NAG_NOTICES', true);\n<\/code><\/pre>\n\nCode Inspiration<\/h4>\n\n
\n
Recommended Plugins<\/h4>\n\n
\n
Premium Plugins<\/h4>\n\n
\n
Special Thanks<\/h4>\n\n
\n
Disclaimer<\/h4>\n\n
\n
\/wp-content\/plugins\/virtual-robotstxt-littlebizzy<\/code><\/li>\ntry_files<\/code> sends requests to WordPress:<\/p>\n\n\n
\n
\/wp-content\/plugins\/virtual-robotstxt-littlebizzy<\/code><\/li>\ntry_files<\/code> sends requests to WordPress:<\/p>\n\nlocation = \/robots.txt {\n try_files $uri $uri\/ \/index.php?$args;\n allow all;\n log_not_found off;\n access_log off;\n}\n<\/code><\/pre><\/dd>\n1.0.8<\/h4>\n\n
\n
1.0.7<\/h4>\n\n
\n
1.0.6<\/h4>\n\n
\n
DISABLE_NAG_NOTICES<\/code><\/li>\n<\/ul>\n\n1.0.5<\/h4>\n\n
\n
1.0.4<\/h4>\n\n
\n
1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n