-
Notifications
You must be signed in to change notification settings - Fork 22.5k
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
feat(http): Add X-Robots-Tag header #37079
Conversation
Preview URLs
External URLs (3)URL:
URL:
(comment last updated: 2024-12-11 12:58:12) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know very little about HTTP headers and knew very little about robot directives, so I had many questions. I realize this is a reference and not a guide, so you may want to disregard some of my questions in favor of a guide.
it was really good, and I learned a lot. In addition to the above clarifications, just a few suggestions to make it less wordy for ease of reading.
|
||
## See also | ||
|
||
- {{HTTPHeader("Forwarded")}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we have a guide on setting HTTP headers that we can link to?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not yet, but that's a good idea. We could have a how-to page for this in the HTTP section, it might be good to talk about cases where you have a website but can't control headers (GitHub pages?)
Co-authored-by: Estelle Weyl <[email protected]>
Co-authored-by: Estelle Weyl <[email protected]>
Co-authored-by: Estelle Weyl <[email protected]>
Co-authored-by: Estelle Weyl <[email protected]>
Co-authored-by: Estelle Weyl <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I got a notification so re-reviewed. I just realized you didn't ask for another review yet, but already reviewed. as some of it may be helpful, sharing.
Super, thank you. I haven't incorporated all of the suggestions yet, so I can re-request when I think everything's in a good state 👍🏻 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking really, really good. Just think we may need a note on the all on one line example to indicate that the directives for all user agents goes first, and then exceptions for individual bots goes after if doing on one line (if that is accurate).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Thanks :)
Adding just one nitpick to the review. I’d suggest calling <meta>
an element, not a tag. Unlike other sources do 🥲 It’s called an element in the spec, and we do it mostly consistently throughout the MDN.
Here’s how I usually explain the difference. The <p>
element consists of opening <p>
and closing </p>
tags. Element is a language entity with its semantics, attributes, etc. Tag is a syntactic construction that makes all elements work.
Co-authored-by: Estelle Weyl <[email protected]>
Co-authored-by: Vadim Makeev <[email protected]>
Co-authored-by: Vadim Makeev <[email protected]>
Thanks, both. I think this is ready to merge in case you want to have another quick look |
Description
This PR adds the
X-Robots-Tag
header page.Omitting historical rules no longer used by Google, at least
noarchive
nocache
nositelinkssearchbox
See https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag#directives
Motivation
We're missing docs about it, and it's a widely used header for controlling indexing & search presentation.
Related issues and pull requests