I created a custom post type:

    'labels' => array(
        'name' => _x('Sample Posts', 'post type general name'),
        'singular_name' => _x('Sample Post', 'post type singular name')
    'public' => true,
    'show_in_nav_menus' => false,
    'exclude_from_search' => true

How can i disable the single post view for this specific post type? Displaying a simple 404 is fine, or redirecting to the homepage. This is inside a plugin, so i can't create a single-sample_post_type.php file to setup an empty page.



Redirect to a custom URL for single view, archive page is still publicly accessible.

You can use template_redirect hook to redirect for a custom post type, you can use any other URL you want to in place of home_url() and the error code in other argument.

add_action( 'template_redirect', 'wpse_128636_redirect_post' );

function wpse_128636_redirect_post() {
  if ( is_singular( 'sample_post_type' ) ) {
    wp_redirect( home_url(), 301 );


Completely disable Single or Archive page from front-end; Works for a Custom post only.

A alternative approach is to specify value for param publicly_queryable while registering the custom post if you are ok with displaying a 404 page. [ Thanks @gustavo ]

'publicly_queryable'  => false

It hides single as well as archive page for the CPT, basically completely hidden from front-end but can be done for custom posts only.

This second solution is best suitable for the scenario where you need a Custom post for admin/back-end usage only.

  • A good solution. I found it was helpful to only perform this redirect for non-authenticated users, by checking to see if get_current_user_id() evaluates to 0.
    – RevNoah
    Jun 29 '15 at 13:25
  • 2
    Please check the answer form @Gustavo
    – Richard
    Nov 18 '16 at 9:17
  • 2
    why not use only is_singular('post-type-slug') in the if() condition instead of 2 conditions?
    – Akash K.
    Oct 22 '18 at 20:36
  • @AkashK. Yeah that can work as well, wasn't aware of the function.
    – Kumar
    Oct 23 '18 at 6:26
  • 1
    Missing closing bracket in code - should be... if ( is_singular( 'sample_post_type' ) )
    – neilgee
    Aug 18 '20 at 4:31

Just setting the argument

'publicly_queryable'  => false

when you call register_post_type()

  • 1
    This looks like the answer to stop your CPT from creating actual web pages while still creating all database references. Sep 17 '15 at 18:11
  • 46
    This hides archive too
    – spaceman
    Oct 11 '16 at 16:12
  • 1
    This should be the accepted answer. Mar 16 '18 at 10:26
  • For me this causes a redirect to the homepage instead of a 404. Any ideas why? I'm registering the post_type with Piklist, in case that's relevant. Sep 9 '18 at 21:27

A simpler way to do that can be passing the following args when registering the Custom Post Type

'labels' => array(
    'name' => _x('Sample Posts', 'post type general name'),
    'singular_name' => _x('Sample Post', 'post type singular name')
'public' => true,
'exclude_from_search' => true,
'show_in_admin_bar'   => false,
'show_in_nav_menus'   => false,
'publicly_queryable'  => false,
'query_var'           => false
  • 3
    You would actually need publically_querable to be true for Post Type Archives to work.
    – Howdy_McGee
    Nov 12 '14 at 19:42
  • This does not work for me. It justs redirects back to the homepage when trying to go to the archive Jul 15 '15 at 15:51
  • Setting query_var to false only disables using query vars in the url, ie /?sample_post_type=sample_slug, but not from accessing it via /sample_post_type/sample_slug/ Jan 5 at 5:57

One. From your functions file.

add_action( 'template_redirect', 'redirect_cpt_singular_posts' );
    function redirect_cpt_singular_posts() {
      if ( is_singular('your-cpt-slug') ) {
        wp_redirect( home_url(), 302 );

Two. From your single.cpt.php file:

<?php wp_redirect( home_url() ); exit; ?>
  • I liked second option. But I need to know is there any drawback with this second option. Oct 10 '17 at 6:27
  • @user2584538 If you don't have a custom single-cpt_name.php file you could not do it. If you put the function in a simple plugin file, you could activate/deactivate without editing any file.
    – EliasNS
    Feb 5 '18 at 10:12
  • Drawback would probably be SEO wised. For any of those answer. I would recommend adding the following meta tag <meta name="robots" content="none, nosnippet, noarchive" /> on each page you decide to redirect. Jan 2 at 2:12

Tested all the ones mentioned above and the actual solution is simpler than any redirects suggested.

In order to have archive be accessible and list the items, and single post not be accessible and auto redirect to 404 set

'query_var' => false

when registering your CPT. If you set publicly_queryable to false your archives will be redirected to home, any other combo wont work. Set the query_var to false and that is it.

Here is full CPT https://gist.github.com/danyj/bfd038d3c8d578548c4d700bd0a7942a

see line 50 https://gist.github.com/danyj/bfd038d3c8d578548c4d700bd0a7942a#file-thz_cpt_items_single_view_redirect-php-L50

as stated here


Note: If query_var is empty, null, or a boolean FALSE, WordPress will still attempt to interpret it (4.2.2) and previews/views of your custom post will return 404s.

  • 2
    It feels a bit like a hack but it seems to work. Wish they'd just add a dedicated has_single property along with the existing has_archive property instead.
    – powerbuoy
    Jan 31 '19 at 13:40
  • Hi, I tried doing the same but it did not work. Despite adding the query_var to false, I can still visit the single page links. Can you help?
    – iSaumya
    Oct 13 '20 at 12:08
  • @iSaumya try to flush your permalinks (go to permalinks page and save again) or use wp-cli command wp rewrite flush && wp cache flush
    – thetwopct
    May 28 at 16:23

Working from of Sven's really good answer, I rewrote his function to make it easier to add multiple post types using in_array() in the if statement and then redirecting to the archive page instead of the home page.

(by the way, I think the setting query_var and/or publically_queryable to false will disable not only the single views, but also the native archive view, overriding 'has_archive' => true. In that case you can still set up a custom WP_query and create your own archive page, in a template, but the main query won't do that any more, will it?)

function fq_disable_single_cpt_views() {
  $queried_post_type = get_query_var('post_type');
  $cpts_without_single_views = array( 'my-post-type', 'my-other-post-type' );
  if ( is_single() && in_array( $queried_post_type, $cpts_without_single_views )  ) {
    wp_redirect( home_url( '/' . $queried_post_type . '/' ), 301 );

add_action( 'template_redirect', 'fq_disable_single_cpt_views' );
  • this was a good idea, but doesn't work if you change your redirect for the cpts
    – rudtek
    Mar 23 '20 at 17:57
  • 2
    I changed your wp_redirect line to wp_redirect( get_post_type_archive_link( $queried_post_type ), 301 ); works a charm!
    – rudtek
    Mar 23 '20 at 18:06
  • Nice. Good improvement.
    – slashbob
    Mar 24 '20 at 21:18

In case you want to completely disable custom post type single view on frontend but be able to display archive page things are getting a little complicated.

Setting publicly_queryable to false or rewrite to false will prevent for displaying both single and archive view. There is no flag in register_post_type function arguments to prevent creating only single view rewrite rules.


However you can remove rewrite tag after registering your post type and this will leave archive view rewrite rules untouched but remove only single view rewrite rules.

 * Register event post type
function wpse_128636_register_event_post_type() {

    $labels = array(
        'name' => __( 'Events' ),
        'singular_name' => __( 'Event' ),
        'add_new' => __( 'Add new' ),
        'add_new_item' => __( 'Add new' ),
        'edit_item' => __( 'Edit' ),
        'new_item' => __( 'New' ),
        'view_item' => __( 'View' ),
        'search_items' => __( 'Search' ),
        'not_found' => __( 'Not found' ),
        'not_found_in_trash' => __( 'Not found Events in trash' ),
        'parent_item_colon' => __( 'Parent' ),
        'menu_name' => __( 'Events' ),


    $args = array(
        'labels' => $labels,
        'hierarchical' => false,
        'supports' => array( 'title', 'page-attributes' ),
        'public' => true,
        'show_ui' => true,
        'show_in_menu' => true,
        'show_in_nav_menus' => true,
        'publicly_queryable' => true,
        'exclude_from_search' => true,
        'has_archive' => true,
        'rewrite' => array('slug' => 'event'),
        'capability_type' => 'post',

    register_post_type( 'event', $args );
    remove_rewrite_tag( '%event%' ); // This line will remove event rewrite rules for single view

add_action( 'init', 'wpse_128636_register_event_post_type' );

Another bonus is that from now on you can create simple WordPress pages using event post type permalink structure (event/simple-page) which can be helpful in complex websites.

Remember to flush rewrite rules after code modification.

  • 1
    This should be the accepted answer, its short, simple and doesn't mess with archive pages. Jun 12 '20 at 20:17
  • For me, it turns the single pages into 404 pages, but YOAST SEO still places the links in its XML sitemap. Apr 23 at 17:13

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.