Use a custom post type when you are creating a distinct kind of content with its own editing workflow or record structure. Use a taxonomy when you need reusable terms to classify content. Use custom fields for properties that describe an individual record. These tools are complementary: a movie site, for example, could have a Movie post type, a Genre taxonomy and a release-year field.
Choose by asking what the content represents
A post type defines what kind of record you are creating. WordPress already provides posts and pages; a custom post type makes sense for a distinct kind of content that should not be treated as either. WordPress Developer Resources gives Movies, Products, Projects and Assignments as examples of possible custom post types in its custom post type guidance.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Professional WordPress: Design and Development | $6.04 | Buy on Amazon |
| 2 |
|
WordPress Onder De Motorkap: WordPress aanpassen Onder De Motorkap (Dutch Edition) | $24.99 | Buy on Amazon |
A taxonomy defines how records are classified or grouped. Categories and tags are familiar examples; a custom taxonomy can represent classifications that fit your content better, such as movie genres or cook-time ranges. Taxonomy terms can be reused across records, and a taxonomy can be associated with more than one object type.
A custom field stores a value that belongs to a particular record. A release year or poster image can be fields on a movie record. If visitors need to browse or filter by a value shared across many records, a taxonomy may be more useful than a field. The right choice depends on whether the value is a property of one item or a reusable classification.
Recommended Free Tools
#1 Best Overall
- Used Book in Good Condition
When a custom post type is the right fit
- The content has its own editorial meaning or lifecycle, rather than being a standard post or page.
- Editors need a distinct admin screen or workflow for creating and managing it.
- Each item has a consistent record structure, potentially including fields such as director, release year or poster image.
- You need to configure its public behavior separately, such as whether it is publicly queryable or has an archive.
WordPress allows a post type to support features such as a title, editor, thumbnail, comments, statuses and custom fields. Which features and front-end behaviors are available depends on how the type is registered; the presence of a custom post type does not by itself mean it is publicly displayed. See the register_post_type() reference for the registration options.
When a taxonomy is the right fit
- You need shared terms to classify or group multiple records.
- Editors should manage terms separately from the records that use them.
- The classification should support navigation or filtering, such as browsing all records in a genre.
- The grouping may apply to more than one post type.
Taxonomies can be hierarchical, like categories, or flat, like tags. Their admin interface and front-end behavior depend on registration settings. You can also make a taxonomy internal rather than exposing term pages publicly. WordPress explains the available registration behavior in its register_taxonomy() reference.
Use post types, taxonomies and fields together
These are different parts of a content model, not mutually exclusive alternatives. For a movie site, the structure might look like this:
- Post type: Movie, for each individual movie record.
- Taxonomy: Genre, with reusable terms such as drama or comedy.
- Custom fields: Properties of each movie, such as release year, director or poster image.
WordPress Developer Resources lays out this relationship in its explanation of how post types, taxonomies and custom fields work together. Model each element according to its job: the record is the post type, the shared classification is the taxonomy, and the item-specific value is a field.
Check how editors and visitors will use the structure
Before registering anything, decide what people need to do with it. For editors, consider whether the item needs its own admin menu, which built-in features it should support, and whether terms should be hierarchical. For visitors, decide whether the content should appear in front-end queries, have an archive, expose taxonomy term pages, appear in navigation menus or be included in search.
Those behaviors are controlled by registration arguments, not simply by choosing a post type or taxonomy. In particular, a registered type or taxonomy is not automatically public in every sense. Set the intended admin and front-end behavior deliberately using the options documented for post types and taxonomies.
Keep content available when the theme changes
If the content should remain available after switching themes, WordPress recommends registering custom post types in a plugin rather than in the theme. A theme change should alter presentation, not make a site’s content model disappear. The Plugin Handbook’s custom post type guidance explains this recommendation.
Implementation details that prevent common problems
- Register a custom post type on the
initaction, not before it. - Register the taxonomy with
register_taxonomy()and explicitly associate it with the intended post type. Theregister_post_type()reference recommends declaring the relationship through thetaxonomiesargument so it is recognized consistently in query hooks. - Use unique, lowercase, prefixed identifiers. WordPress specifies a maximum of 20 characters for a post type key and 32 characters for a taxonomy key; its references also warn against reserved identifiers and query-variable conflicts.
- Choose public display, archives, rewrite behavior, admin UI, navigation-menu availability and search inclusion through the registration settings that match the site’s intended behavior.
For the exact arguments and constraints, consult the official references for register_post_type() and register_taxonomy().
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
