I was checking the Google Search Console coverage report and found that lots of our forum pages are blocked by robots.txt. So I went ahead and checked the robots.txt. Then I found that semrushbot and ahrefsbot are blocked by default: [image] I know these are two widely used SEO tools, why blocking…

[imagen] Jamie_Liu1: I know these are two widely used SEO tools, why blocking their bots? Because they suck? They add a lot of server load for no discernable benefit, and our customers do have pageview limits on their plans.

[imagen] Jamie_Liu1: I know these are two widely used SEO tools, why blocking their bots? Because those bots are “resource sucking bot hogs” which provide very little value to sites compared to the amount of resources these bots consume. Of course, you can customize the Discourse robots.txt …

Thanks so much for the information! I found another issue and maybe you can share your insight on it as well. :slight_smile: I know Discourse has blocked user pages by default, but in my Google Search Console coverage report, there are still some user pages indexed, which is an issue in Google’s e…

This was fixed recently with FIX: add noindex header to user profile pages. committed 05:56AM - 08 Jan 20 UTC (UTC) [imagen] vinothkannans +4 …

@osioke Thanks for your reply! I believe our installed version already has the feature? Because I noticed that the fix was committed in Jan. [image] Could you please verify if I need to upgrade to the latest version to have this feature?

It doesn’t hurt to update IMO, but yes, that fix should be in your installed version. I would try updating and reverifying unless you don’t want to update for some other reason.

Sounds good. We are updating now. Hope things will work out after the update. I’ll get back and keep you informed. :slight_smile: Thanks!

Just to clarify, is there no way to unblock semrushbot and seo spider? We need them for SEO audit. Tried removing both from /admin/customize/robots (also tried Allow: ) but we get 429 error in Screaming Frog. Or is this 429 error a separate issue? Your insights are highly appreciated.

429 errors mean that those crawlers are getting rate-limited. Discourse has some throttling enabled by default to prevent abuse. You can read more about this here. [imagen] Available settings for global rate limits and throttling Self-Hosting Discourse ships w…

[imagen] trying2survive: Just to clarify, is there no way to unblock semrushbot and seo spider? Did you try this (but use your container name)? Note: you can also configure this in the Admin UI: # docker exec -it socket-only bash root@socket-only:/# rails c [1] pry(main)> SiteSetting.blocke…

¿Por qué semrushbot y ahrefsbot están bloqueados de forma predeterminada?

Soporte

Johani (Joe) 2 Diciembre, 2020 16:34 11

Los errores 429 indican que esos rastreadores están siendo limitados por tasa. Discourse tiene cierta limitación de velocidad activada de forma predeterminada para prevenir abusos. Puedes leer más sobre esto aquí.

Tema		Respuestas	Vistas
Handling Bingbot Feature	29	7484	20 Noviembre 2020
MegaIndex bot did about 4,000 pageviews on one day Community Building	40	4626	2 Diciembre 2023
Issues Google Search Console is throwing at me for wrong discourse structure (or some for wrong administration of my site) Support	18	233	18 Diciembre 2024
Why there are lots of Disallow rule in robots.txt? Support	34	4622	22 Diciembre 2020
How to protect myself from bots crawling my Discourse instance? Support	6	1632	17 Enero 2022

¿Por qué semrushbot y ahrefsbot están bloqueados de forma predeterminada?

Temas relacionados