A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
MetaExtensions: Difference between revisions
(Added keywords-not. For keywords, from not necessary to not very necessary, as engines use them somewhat. Hyphenated _comma-separated_. Punctuation. Spelling of _inteded_.) |
m (Layout spaced out because keyword ran into description and seemed to reverse meaning. Named new link. Extra comma cut.) |
||
| Line 9: | Line 9: | ||
|- | |- | ||
| cache | | cache | ||
| Value must be "public", "private", or "no-cache" | | Value must be "public", "private", or "no-cache". Intended as a simple way to tell user agents whether to store a copy of the document or not. An alternate for HTTP/1.1's cache-control; for publishers without access to modifying cache-control.<br/>'''This doesn't actually work; use HTTP headers instead.''' | ||
| none | | none | ||
| | | | ||
| Line 20: | Line 20: | ||
| Unendorsed | | Unendorsed | ||
|- | |- | ||
| keywords-not | | keywords-not | ||
| A comma-separated list of negative keywords that distinguish a closely-related theme from this page's true theme, to support Boolean NOT searches often more realistically than visible text can, especially when both themes share the same lexicon. | | A comma-separated list of negative keywords that distinguish a closely-related theme from this page's true theme, to support Boolean NOT searches often more realistically than visible text can, especially when both themes share the same lexicon. | ||
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=6609] | | [http://www.w3.org/Bugs/Public/show_bug.cgi?id=6609 W3C Bug 6609] | ||
| keywords-negative; keyword-negative; negative-keywords; negative-keyword; keywords-neg; keyword-neg; neg-keywords; neg-keyword; not-keywords; not-keyword; keyword-not | | keywords-negative; keyword-negative; negative-keywords; negative-keyword; keywords-neg; keyword-neg; neg-keywords; neg-keyword; not-keywords; not-keyword; keyword-not | ||
| Proposal | | Proposal | ||
Revision as of 11:15, 22 February 2009
This page lists the allowed extension values for the name="" attribute of the <meta> element in HTML5. You may add your own values to this list, which makes them legal HTML5 metadata names. We ask that you try to avoid redundancy; if someone has already defined a name that does roughly what you want, please reuse it.
| Keyword | Brief description | Link to more details | Synonyms | Status |
|---|---|---|---|---|
| cache | Value must be "public", "private", or "no-cache". Intended as a simple way to tell user agents whether to store a copy of the document or not. An alternate for HTTP/1.1's cache-control; for publishers without access to modifying cache-control. This doesn't actually work; use HTTP headers instead. |
none | Unendorsed | |
| keywords | A comma-separated list of keywords that describe this page. Not very necessary these days; search engines use much more sophisticated means to determine the page's contents. | none | Unendorsed | |
| keywords-not | A comma-separated list of negative keywords that distinguish a closely-related theme from this page's true theme, to support Boolean NOT searches often more realistically than visible text can, especially when both themes share the same lexicon. | W3C Bug 6609 | keywords-negative; keyword-negative; negative-keywords; negative-keyword; keywords-neg; keyword-neg; neg-keywords; neg-keyword; not-keywords; not-keyword; keyword-not | Proposal |
| description | A brief phrase that describes this page. Could be used for search results or bookmarks lists. | none | Unendorsed | |
| robots | A comma-separated list of operators explaining how search engine crawlers should treat the content. Possible values are "noarchive" to prevent cached versions, "noindex" to prevent indexing, and "nofollow" works as the link rel value with the same name. This meta name is already supported by every popular search engine. | Robots exclusion protocol, Googlebot, Yahoo! Slurp, and Ask.com Teoma | Proposal |
For the "Status" section to be changed to "Accepted", the proposed keyword must either have been through the Microformats process, and been approved by the Microformats community; or must be defined by a W3C specification in the Candidate Recommendation or Recommendation state. If it fails to go through this process, it is "Unendorsed".
For more details, see the HTML5 specification.