How to tag pages
Article tags are an important way to put readers in touch with helpful content. Each page should normally have several tags to help keep content organized. This article explains the best way to tag pages so that our readers can find information and we can keep the content organized.
Please use tags properly as explained below. If you don't, our automated tools will not correctly generate lists of content, landing pages, and cross-linking of articles.
Warning: Note to translators and localizers: You should not translate any tags listed on this page. They are used for specific purposes such as certain site management tasks and automated data processing, and translating them would break these processes.
Tags used on MDN Web Docs can be classified into the following categories based on what the tags are used for or the information they convey:
- Document type: Tags in this category convey the type of document it is –– a reference, a tutorial or a landing page. Our readers can use these tags to filter searches, so they're really important!
- Topic identification: Tags in this category convey what the article is about. Is it about an API, the DOM, or graphics? Again, these tags are important because they can filter searches.
- API identification: Reference pages about an API need to identify the specific component of the API being documented (that is, what interface it's a part of and what property or method the page covers, if applicable). Tags in this category help with this information.
- Technology status: Tags in this category convey the status of the technology –– non-standard, deprecated or experimental.
- Skill level: Tags in this category are used for tutorials and guides and to indicate the level of information covered by the article.
- Document metadata: The writing community uses tags to keep track of which pages need what kind of work.
The sections below explain these different categories in more detail and the tags that fall in each category.
When you add one of these tags to an article, you help the automated tools to more accurately generate landing pages, tables of contents, and so on. Our new search system also uses these tags to help our readers locate reference or guide information easily.
We use the following tags to denote the appropriate document type:
The article provides introductory material about a topic. Ideally, each technology area should have only one "Intro".
The article contains reference material about an API, element, attribute, property, or the like.
The page is a landing page.
The article is a how-to or a guide page.
The article is a code sample page or has code samples (that is, actual snippets of useful code, not one-line "syntax examples").
By identifying the article's topic area, you help generate better search results (and landing pages and navigation as well).
While there's some room for flexibility here as we identify new topic areas, we try to limit ourselves to the names of APIs or technologies. Some useful examples include:
APIfor each API's overview, interface, method, and property
Methodfor each method of an API
Propertyfor each property of an API
WebExtensionsfor WebExtension documentation
In general, the topic identification tag should be the name of an interface with a number of related pages (like Node, which has many pages for its various properties and methods) or the name of an overall technology type. You might tag a page about WebGL with
WebGL, for example, but a page about
These tags are used in Mozilla-specific content only:
Within the API reference, the following tags help to identify the part of API an article covers:
The main article for an interface should have this tag. For example,
Each interface may have up to one page tagged "Constructor"; this is the interface's constructor. The page should have the same name as the interface, like
Every article describing a particular property within an interface needs this tag. See
Each article documenting an interface method needs this tag. See
In addition, reference pages need to include interface, property, and method names among their tags. This is illustrated in the following examples:
- The interface
RTCPeerConnection: Include the tag
RTCPeerConnectionalong with other relevant tags like
- The method
RTCPeerConnection.createOffer(): Include the tags
createOffer(note no parentheses in tag names!) along with the other relevant tags, including
Reference. Consider including tags like
SDP, which are also relevant here.
- The property
RTCPeerConnection.iceConnectionState: Include the tags
iceConnectionStatealong with the other relevant tags, including
Reference. Also consider including
To help readers understand how viable a technology is, use these tags to label articles with respect to the status of the technology's specification. This isn't as detailed as actually explaining what the spec is and how far the technology has come in the specification process (that's what the Specifications table is for), but it helps the reader judge, at a glance, whether it's a good idea to use the technology described in the article.
Tags in this category include:
The property or attribute is read-only.
The technology or API is not part of a standard, whether it's stable or not in any browsers which implement it (if it's not stable, it should also be Experimental). If you don't use this tag, your readers will assume the technology is standard. The browser compatibility table on the page should clarify which browser(s) support this technology or API.
The technology or API covered on the page is no longer recommended. It might be removed in the future or might only be kept for compatibility purposes. Avoid using this functionality.
The technology is not standardized and is an experimental technology or API that may or may not ever become part of a standard. It is also subject to change in the browser engine (typically only one) that implements it. If the technology isn't part of any specification (even in draft form), it should also have the Non-standard tag.
The API requires privileged access to the device on which the code is running.
The API only works in certified code.
These tags are no excuse to leave out the browser compatibility table in your article! That should always be present.
Use these tags only for guides and tutorials (that is, pages tagged
Guide) to help users choose tutorials based on how familiar they are with a technology. There are three values for this:
Articles designed to introduce the reader to a technology they've never used or have only a passing familiarity with.
Articles for users who have gotten started with the technology but aren't experts.
Articles about stretching the capabilities of a technology and of the reader.
The writing community uses these tags to label articles as requiring specific types of work. Here's a list of the ones we use most:
The article is not complete and is still actively being updated (although it's also possible it's been forgotten about). Try to check with the most recent contributors before making changes to avoid potential content collisions.
The article needs a table to specify compatibility of a feature across browsers. See here for a guide on contributing to browser compatibility.
The article is a stub or is otherwise lacking information. This tag means that someone should review the content and add more details and/or finish writing the article.
The article needs one or more examples to help illustrate the article's point. These examples should use one of the code example styles.
The article has one or more examples that need to be updated to use the live sample system.
The article needs improvement to the page markup (usually because the page content consists mostly or entirely of
The article needs a table to indicate on which specification document(s) the feature was defined.
The content is out of date and needs to be updated.
The content is not really worth localizing and will not appear on localization status pages.
The content is important and should be marked as a priority for MDN translators. Shows up in an extra priority table on localization status pages.
To put it all together, to each page you assign tags from the different categories explained above. Some examples are shown below:
- A tutorial about WebGL for beginners will have the following tags:
- A reference page for
<canvas>will have the following tags:
There are several kinds of tag problems you can help fix.
Please fix any documents that have tags that don't follow the standards described on this page.
Note that you may occasionally see some localized tags (such as
Référence) showing up on some English pages. This was due to a bug in Kuma, which caused the tags to reappear even if they were deleted. That bug has since been fixed, so any remaining localized tags can be cleaned up if they're spotted.
If you're looking at an article about HTML and it's tagged
Web tag, that's probably wrong too. Remove these tags and add the right tags if they aren't already there. Please also correct misspelled tags (e.g.,
Reference or another type as well!
This insidious beast is the most revolting tag problem of all: some web vermin has deposited its droppings in the page tags (like "Free warez!" or "Hey I was browsing your site and wanted to ask you if you could help me solve this problem I'm having with Flash crashing all the time"). We've got to delete these right away! They're ugly, they're hard to manage if they're allowed to linger too long, and they're terrible for SEO.