Virtual Robots.txt


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.

Por defecto, el plugin Virtual Robots.txt admite el acceso a las partes de WordPress a las que los robots como Google necesitan acceder. Otras partes son bloqueadas.

If the plugin detects an existing XML sitemap file, a reference to it will be automatically added to your robots.txt file.


  1. Sube la carpeta pc-robotstxt al directorio /wp-content/plugins/
  2. Activa el plugin desde el menú ‘Plugins’ de WordPress
  3. Once you have the plugin installed and activated, you’ll see a new Robots.txt menu link under the Settings menu. Click that menu link to see the plugin settings page. From there you can edit the contents of 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.

¿Funciona en instalaciones de WordPress en sub-directorios?

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.

¿Este plugin modifica entradas, páginas o categorías?

No, no lo hace.

¿Por qué bloquea el plugin ciertas carpetas y archivos por defecto?

Por defecto, el robots.txt virtual esta establecido para bloquear los archivos y carpetas de WordPress que no deben ser accesibles para los buscadores. Si no estás acuerdo con los ajustes por defecto, puedes cambiarlos fácilmente.


19 de septiembre de 2023 4 respuestas
I had an issue that I believed was being caused by the plugin but the plugin author was very quick to help and clear up the issue. Great and helpful customer service – thanks!
23 de noviembre de 2018
Works great and easy to use and customise. It already set by default the directories that need to be left out of Search Engines scanning/indexing… Very happy with it!
18 de marzo de 2018 1 respuesta
What I saw wasn’t what I got. The XML sitemap wasn’t included in the robots.txt file, even thought this was described as a feature that should work out of the box. In addition to that, upon installing this plugin, it blocked certain directories without asking. Lastly, it inserts a line at the top of the file, promoting the plugin. That should be an optional feature that users are empowered to turn off. All in all, it offers the functionality, but falls short and disappoints in other areas.
29 de diciembre de 2016
I thought this would be simple. Sure sounds simple. But after I saved your suggested text to my brand new «virtual robots.txt», I clicked the link where it says «You can preview your robots.txt file here (opens a new window). If your robots.txt file doesn’t match what is shown below, you may have a physical file that is being displayed instead.» That new window shows text that is indeed different from the plugin’s. So I understand that to mean there’s a physical robots.txt file on my server. So which one is actually going to be used? Your FAQ offers this: Q: Will it conflict with any existing robots.txt file? A: If a physical robots.txt file exists on your site, WordPress won’t process any request for one, so there will be no conflict. If a physical file exists, WP won’t process ANY request for one? This SOUNDS like WP will ignore BOTH the physical file AND your virtual one. In which case, what’s the point? Might as well not have one, it seems to me. When I manually go to, I see what’s in the physical file, not what the plugin saved. So… is it working? I don’t know! Should I delete the physical file and assume the virtual one will work? I don’t know! Should I delete this plugin and edit the physical file manually? Most likely. 2 stars instead of 1 because I appreciate getting the suggested lines to include in my file.
Leer todas las 9 reseñas

Colaboradores y desarrolladores

«Virtual Robots.txt» es un software de código abierto. Las siguientes personas han colaborado con este plugin.


«Virtual Robots.txt» está traducido en 1 idioma. Gracias a los traductores por sus contribuciones.

Traduce «Virtual Robots.txt» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios


  • Fix to prevent the saving of HTML tags within the robots.txt form field. Thanks to TrustWave for identifying this issue.


  • 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.


  • Versión inicial.