How to create custom post types in WordPress

Decide what the content represents, such as books, case studies or team members. Choose a singular label, plural label, internal post type key and public URL slug. Keep the internal key lowercase, use no spaces, and avoid generic slugs that may conflict with pages, plugins or themes. WordPress limits post type keys to 20 characters.

List the editor features you need, such as title, editor, excerpt, featured image, author, revisions and custom fields. Decide whether the type needs a public single URL, an archive page, search results and the block editor.

For the manual route, add the registration to a site-specific plugin rather than a theme. WordPress recommends a plugin so the content type remains available when you change themes. Register it on the init action with register_post_type().

A minimal example is function site_register_books(){register_post_type('site_book',array('labels'=>array('name'=>'Books','singular_name'=>'Book'),'public'=>true,'has_archive'=>true,'show_in_rest'=>true,'supports'=>array('title','editor','thumbnail'),'rewrite'=>array('slug'=>'books')));} add_action('init','site_register_books');. Replace the labels, key and slug with your own values, and prefix function names and identifiers to reduce collisions.

Use a taxonomy when visitors need to group or filter entries, such as genres, locations or departments. Register a custom taxonomy with register_taxonomy() and associate it with your post type. Register the post type and taxonomy on init; custom taxonomies still need their own registration even when listed in the post type's taxonomies argument.

For a few simple values, enable custom fields or add a meta box. For repeaters, relationships, validation and user-friendly field screens, use a dedicated custom-fields or content-modelling plugin rather than storing unstructured text in the editor.

Publish one test entry and decide how it should appear. A public post type normally needs a single-entry view and, if has_archive is enabled, an archive view. Your theme can provide these templates, or a block theme, page builder or dynamic-content plugin can render the title, content, featured image, taxonomy terms and custom fields.

Set show_in_rest to true if you want the post type in the block editor or REST API. Without it, the editor experience may be limited even though the post type appears in the admin area.

Go to Settings → Permalinks and select Save Changes once after registering or changing the post type. This rebuilds WordPress rewrite rules. If you skip it, single entries and archives commonly return 404 errors even when the registration code is correct. WordPress documents flush_rewrite_rules() for controlled programmatic flushing, but it is an expensive operation and should not run on every request.

Test the admin menu, editor, single URL, archive URL, search, taxonomy URLs and navigation links. If unrelated pages also return 404 errors, check for a duplicate page or archive slug and for overly broad custom rewrite rules. Support threads repeatedly identify slug conflicts and stale rewrite rules as common causes.

The fast route is to use JetEngine For Elementor. It provides screens for custom post types, taxonomies, dynamic fields, listings, filters and Elementor layouts, so you do not need to maintain the registration code or build every listing template by hand.

Install and activate the plugin, create the post type and its fields, choose the public slug, then build a listing and single-item layout in Elementor. Still check the generated URLs, avoid slug conflicts, and save the WordPress permalink settings after changing rewrite-related options. This route is a good fit when the site needs several content types, relationships or visual templates; the manual route is fine for one simple type that will be maintained by a developer.