Wikipedia:Categorization

The primary purpose of the categorization system on Wikipedia is to provide navigational links within a structured, tree-like hierarchy of categories. By grouping pages according to their essential, defining characteristics, the system allows readers to browse and efficiently locate related topics.

Proposals to delete, merge, or rename categories should follow the process outlined at Wikipedia:Categories for discussion. Please use that forum before undertaking extensive re-categorization of existing categories or the mass creation of new ones.

Categorizing pages

A screencast showing how to categorize pages and explaining the usage of the tool HotCat

Every Wikipedia page should belong to at least one category, except for talk pages, redirects, and user pages, which may optionally be placed in categories where appropriate.

Each categorized page should be placed only in the most specific categories to which it logically belongs, and subcategories should be categorized under only the most specific parent categories possible.

exclamation mark  Important: All categories form part of a tree-like hierarchy. Do not add categories to pages as if they are tags.

Creating category pages

Sometimes proper categorization requires the creation of a new category.

Before creating a new category

Categories are not the only means of allowing users to browse sets of related pages, and have several disadvantages, including:

So, consider whether a list would be more appropriate than a category (or in addition to a category) for a grouping of pages. As examples, a list of Nobel laureates could include dates, and a list formatted as a table can provide options for sorting the entries.

Also consider whether the proposed category might be considered "category clutter", as described in Wikipedia:Overcategorization.

Choosing a name for the category

A good category name is accurate and neutral, and, as much as possible, defines the category's inclusion criteria in the name itself.

exclamation mark  Important: Moving non-conventionally categorized pages to another category name (see {{Category redirect}}) imposes an additional overhead – an edit for every categorized page and subcategory. So, when choosing a name for the category, please be sure a category with a similar name or similar inclusion criteria does not already exist. (See also: WP:OVERLAPCAT.)

One way to determine if suitable categories already exist for a particular page is to check the categories on pages concerning similar or related topics. You can also search existing category names as described at Help:Searching (top of page).

For example: You might want to add a subcategory for people to Category:Mexicans. By starting at Category:People by nationality, you will discover that Mexicans are placed in Category:Mexican people.

Information Note: Eponymous categories (categories whose name and topic is the same as an article, such as a category named after a person) should only be created if enough directly related articles exist.

Creating the category

After you have determined an appropriate name for the category, find a suitable place for the new category. (For example, categories of people should be in the tree of "people" categories.) See § Category tree organization for more information on this.

Once you have determined where to categorize this new category, you should be ready to create the new category.

To create a category:

  1. Add a page to the intended category. Do this by editing that page, and add the name of the new category: (e.g. [[Category:New category name]])
    • Per MOS:ORDER, categories are placed at the end of the wikitext, but before any stub templates, which transclude their own categories.
    • Eponymous categories should appear first. Beyond that, the order in which categories are placed on a page is not governed by any single rule (for example, it does not need to be alphabetical, although partially alphabetical ordering can sometimes be helpful). Normally the most essential, significant categories appear first.
  2. Save your edit. The as-yet-undefined category name will now appear as a red link in the category list at the bottom of the page.
    • A page should never be left with a non-existent (red-linked) category on it. Either the category should be created, or else the link should be removed or changed to a category that does exist.
  3. Next, click on that red link, which brings you to the new category page to create.
  4. Finally, at the bottom of the category page, simply add a parent category (e.g. [[Category:Parent category name]]), which should usually be a hypernym of the subcategory. This will add the new category into the appropriate parent category. (A category can have more than one parent category.)

exclamation mark  Important: If something goes wrong, double check to see if you followed the steps properly and check if the wikitext is correct. For example, if the category fails to list in the parent category, the wikitext should be [[Category:Parent category name]], not [[:Category:Parent category name]].

Category description

While it should typically be clear from the name of an existing category which pages it should contain, sometimes, a common-sense guess based on the name of the category is not enough to figure out whether a page should be listed in the category. So, rather than leave the text of a category page empty (other than parent categories), adding a hatnote linking to the main article or another page which describes the topic (see § Articles with eponymous categories) can help with that.

However, only linking to a Wikipedia article explaining the title is often not sufficient as a description for a category. It can be helpful – to both readers and editors – to include a clear description of the category, indicating what pages it should contain, how they should be subcategorized, and so on, and linking to one or more pages as background information.

In such cases, the desired contents of the category should be described on the category page, similar to how the list selection criteria are described in a stand-alone list. The category description should make direct statements about the criteria by which pages should be selected for inclusion in (or exclusion from) the category. This description, not the category's name, defines the proper content of the category. Do not leave future editors to guess about what or who should be included from the title of the category. Even if the selection criteria might seem obvious to you, an explicit standard is helpful to others, especially if they are less familiar with the subject.

The description can also contain links to other Wikipedia pages, in particular to other related categories that do not appear directly as subcategories or parent categories, and to relevant categories at sister projects, such as Commons.

Like disambiguation pages, category pages should contain neither citations nor external links.

Various templates have been developed to make it easier to produce category descriptions; see Category namespace templates and Wikipedia:Category classification templates. There are hatnote templates including {{Category main article}} and {{Category see also}}; others are listed at Wikipedia:Hatnote#Categories.

Additional considerations

Categories may have hundreds or thousands of members, displayed over many pages, with up to 200 entries on a single page. To make navigating large categories easier, a table of contents can be used on the category page. The following templates are some of the ways of doing this:

Likewise, a maximum of 200 subcategories are displayed at a time, so some subcategories may not be immediately visible. To display all subcategories at once, add a category tree to the text of the category page, as described at Help:Category § Displaying category trees and page counts.

Category pages can have interlanguage links to corresponding categories in other language Wikipedias. Edit these on Wikidata by following the instructions at Help:Interlanguage links.

Categorizing articles

In general, categories of articles must be:

Naming conventions

Topic and set categories

  • Topic categories are named after a topic (usually corresponding to the name of a Wikipedia article), and should be singular.
    For example, Category:France contains articles relating to the topic France. Other examples: Category:Law, Category:Hillary Clinton.
  • Set categories are named after a class, and should be plural. A category may be explicitly labeled as such using the {{Set category}} template.
    For example, Category:Cities in France contains articles whose subjects are cities in France. Other examples: Category:Writers, Category:Villages in Poland.
  • Note that in some instances a topic category and a set category may have similar names – the topic category name is singular and the set category name is plural. Be careful to choose the right one when categorizing articles.
    For example, Category:Opera is a topic category (containing all articles relating to the topic), while Category:Operas is a set category (containing articles about specific operas).
  • Sometimes, for convenience, the two types can be combined to create a set-and-topic category.
    For example, Category:Voivodeships of Poland contains articles about particular voivodeships as well as articles relating to voivodeships in general.

Categorizing articles about people

Categorizing articles about works

Categorizing list pages

If there are more than a few lists in a particular subject area, it may be appropriate to create a specific subcategory that contains only the list pages and no other types.

When placing list pages in a lists category, use a sort key to adjust the page title to exclude the starting words "List of", otherwise all lists would appear under "L".

Eponymous categories

A category that covers exactly the same topic as an article is known as the eponymous category for that article (e.g. New York City and Category:New York City; Abraham Lincoln and Category:Abraham Lincoln; Georgia in the Roman era and Category:Georgia (country) in the Roman era).

An eponymous category is generally named the same as its main article, but exceptions sometimes apply. See § Naming conventions for more information.

Eponymous categories should not be created unless enough directly related articles or subcategories exist. However, this should not be done simply to reduce the number of categories displayed in an article.

An eponymous category should have only the categories of its article that are relevant to the category's content. For example:

Articles with eponymous categories

  • The article itself should be a member of the eponymous category. It should be sorted with a space, so that it appears at the start of the category listing (see § Sort keys below).
  • The article should be linked on the category page as the main article of the category using the {{Category main article}} template.
  • Articles with an eponymous category may be categorized in the broader categories that would be present if there were no eponymous category (e.g. the article France appears in both Category:France and Category:Countries in Europe, even though the latter category is the parent of the former category). Editors should decide by consensus which solution makes most sense for a category tree. There are three options:
    1. Keep both the eponymous category and the main article in the parent category. This is used in Category:Countries in Europe to allow that region's country articles to be navigated together.
    2. Keep just the article in the parent category. This is used in Category:British Islands, to prevent a loop.
    3. Keep just the eponymous category in the parent category. This is used for Category:Farmers in Category:People by occupation. Such "X by Y" categories sometimes cover a limited navigational set, not a topic (see § Category tree organization below), thus there is no logical article content.

If eponymous categories are categorized separately from their articles, it will be helpful to make links between the category page containing the articles and the category page containing the eponymous categories. The template {{Category see also}} can be used for this. An example of this set-up is the linked categories Category:American politicians and Category:Wikipedia categories named after American politicians.

Categorizing draft pages

Drafts, no matter whether in the draft namespace or your userspace, are not articles and thus do not belong in content categories such as Category:Living people or Category:Biologists. If you copy an article from mainspace to draftspace or userspace and it already contains categories, disable those categories. This can be done in any of the following four ways (but only the first two ways are recommended, as a disadvantage of the last two ways is that the categories will not be linked on the page):

The same system may be used in a new draft to list the categories it may have when moved to mainspace. After you move the draft into article space, remove the leading colons, uncomment out the categories or remove the <nowiki>...</nowiki> tags to re-enable the categories. If you use the draft categories template, the categories will automatically work as normal in mainspace, but the template should be removed.

Two scripts are available to help with these tasks: User:DannyS712/Draft no cat and User:DannyS712/Draft re cat.

Categorizing project pages

Wikipedia administrative categories

A distinction is made between two types of categories:

Administrative categories include stub categories (generally produced by stub templates), maintenance categories (often produced by cleanup templates such as {{Cleanup}} and {{Citation needed}}, or those used for maintenance projects), and categories of pages in non-article namespaces, such as WikiProject assessment categories and categories holding Wikipedia policies and guidelines.

Article pages should be kept out of administrative categories if possible. For example, the templates that generate WikiProject and assessment categories should be placed on talk pages, not on the articles themselves. If it is unavoidable that an administrative category appears on article pages (usually because it is generated by a maintenance template that is placed on articles), then in most cases the category should be made a hidden category, as described in § Hiding categories below.

Maintenance categories should never be added to articles directly. Instead, the categories should be added using templates.

There are separate administrative categories for different kinds of non-article pages, such as project page categories, template categories, disambiguation page categories, etc.

In some administrative categories, pages may be included regardless of type or namespace. For example, in an error-tracking category, it makes sense to group templates separately, because addressing the errors there may require different skills compared to fixing an ordinary article. For sorting each namespace separately, see § Sort keys below.

Files

Category tags should be added to file pages of files that have been uploaded to Wikipedia. When categorized, files are not included in the count of articles in the category, but are displayed in a separate section with a thumbnail and the name for each. A category can mix articles and images, or a separate file/image category can be created. A file category is typically a subcategory of the general category about the same subject, and a subcategory of the wider category for files, Category:Wikipedia files. To categorize a new file when uploading, simply add the category tag to the upload summary.

Freely licensed files should be uploaded to, and categorized on, Wikimedia Commons, instead of uploading and categorizing on Wikipedia. Existing freely licensed files should usually be moved from Wikipedia to Commons, with a mirror page automatically remaining on Wikipedia. (For an example of one such mirror page, see here.) Categories should not be added to these Wikipedia mirror pages, because doing so creates a new Wikipedia page that is subject to speedy deletion. Exceptions to this principle are made for mirror pages of images that are nominated as featured pictures and for those that appear on the Wikipedia Main Page in the Did You Know? column.

Images that are used in Wikipedia that are non-free or fair use should not appear as thumbnail images in categories. To prevent the thumbnail preview of images from appearing in a category, __NOGALLERY__ should be added to the text of the category. In such cases, the file will still appear in the category, but the image preview will not.

Templates

Templates are not articles and thus do not belong in content categories. They should, however, be placed in template categories – subcategories of Category:Wikipedia templates – to assist when looking for templates of a certain type. For example, Template:The Beatles albums is categorized under Category:England rock music group navigational boxes, which is ultimately a subcategory of Category:Music navigational boxes (type), but Template:The Beatles albums should not be categorized under Category:The Beatles or Category:Albums (content).

Pages using a template should rarely be placed in the same categories as the template itself. To ensure a template's categories are not applied to a page using the template, template categories should be placed on the template's documentation page, normally after the two pipes in a <includeonly>{{Sandbox other||...}}</includeonly> block. Because template documentation is rarely protected, template categorization can be modified by all editors even when the template code itself is protected from editing by most editors. When there is no documentation page, the categories for the template may be placed at the bottom of the template itself, within a <noinclude>...</noinclude> block. There should be no spaces or new lines between the last part of the template proper and the opening <noinclude> tag.

User pages

User pages are not articles and thus do not belong in content categories such as Category:Living people or Category:Biologists. Similarly, draft versions of articles should be kept out of content categories. Also, do not transclude full articles into your user pages, as this will result in the user page being included in all the article's categories.

You also may not leave userspace pages sitting in red-linked categories that do not exist. Although it may seem less serious than mixing userspace content with mainspace content in conventional categories, red-linked categories in userspace get picked up by the category cleanup reports just the same as red-linked categories in mainspace, and thus actively disrupt the process of cleaning up mainspace category errors. The sole exception is that you are allowed to file your user page in Category:Wikipedians with red-linked categories on their user page, a harmless joke category that consensus has deemed a standalone exception to the rule – however, you must use that exact category itself, and are not free to use differently worded or differently spelled variants of it, and your page cannot be left in any other red-linked categories besides that.

However, user pages can optionally be placed in user categories – subcategories of Category:Wikipedians, such as Category:Wikipedian biologists – which assist collaboration between users. Also, certain user sub-pages that are non-article drafts are permitted in project categories, such as Category:User essays.

Note also that Wikipedia policy around ownership of content means that other editors are allowed to edit pages in your personal userspace. If your page is in categories that it cannot be in under USERNOCAT, other editors are free to remove it from those categories and do not need to ask you for permission to edit "your" content.

A list of article-space categories with user pages is maintained at Wikipedia:Database reports/Polluted categories.

Categorization using templates

Many templates include category declarations in their transcludable text, for the purpose of placing the pages containing those templates into specific categories. This technique is very commonly used for populating certain kinds of administrative categories, including stub categories and maintenance categories. See Template:Infobox roller coaster for an example that only adds a category by manufacturer if it exists, and otherwise uses a hidden category.

However, it is recommended that articles not be placed in ordinary content categories using templates in this way. There are many reasons for this: editors cannot see the category in the wikitext; removing or restructuring the category is made more difficult (partly because automated processes will not work); inappropriate articles and non-article pages may get added to the category; sort keys may be unavailable to be customized per category; and ordering of categories on the page is less controllable.

When templates are used to populate administrative categories, ensure that the code cannot generate nonsensical or non-existent categories, particularly when the category name depends on a parameter.

See Wikipedia:Category suppression for ways of keeping inappropriate pages out of template-generated categories.

Category declarations in templates often use {{PAGENAME}} as the sort key, because this overrides any DEFAULTSORT defined on the page.

Redirecting categories

Do not create inter-category redirects by adding #REDIRECT [[Target page]] to a category page. Unlike when renaming articles, categories cannot be redirected using "hard" redirects. Articles added to a redirected category will not show up in the target category. And since redirected categories do not become "red links", editors will not be aware when they add an article to a redirected category.

Instead, a form of "soft redirect" may be used in limited circumstances. You can create a category redirect by adding {{Category redirect|target}} to the category page. Bots patrol these categories and move articles to the "target" of the redirect.

If you need to add a redirect category to a {{Category redirect}}, use the template's second parameter. For example: {{Category redirect | Years of the 19th century in Ceylon | {{R from category navigation}} {{R from template-generated category}} }}

Category redirects are costly. While placing a page in a category redirect is not a big problem, it is a problem. There are plenty of helpful uses of category redirects, but category redirects are not as cheap as regular redirects. Links to article redirects are not broken: i.e. click on the link and you are automatically redirected to its target. However, links to category redirects are broken and need to be fixed, except when resolved by a template (i.e. the template generates categories using a pattern, and some of the resulting category names are intentionally resolved by the use of {{Resolve category redirect}} within the template, as in the Ceylon example above). Placing a page into a category redirect makes it show up in the category redirect – not its target – until a bot comes along and fixes the link.

If a category is renamed because it is ambiguous, and categories exist for two or more meanings, then create a category disambiguation page at the old name, using {{Category disambiguation}}. See also Category:Disambiguation categories.

Hiding categories

In cases where, for technical reasons, administrative categories appear directly on articles rather than talk pages, they should be made into hidden categories, so that they are not displayed to readers. This rule does not apply to stub categories – these are not hidden.

To hide a category, add the template {{Maintenance category|hidden=yes}} to the category page (the template uses the magic word __HIDDENCAT__). This also places the page in Category:Hidden categories.

A logged-in user may elect to view all hidden categories, by checking "Show hidden categories" in the "Appearance" tab of their Preferences. "Hidden" parent categories are never in fact hidden on category pages (although they are listed separately).

Hidden categories are listed at the bottom when previewing. All users of the desktop version can see hidden categories for a page by clicking "Page information" on the right-hand side, or by editing the whole page with the source editor.

For more information, see mw:Help:Categories § Hidden categories.

Categorizing stub articles

Stub templates categorize stub articles for maintenance purposes into administrative categories, not for user browsing, so they do not count as categorization for the purposes of Wikipedia's categorization policies. An article which has a "stubs" category on it must still be filed in the most appropriate content categories, even if one of them is a direct parent of the stubs category in question.

Category tree organization

Partial view of Wikipedia's category system from 2007. Arrows point from category to subcategory.

Categories are organized as overlapping "trees", formed by creating links between inter-related categories (in mathematics or computer science this structure is called a partially ordered set).

There is one top-level category: Category:Contents. All other categories are subcategorized below this category.

Subcategorization

If logical membership of one category implies logical membership of a second category (an is-a relationship), then the first category should be made a subcategory (directly or indirectly) of the second category (the "parent" category). Any category may potentially contain (or "branch into") subcategories.

When making one category a subcategory of another, ensure that the members of the subcategory really can be expected (with possibly a few exceptions) to belong to the parent also.

A subcategory may potentially have two or more parent categories.

If two categories are closely related but are not in a subset relation, then links between them can be included in the category description of the category pages.

Pages (and subcategories) should not usually be placed in both a given category and any of its subcategories or parent categories. For some exceptions to this, see § Eponymous categories and § Non-diffusing subcategories.

Recursive categorization

Category chains formed by parent–child relationships should never form closed loops; that is, no category should be contained as a subcategory of one of its own subcategories.

Diffusing large categories

Although there is no limit on the size of categories, a large category will often be broken down ("diffused") into smaller, more specific subcategories. For example, Category:Rivers of Europe contains no articles about specific rivers directly; they are all in subcategories.

A category may be diffused using several coexisting schemes; for example, Category:Albums is broken down by artist, by date, by genre, etc. Metacategories may be created as ways of organizing schemes of subcategories. For example, Category:The Beatles albums is not placed directly into Category:Albums but into the metacategory Category:Albums by artist, which itself appears in Category:Albums by person then Category:Albums. (See Category:Categories by parameter.)

It is possible for a category to be only partially diffused – some members are placed in subcategories, while others remain in the main category.

Information about how a category is diffused may be given on the category page. Categories which are intended to be fully broken down into subcategories can be marked with the {{Category diffuse}} template, which indicates that any pages which editors might add to the main category should be moved to the appropriate subcategories when sufficient information is available. (If the proper subcategory for an article does not exist yet, either create the subcategory or leave the article in the parent category for the time being. However, avoid creating subcategories for just one article.)

To suggest that a category is so large that it ought to be diffused, or substantially diffused, into subcategories, you can add the {{Overpopulated category}} template to the category page.

Non-diffusing subcategories

Not all subcategories serve the "diffusion" function described above; some are simply subsets which have some special characteristic of interest, such as Best Actor Academy Award winners as a subcategory of Film actors. They provide an exception to the general rule that pages are not placed in both a category and its subcategory: there is no need to take pages out of the parent category purely because of their membership of a non-diffusing subcategory. (Of course, if the pages also belong to other subcategories that do cause diffusion, then they will not appear in the parent category directly.)

Non-diffusing categories should be identified with a template on the category page:

Subcategories defined by gender, ethnicity, religion, and sexuality should almost always be non-diffusing subcategories to prevent othering. The Wikipedia:Categorizing articles about people guideline outlines the rules on these categories in more detail.

Note that some categories can be non-diffusing on some parents and diffusing on others. For example, Category:British women novelists is a non-diffusing subcategory of Category:British novelists, but it is a diffusing subcategory of Category:Women novelists by nationality.

Sort keys

By default, a category page will list its member pages and subcategories alphabetically by their page titles. Sometimes, this is undesirable, so sort keys are needed to produce a better ordering. A sort key can be added to a page using {{DEFAULTSORT:sort key}}, which is a magic word that will cause the page to be sorted in categories under a different specified title. (Per MOS:ORDER, this is placed just before the list of category declarations.) The page title, and DEFAULTSORT, can also be overridden for individual categories using the same syntax as piped links: [[Category:Category name|sort key]]. For the mechanics, see Help:Category § Sorting category pages.

People are usually sorted by last name rather than first name, so "Last name, First name" sort keys are used (e.g. Washington, George for George Washington). There are many other rules for sorting people's names; for more information, see Wikipedia:Categorization/Sorting names.

Other sort key considerations (in no particular order):

Inappropriate categorization

Anyone who can edit a page may remove a questionable categorization. If an article has an "incorrect" or "inappropriate" category, remove that category from the article, and replace it (if applicable) with a more correct category.

Even if an article may occupy the grey areas of a category's inclusion criteria, that is not a valid reason to keep the article in a category. If a particular article does not fit the inclusion criteria of a category, then the article simply should not be added to it.

If categorization of any particular page is disputed, please discuss the categorization on the talk page of the page in question. If the category seems reasonable, but questionable in some cases, consider whether you can solve (part of) the problem by writing a clearer category description.

If you have a proposal for a better name for the category or for a wider re-arrangement of the categorization scheme, or if you have a concern that may apply to several members of the category (such as if the category violates one or more sections on this page, Wikipedia:Categorizing articles about people, Wikipedia:Overcategorization, or other Wikipedia policies and guidelines), you can start or participate in a discussion about the category.

Category talk pages are not always widely watched. Consider whether you can invite more potentially interested people to take part in a discussion, such as by discussing it at a relevant WikiProject, or at Wikipedia:WikiProject Categories. Another option could be to nominate the category for discussion at Wikipedia:Categories for discussion, or if the category name has an obvious typographical error, you can list it for speedy renaming at Wikipedia:Categories for discussion/Speedy.

See Wikipedia:Categories for discussion/How-to for instructions on how to use the templates for: deletion ({{cfd}}), renaming ({{cfr}}), or merging ({{cfm}}).

If you are in a content dispute, see Wikipedia:Dispute resolution for what to do next.

Category cleanup templates

See also

For browsing

For maintenance

Notes

  1. ↑ Additionally, the top-level category, Category:Contents, has no parent category.
  2. ↑ in declarative statements, rather than table or list form
  3. ↑ For an attempt to fix this issue in MediaWiki, see T5311.
  4. ↑ Mathematically speaking, this means that the system approximates a directed acyclic graph.
  5. ↑ This condition can be formulated in terms of graph theory as follows: the directed graph that has the categories as vertices and the parent–child relationships as edges should be acyclic.
  6. ↑ i.e. in code, {{DEFAULTSORT:Washington, George}}
  7. ↑ In 2016, English Wikipedia's category collation was changed to "uca-default", which is based on the Unicode collation algorithm (UCA). The most noticeable difference is that UCA groups characters with diacritics with their non-diacritic versions. See Wikipedia talk:Categorization/Archive 16 § OK to switch English Wikipedia's category collation to uca-default? and Wikipedia:Village pump (technical)/Archive 149 § Sorting in categories unreliable for a few days.
  8. ↑ This includes punctuation-like letters with no English equivalent, such as ʻ.
  9. ↑ Previously, zero padding was required to ensure single-digit numbers sorted before double-digit numbers (e.g. "09" for 9). This is no longer necessary.
  10. ↑ "µ" (mu) was previously used, but the capital version "Μ" was confusing.