Article tags are an important way to put visitors in touch with helpful content. Each page should normally have several tags to help keep content organized. This page explains the best way to tag pages so that our readers can find information and we can keep ourselves organized.
For a help with the user interface for editing tags, see the tagging section in our editor guide.
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.
How MDN uses tags
Tags get used on MDN several ways:
- Document categorization
- What type of document is it? Is it a reference? A tutorial? A landing page? Our visitors can use these tags to filter searches, so they're really important!
- Topic identification
- What is the article about? Is it about an API? The DOM? Graphics? Again, these tags are important because they can filter searches.
- Technology status
- What's the status of the technology? Is it non-standard? Obsolete or deprecated? Experimental?
- Skill level
- For tutorials and guides, how advanced is the material covered by the article?
- Document metadata
- The writing community uses tags to keep track of which pages need what kind of work.
Tag type guide
Here's a quick guide to the types of tags and possible values for them.
When you tag an article with one of these categories, you help the automated tools more accurately generate landing pages, tables of contents, and so on. Our new search system will also use these terms so that our visitors can locate reference or guide information at will.
We use the following category names as standard tagging terms:
- The article provides introductory material about a topic. Ideally each technology area should have only one "Intro".
- The article is critical and will display prominently on landing pages. Use this tag sparingly (never more than three documents in each documentation area).
- 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 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 are helping 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:
APIfor each interface, method and property.
Methodfor each method of an API
Propertyfor each property of an API
In general, your 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
To help the reader understand how viable a technology is, we use tags to label pages as 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.
Here are possible values for these tags:
- Apply this tag to reference pages which describe a property or attribute which is read-only.
- Indicates that the technology or API described on the page is not part of a standard, but is considered stable in any implementing browser(s). If you don't use this tag, your readers will assume the technology is standard. The compatibility table on the page should clarify which browser(s) support this technology or API.
- The technology or API covered on the page is marked as deprecated in the specification, and is likely to eventually be removed, but is generally still available in current versions of browsers.
- The technology or API has been deemed obsolete and has been removed (or actively being removed) from all or most current browsers.
- 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.
- 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 compatibility table in your article!
Use the skill-level tag type 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 tags to label articles as requiring specific types of work. Here's a list of the ones we use most:
- The article needs to be deleted.
- 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 created to help illustrate the article's point. These examples should use the live sample system.
- The article has one or more examples that need to be updated to use the live sample system.
- The content is out of date and needs to updating.
- 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.
Web Literacy Map
The WebMaker project, through the Web Literacy Map, has defined skills needed to optimally read, write, and participate on the Web. We use Web literacy skills as tags on MDN to help our users find the resources that best suit their needs:
- The article includes information about how to browse the Web.
- The content has information about how the Web is organized and how it works.
- The article explains how to find information, people, and resources on the Web.
- The information in the article helps the reader understand how to critically evaluate information they find on the Web
- The article provides information about how to keep systems, identities, and content safe.
- The document explains how to create and curate content for the Web.
- The article teaches how to modify existing Web resources to create something new.
- Documentation explaining how to enhance visual aesthetics and user experience.
- Documents which describe how to develop content to be accessible, which means enabling as many people as possible to use it, even when those people's abilities are limited in some way.
- How to write code and/or to create interactive experiences on the Web.
- The document explains how the Internet's technical stack works.
- The article's content covers ways to create resources with others.
- The document provides information about how to work with other people.
- The article details how to get involved in Web communities and to understand how they work.
- The material helps to examine the consequences of sharing data online.
- The article provid=deshow to help keep the Web accessible to everybody
Putting it all together
So to each page you assign tags from several tag types, for example
- A tutorial about WebGL for beginners
- Reference page for
- A landing page for Firefox OS developer tools
Tagging and search filters
Search filters won't work properly unless we tag MDN pages properly. Here's a table of search filters and which tags they look for.
Note: If multiple tags are listed under "Tag name," that means any one or more of these tags must be present for the article to match.
|Filter group||Search filter name||Tag name|
|Topic||Open Web Apps||Apps|
|APIs and DOM||API|
|Firefox for Android||Firefox Mobile|
|Firefox for Desktop||Firefox Desktop|
|Firefox OS||Firefox OS|
|Web Development||Web Development|
|Add-ons & Extensions||Add-ons || Extensions || Plugins || Themes|
|Skill level||I'm an Expert||Advanced|
|Document type||Docs||This restricts the search to docs content, leaving out Hacks and other MDN content.|
|Demos||This includes Demo Studio content in the search results.|
|How-To & Tutorial||Guide|
|Developer Profiles||This includes developer profiles from the MDN site in the search results.|
|External Resources||The dev team is still figuring this out...|
Tagging problems you can fix
There are several kinds of tag problems you can help fix:
- No tags
- Generally articles should have at least a "category" tag and a "topic" tag. Usually other tags are appropriate as well, but if you can help us ensure that the minimum tags are present, you'll be a documentation hero!
- Tags that don't follow our tagging standards
- Please fix any documents whose tags don't follow the standards on this page.
Note that due to a bug in Kuma, some localized tags (such as
Référence) may show up on some English pages. These tags are likely to reappear even if you delete them; don't bother trying to fix them until the Kuma bug is fixed.
- Incorrect tags
- Missing tags
- Tag spam
- 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.
If you see one (or more) of these problems, please log into MDN and click EDIT at the top right of the MDN window. Once the editor loads up, scroll down to the bottom of the page, where you'll see the tag box. For more details on the tagging interface, see "The tags box" in the MDN editor guide.