CPT, Custom Taxonomies, and Custom Fields: Do you really know when to use each one?
Many people who develop in WordPress have heard of these three features:
- Custom Post Types (CPT)
- Custom taxonomies
- Custom fields (ACF, Meta Box etc.)
But the truth is that not everyone knows how to make the right choices when structuring a project.
I often see bloated sites, with poorly planned structure, simply because someone used custom fields for everything — including where they should have created a CPT or a taxonomy.
Let’s simplify:
-
Custom Post Type (CPT) Use when you need a new type of content with its own identity. Ex: “Portfolio”, “Events”, “Properties”, “Products”. It is ideal when the content requires an individual page, specific slug and separate management in the admin.
-
Custom Taxonomies Use when you want to organize or classify content in a CPT. Ex: Categories of a portfolio, regions of a property, themes of an event. It serves for grouping and logical navigation.
-
Custom Fields Use when content needs specific data, but not new content types. Ex: Price of a property, date of an event, color of a product. Here, the data is associated with a post — it does not create a navigation structure.
In short:
- Custom field saves data.
- Taxonomy organizes.
- CPT represents a new type of content.
Making these choices correctly directly affects the performance, scalability and maintainability of the project.
It’s not about making it work. It’s about doing it right.
Do you usually map out this structure before starting a project? Or do you still define it as you code it?