Necesito editar el archivo robots.txt: ¿dónde está?

[jerdog (Jeremy M)]

@codinghorror

@sam

The problem is that we store “latest” content in the search index which is pointless cause we never want people to land on “latest”

This statement makes zero sense to me, “latest” is the default homepage for Discourse so we absolutely do want people to land there.

Correct me if I am wrong, but Latest is the default display but not the default link, right? This has to do with the actual /latest link

[sam (Sam Saffron)]

@codinghorror

This statement makes zero sense to me, “latest” is the default homepage for Discourse so we absolutely do want people to land there.

We have every single page of latest in the index, the content is like quicksand and there is nothing in the homepage that is “site specific” and not quicksand which is a big problem:

We absolutely do not want people landing on page 2 / 3 etc.. page 1 maybe, but the content on page 1 keeps on changing.

This URL for example https://meta.discourse.org/latest?no_definitions=true&no_subcategories=false&page=2 is stored in the Google index.

I am reticent to change stuff though cause I do not know how the big Google will deal with us adding “dont store in index” directives here. Also people never land on these pages anyway cause Google automatically detects they are rubbish and do not send people there.

If there is anything super positive here, I guess it would be having a wonderful “HTML off” homepage that has useful enough content that search engines would send people to the page.

For example, it would be super nice if discourse community discussions ranked meta.discourse.org first cause we had a nice front page.

A simple fix here we can make that can give us lots of mileage is nice expansion of pinned posts:

They are stable content, we can expand that:

In fact we can even expand it a bit further for crawler views. Additionally we could list all the categories on the home page as well in the crawler view… there is a bunch of stuff we can do.

[Pham_Quyet_Nghi (Phạm Quyết Nghị)]

Hello!
this is my file

