Deleting a WordPress category removes that organisational label, not the posts assigned to it. Review where those posts should appear and how readers reach the category archive before deleting an established category.
IN THIS ARTICLE
01 Review assignments and links
Open Posts, Categories and check the category's post count. A zero count is useful evidence but does not prove that no menu or external link points to its archive. For a populated category, decide whether to rename it, merge its editorial purpose into another category, or remove the grouping entirely.
02 Remove a category deliberately
- Assign affected posts to their intended replacement categories. Use the post list filter to review the selected category and edit the relevant items.
- Confirm that the category being removed is not the default under Settings > Writing. Choose and save another default first if necessary.
- Return to Posts > Categories, locate the exact category and use Delete. For several genuinely unused categories, review the selection before applying the bulk delete action.
- Update navigation links, widgets and content links that pointed to the removed archive. Plan a redirect only where an appropriate replacement collection exists.
Confirm the expected result
Open several affected posts and confirm their categories. Posts that would otherwise have no category use the default category; do not assume WordPress chooses the best replacement topic for you. Review child categories as well, because deleting a parent changes the remaining hierarchy.
How can I correct a mistaken category deletion?
Categories do not use the same Trash workflow as posts. Recreating a category with a similar name does not necessarily restore its old identity or every assignment. If a large structural change was wrong, review a backup-based recovery plan before overwriting the database, especially on sites receiving new posts, comments or orders.
If the archive continues to appear after removal, check caches and redirects before repeating the deletion. The post content should remain accessible at its own URL unless another setting or action also changed it.