Necessità di modificare il file robots.txt: dove si trova?

[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)]

Ora puoi bannare o limitare i webcrawler abusivi tramite le impostazioni del sito, il che modifica indirettamente robots.txt, ma non forniamo ancora la possibilità di un’editing arbitrario.

Credo che dovremmo farlo comunque.. @eviltrout puoi definire lo scope per la versione 2.4? Questo risponde a molte richieste, molte delle quali non condividiamo, ma il mio atteggiamento al riguardo è “è il tuo funerale, quindi vai pure avanti se senti di doverlo fare ”

[Stephen]

Possiamo almeno considerare la modifica del file robots.txt completamente al di fuori dell’ambito del supporto della comunità?

[vinothkannans (Vinoth Kannan)]

FTR, chiunque può facilmente aggiungere regole aggiuntive tramite un semplice plugin utilizzando il template del connettore “robots_txt_index”. Ad esempio: app/views/connectors/robots_txt_index/sitemap.html.erb

[eviltrout (Robin Ward)]

Ecco come penso che dovrebbe funzionare:

• Aggiungi un nuovo URL alla sezione di amministrazione che non sia collegato direttamente. Ad esempio /admin/customize/robots

  • Mostra un <textarea> con il contenuto attuale di robots.txt.

  • Se non è stato modificato in precedenza, pre-compilalo con i contenuti basati sulla whitelist/blacklist.

  • Quando l’amministratore clicca su Salva le modifiche, il contenuto deve essere salvato nel database e sostituirà i contenuti esistenti di robots.txt per quel forum.

[codinghorror (Jeff Atwood)]

@eviltrout

Aggiungi un nuovo pulsante nella sezione amministrazione, “Admin > Personalizza > robots.txt”

Sono fortemente contrario a questa idea, perché attribuisce un’opzione oscura e pericolosa a un’alta priorità nell’interfaccia utente.

Credo che il percorso per personalizzare robots.txt debba essere personalizzato e inserito manualmente per ora. Se gli utenti lo desiderano, devono cercare su Google o sui forum e trovare il percorso.

[eviltrout (Robin Ward)]

Ecco perché l’ho nascosto dietro “Modifica avanzata”, ma se stiamo rendendo l’interfaccia troppo complessa posso semplificarla ulteriormente (modificherò quel post).

[Osama]

Ho creato una PR per questo:

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

Screenshot:

[codinghorror (Jeff Atwood)]

Sembra tutto a posto! Assicurati che il pulsante di ripristino utilizzi il glifo corretto, lo stesso che usiamo per il ripristino nelle impostazioni del sito. Inoltre, usiamo semplicemente la parola “reset”, quindi puoi riutilizzare quel testo invece di crearne una nuova traduzione.

Inoltre, dobbiamo aggiungere alcuni avvisi per le poche impostazioni del sito che modificano robots.txt, le quali verrebbero sovrascritte se le modifichi manualmente, ecc.

[Osama]

La PR è stata appena unita:

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

Se aggiorni all’ultima versione con i test passati, potrai personalizzare robots.txt in /admin/customize/robots. La pagina non è collegata da nessuna parte nell’interfaccia utente: dovrai copiare e incollare manualmente l’URL nel tuo browser.

Nota: se sovrascrivi il file, eventuali modifiche successive alle impostazioni del sito che modificano robots.txt (ad esempio whitelisted crawler user agents, ecc.) non verranno applicate al file (le impostazioni verranno salvate correttamente, ma le modifiche non si rifletteranno su robots.txt). Puoi ripristinare la versione predefinita e le impostazioni del sito verranno nuovamente applicate al file.

Se sono presenti sovrascritture e un amministratore visualizza il file in /robots.txt, vedrà un commento in alto che indica la presenza di sovrascritture e fornisce collegamenti per modificare il file o ripristinare la versione predefinita.