# See http://www.robotstxt.org/robotstxt.html for documentation on how to use the robots.txt file
#
User-agent: *
Disallow: /auth/cas
Disallow: /auth/facebook/callback
Disallow: /auth/twitter/callback
Disallow: /auth/google/callback
Disallow: /auth/yahoo/callback
Disallow: /auth/github/callback
Disallow: /auth/cas/callback
Disallow: /assets/browser-update*.js
Disallow: /users/
Disallow: /u/
Disallow: /my/
Disallow: /badges/
Disallow: /search
Disallow: /search/
Disallow: /tags
Disallow: /tags/
Disallow: /email/
Disallow: /session
Disallow: /session/
Disallow: /admin
Disallow: /admin/
Disallow: /user-api-key
Disallow: /user-api-key/
Disallow: /*?api_key*
Disallow: /*?*api_key*
Disallow: /groups
Disallow: /groups/
Disallow: /t/*/*.rss
Disallow: /tags/*.rss
Disallow: /c/*.rss


User-agent: mauibot
Disallow: /


User-agent: bingbot
Crawl-delay: 60
Disallow: /auth/cas
Disallow: /auth/facebook/callback
Disallow: /auth/twitter/callback
Disallow: /auth/google/callback
Disallow: /auth/yahoo/callback
Disallow: /auth/github/callback
Disallow: /auth/cas/callback
Disallow: /assets/browser-update*.js
Disallow: /users/
Disallow: /u/
Disallow: /my/
Disallow: /badges/
Disallow: /search
Disallow: /search/
Disallow: /tags
Disallow: /tags/
Disallow: /email/
Disallow: /session
Disallow: /session/
Disallow: /admin
Disallow: /admin/
Disallow: /user-api-key
Disallow: /user-api-key/
Disallow: /*?api_key*
Disallow: /*?*api_key*
Disallow: /groups
Disallow: /groups/
Disallow: /t/*/*.rss
Disallow: /tags/*.rss
Disallow: /c/*.rss

I read the tutorials above but I do not understand how to fix the question “Need to edit robots.txt file - where is it?”. Looking forward to receiving help from the community

This is the content to be want to update

# See http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
#
User-agent: *
Disallow: /auth/cas
Disallow: /auth/facebook/callback
Disallow: /auth/twitter/callback
Disallow: /auth/google/callback
Disallow: /auth/yahoo/callback
Disallow: /auth/github/callback
Disallow: /auth/cas/callback
Disallow: /assets/browser-update*.js
Disallow: /users/
Disallow: /u/
Disallow: /badges/
Disallow: /search
Disallow: /search/
Disallow: /tags
Disallow: /tags/

Thanks all

[Stranik (Evgeny)]

@Pham_Quyet_Nghi

I do not understand how to fix the question “Need to edit robots.txt file - where is it?”.

I think you can override the file in your own plugin.

app/views/robots_txt/index.erb

[Pham_Quyet_Nghi (Phạm Quyết Nghị)]

My archive directory is this

how to override the file in your own plugin

Thanks

[cpradio]

You will want to read the plugin development topics and then read this
https://meta.discourse.org/t/how-to-block-all-crawlers-but-googles/62431/4?u=cpradio

[Pham_Quyet_Nghi (Phạm Quyết Nghị)]

I really do not want to block the google search engine that I want to change by content in the robots.txt file

Why does my website not find such a directory /discourse/app/views ?

[Mittineague]

There is no robots.txt text file per se. It is a Ruby controller

app/controllers/robots_txt_controller.rb

[cpradio]

@Pham_Quyet_Nghi

I really do not want to block the google search engine that I want to change by content in the robots.txt file

Why does my website not find such a directory /discourse/app/views ?

You really need to read some of the Development topics, it explains all of that and more. The plugin should be trivial, to be honest. Or you can post something in Marketplace with a budget to see if someone will build it for you.

[j127]

@sam

we should probably add noindex tags on user pages

If that is added, could it be made into an overridable setting? I clicked on this link in the newsletter, because getting user pages indexed is also something we need. We’re hoping to add additional information to them and eventually redirect the old (indexed) user pages to the Discourse ones.

[j127]

@jerdog

we need to add /latest* to the Disallow list.

I was just noticing this problem on one of my Discourse sites. The way to block those dynamic URLs from bots while still allowing search engines to crawl /latest is this:

Disallow: /latest?

That will only block the dynamic ones, but not /latest, so search engines would still be able to see the latest content. I tested the rule in Google’s Webmaster Tools and it works.

Here’s an example of some of the dynamic URLs that are getting crawled on my site:

https://gist.githubusercontent.com/j127/d329c15dab45369b03321cad40448734/raw/300aa579b1386087b903da6aa52c52ff5d95828c/latest.txt

Is it possible to add that one line to robots.txt?

(Edit: I looked more closely at the file, and I wouldn’t use noindex there, at least on that dynamic rule. I’m pretty sure that Google has recommended not to use noindex in robots.txt though it was several years ago.)

[codinghorror (Jeff Atwood)]

Ahora puedes prohibir o limitar los webcrawlers abusivos mediante la configuración del sitio, lo que edita indirectamente robots.txt, pero aún no ofrecemos la capacidad de edición arbitraria.

Creo que deberíamos hacerlo… @eviltrout, ¿puedes definir el alcance de esto para la versión 2.4? Responde a muchas solicitudes, muchas de las cuales no compartimos, pero mi actitud al respecto es “es tu responsabilidad, así que adelante si sientes que debes ”.

[Stephen]

¿Podemos al menos considerar que editar el archivo robots.txt está totalmente fuera del alcance del soporte comunitario?

[vinothkannans (Vinoth Kannan)]

Por cierto, cualquiera puede agregar fácilmente reglas adicionales mediante un plugin sencillo utilizando la plantilla de conector “robots_txt_index”. Por ejemplo: app/views/connectors/robots_txt_index/sitemap.html.erb

[eviltrout (Robin Ward)]

Así es como creo que debería funcionar:

• Agregar una nueva URL a la sección de administración que no esté vinculada directamente. Por ejemplo, /admin/customize/robots.

  • Mostrar un <textarea> con el contenido actual de robots.txt.

  • Si no lo han editado antes, prellenarlo con el contenido basado en la lista blanca/negra.

  • Cuando el administrador haga clic en Guardar cambios, se guardará en la base de datos y reemplazará el contenido existente de robots.txt para ese foro.

[codinghorror (Jeff Atwood)]

@eviltrout

Añade un nuevo botón en la sección de administración, “Admin > Personalizar > robots.txt”

Me opongo firmemente a esto, ya que otorga una opción oscura y peligrosa un lugar destacado en la interfaz de usuario.

Creo que la ruta para personalizar robots.txt debe ser personalizada e ingresada manualmente por ahora. Si los usuarios la desean, deben buscar en Google o en meta y encontrar la ruta.

[eviltrout (Robin Ward)]

Por eso lo escondí detrás de “Edición avanzada”, pero si estamos ocultando la interfaz, puedo simplificarlo aún más (editaré ese mensaje).

[Osama]

He creado un PR para esto:

FEATURE: Allow customization of robots.txt (#7884)

Capturas de pantalla:

[codinghorror (Jeff Atwood)]

¡Se ve bien! Asegúrate de que el botón de revertir use el glifo correcto, el mismo que usamos para revertir en la configuración del sitio. Además, solo usamos la palabra «restablecer», así que puedes reutilizar ese texto en lugar de crear una nueva traducción.

También necesitamos algunas advertencias sobre el puñado de configuraciones del sitio que modifican robots.txt, las cuales serán sobrescritas si editas manualmente, etc.

[Osama]

La PR acaba de ser fusionada:

FEATURE: Allow customization of robots.txt (#7884)

Si actualizas a la última versión con pruebas aprobadas, podrás personalizar robots.txt en /admin/customize/robots. La página no está enlazada desde ninguna parte de la interfaz de usuario; tendrás que copiar y pegar la URL manualmente en tu navegador.

Nota: si sobrescribes el archivo, cualquier cambio posterior en la configuración del sitio que modifique robots.txt (por ejemplo, agentes de usuario de rastreadores permitidos, etc.) no se aplicará al archivo (la configuración se guardará correctamente, pero los cambios no se reflejarán en robots.txt). Puedes restaurar la versión predeterminada y la configuración del sitio se aplicará al archivo nuevamente.

Si hay sobrescrituras y un administrador visualiza el archivo en /robots.txt, verá un comentario en la parte superior que indica que existen sobrescrituras y enlaces a donde pueden modificar el archivo o restablecerlo a la versión predeterminada.