-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Misleading warning regarding X-Robots-Tags #37355
Comments
cc @MichaIng |
According to #36689 you changed from "none" to "noindex, nofollow" on purpose due to unknown support status beside Google. Tough question if you still want to accept "none" in that case... |
Only for Google, not for all search engines. Please read the info and links given in the PR. I can in fact verify this with Bing. I was always wondering why some pages on our website were kept in the Bing index, and after changing the header, they started to be taken out of the index.
I think it is irresponsible to leave private Nextcloud instances knowingly exposed to search engines. It is a single header change, and it does not break Nextcloud if you do not change it, it is just a totally correct warning that your privacy is currently not assured. |
Well, in #36689 (comment) you posted the idea of showing a different message which would be a good idea... |
It was a suggestion which no one responded to. If more people keep asking about it, I may reconsider, but you do know about it now, so no need to add it for you 😉. But I added it to #34692. |
Bug description
After upgrading to Nextcloud v26.0.0, I am getting the "Security & setup warning"
However, I configured my instance already to send
which is the same like sending "noindex, nofollow", see https://developers.google.com/search/docs/advanced/robots/robots_meta_tag?hl=de#none
Steps to reproduce
/settings/admin/overview
for warningsExpected behavior
No warning at all.
Installation method
Community Manual installation with Archive
Operating system
Other
PHP engine version
PHP 8.1
Web server
Nginx
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 22.2.3 to 23.0.1)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: