Skip to content

Create a Custom Taxonomy in WordPress Without Code

Key Takeaways

  • Nexter Extension requiere Content Fields activado en Nexter → Content Fields antes de crear una taxonomía personalizada sin código.
  • Una taxonomía en WordPress ofrece archivos de términos, filtrado y consultas correctas, y los editores gestionan sus términos ellos mismos.
  • Show in REST debe estar activado para que la taxonomía aparezca en el editor de bloques; si no está expuesta, no aparece aunque exista.
Table of Contents

A custom taxonomy is your own way of grouping content — Property Types, Cuisines, Departments — working the way categories and tags already do.

What It Does

Taxonomies give you term archives, filtering and proper queries. That is the difference between a taxonomy and a select field: WordPress can query a taxonomy, and editors can manage its terms themselves.

Before You Start

  • Nexter Extension is installed and active.
  • Content Fields is enabled under Nexter → Content Fields.
  • You have a field group, or are about to create one.

Create a Taxonomy

  1. Go to Nexter → Content Fields and open the Taxonomies tab.
The Taxonomies tab on the Content Fields screen
  1. Add a new taxonomy and enter its plural and singular labels.
  1. Set the taxonomy key. As with post types, treat this as permanent.
  1. Choose which post types it applies to.
  1. Decide whether it is hierarchical — like categories, with parents — or flat, like tags.
  1. Decide whether it is shown in REST, which it must be to appear in the block editor.
  1. Save, then open a post of that type and look for the new box.

When to Use It

  • Property Types on a listings site.
  • Cuisine and Course on a recipe site.
  • Department on a team directory.

Limitations

  • A taxonomy that is not shown in REST will not appear in the block editor, even though it exists.
  • Hierarchical or flat is a presentation and query choice; switching later does not reorganise terms already assigned.
  • The key is effectively permanent — term relationships are stored against it.

Troubleshooting

The taxonomy box is missing in the block editor

Turn on Show in REST. The block editor reads taxonomies through the REST API and ignores any that are not exposed.

Term archive pages 404

Save Settings → Permalinks once to flush rewrite rules.

Related Docs

Share your Thoughts

Still in Doubt? Let’s Assist You

Have Feedback or Questions?

Join our WordPress Community on Facebook!

Related Frequently Asked Questions

Why isn’t my custom taxonomy showing in the block editor?

Show in REST has to be enabled for the taxonomy to appear in the block editor. The block editor reads taxonomies through the REST API and ignores anything that is not exposed there. If the taxonomy exists but the box is missing, this is the first setting to check because the taxonomy can still be registered without being editable in the editor.

How do I fix 404s on custom taxonomy archive pages?

Flushing permalinks is the fix here. Save Settings → Permalinks once so WordPress rebuilds its rewrite rules, which is what controls term archive URLs. This matters after creating a taxonomy because the archive route may exist in WordPress but still fail until those rules are refreshed.

When should I use a custom taxonomy instead of a select field?

Use a custom taxonomy when you need term archives, filtering, and proper queries. That is the key difference from a select field: WordPress can query a taxonomy, and editors can manage its terms themselves. Nexter Extension, through Nexter Content Fields, is built for that kind of structured content grouping.

What kinds of sites benefit most from custom taxonomies?

The page points to three clear use cases: Property Types on a listings site, Cuisine and Course on a recipe site, and Department on a team directory. Those are good fits because they are content groupings that need archives or filtering, not just a static dropdown value.

What should I know before creating a custom taxonomy in Nexter?

Nexter Extension must be installed and active, and Content Fields must be enabled under Nexter → Content Fields. You also need a field group already set up or ready to create one. That setup matters because the taxonomy lives inside Nexter’s content fields workflow, not as a standalone WordPress setting.

Can I change a custom taxonomy from hierarchical to flat later?

The hierarchy choice is mainly about presentation and querying, not a full data reshuffle. Switching between hierarchical and flat later does not reorganise terms already assigned, so pick carefully up front. The taxonomy key is also effectively permanent because term relationships are stored against it.

Last reviewed: November 12, 2026

Related Docs