-
-
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
Support for multiple X-Robots-Tags #32102
Support for multiple X-Robots-Tags #32102
Comments
Well this issue might have been created prematurely, after looking closer these pages also appear on the Google search results. But without any information ... just like on Bing. So apparently pages with a lot of access still appear in the search results. |
I guess it's fine to change https://developers.google.com/search/docs/advanced/robots/robots_meta_tag Feel free to submit a pr. |
Wow, this explains a lot, never know that Bing does not support Btw, Nextcloud also sets the HTML meta tag <meta name="robots" content="noindex, nofollow"/> So actually one should be safe also for Bing. I'll open a report. |
PR up: #36689 It does not exactly address the request here to support multiple values, i.e. for not unsetting but appending the values via |
How to use GitHub
Is your feature request related to a problem? Please describe.
The Nextcloud Overview page issues a warning when the X-Robots-Tag is not set exclusively to 'none'.
The problem is 'none' is not supported by Bing. This causes multiple Nextcloud instances to be indexed by Bing, even though this is probably not intended.
One example would be https://cloud.dresden.de/. The page is easily found by searching in Bing and it does have the X-Robots-Tag set to 'none'.
Describe the solution you'd like
One solution would be to keep the requirement for the 'none' tag but allow more tags. This way X-Robots-Tag could be set to 'none,noindex,nofollow'. This way the instance should not be indexed by Bing as well as other search engines.
Describe alternatives you've considered
The alternative currently is to ignore the warning, which is kind of annoying.
(A way to disable warnings would also be appreciated.)
The text was updated successfully, but these errors were encountered: