Categories, tags, and taxonomies

Admin → Content → Categories & Tags manages the terms of every taxonomy on the site. Every site has Categories (category, which can be nested) and Tags (tag, a flat list) for posts. Administrators can add taxonomies of their own, such as *Genres* or *Regions*, and choose which content types use each one.

Manage terms#

• Add a term by name. The slug is generated from it, or type your own: lowercase letters, numbers, and hyphens.
• Rename or re-slug a term. A new slug redirects the term's old archive URL and every post URL that used it.
• Nest categories, or terms of any hierarchical taxonomy, by choosing a parent. A term can never become its own ancestor.
• Delete a term to remove it from every entry. Its child terms move up one level.

Custom taxonomies#

+ New taxonomy asks for a name, a slug (used in archive URLs and the API), whether its terms can be nested, and the content types that use it. Settings on a taxonomy changes its name, description, and content types later; whether it is nested is fixed when you create it. Deleting a taxonomy deletes all its terms. category and tag are built in and cannot be deleted.

Assign terms in the editor#

The editor sidebar shows a picker for every taxonomy the entry's content type uses. Terms are saved with the entry, up to 100 per taxonomy. Editors can create a missing term straight from the picker; authors choose from the terms that exist, and are told to ask an editor for a new one. Creating, renaming, and deleting terms needs content:publish.

URLs and archives#

• A post's first category fills the %category% token in a permalink structure. Posts without a category use uncategorized.
• Term archives such as /category/news and /tag/release list the published entries that carry the term. The bases are set under Settings → Permalinks (category and tag by default), and custom taxonomies can have a base of their own.
• Changing a post's category, or a term's slug, redirects the old URL to the new one with a 301.

API and AI agents#

PUT /api/manage/v1/content/{id}/terms

{ "terms": { "category": ["<term id>"], "tag": ["<term id>", "<term id>"] } }

MCP agents get the same operations as taxonomies_list, taxonomies_create, taxonomies_update, taxonomies_delete, terms_list, terms_create, terms_update, terms_delete, content_terms_get, and content_terms_set.