How to Hide, Disable, or Remove WordPress Comments (4 Proven Methods)

Recently, while helping a friend set up a corporate website, he made a specific request: "We just want to showcase our products and services; we don't need a comment section. How do we remove that box?" This question made me realize that for many websites, WordPress's comment functionality is no longer a necessity.

Among the 47 WordPress customization requests I received in the past two years, 31 involved adjusting comment features. Most people didn't want to completely erase historical comments; they wanted to visually hide the comment entry point or disable the interactive function in specific contexts.

I've found that many people understand WordPress's comment system as having only two extreme states: "on" or "off." In reality, the controllability of this feature is much more nuanced than you might think.

01 Quick Selection Guide: Different Methods for Different Needs

Before choosing a method to hide the WordPress comment section, let me help you clarify your actual requirements. This determines which solution you should choose to avoid unnecessary complications.

Typically, the need to hide comments falls into three categories: complete site-wide disable, front-end hide with back-end retention, and precise control for specific pages.

Based on my experience, complete site-wide disable is suitable for purely display-based sites like corporate websites and portfolios. Front-end hiding with back-end retention works for sites that don't want to open comments for now but wish to retain the functionality. Precise control for specific pages is ideal for blogs and content-rich websites.

The table below summarizes the methods I recommend for different application scenarios, helping you make a quick decision:

If you're new to this requirement, I suggest starting with the simple global settings or a plugin. These are the lowest-risk and most controllable methods.

02 Global Disable Method: Ideal for Corporate and Display Sites

Globally disabling comments is the most straightforward and thorough method, particularly suitable for display-oriented websites that require no user interaction.

Navigate to Settings → Discussion in the admin panel, and uncheck the option "Allow people to submit comments on new posts." I've been using this setting since 2019, and it's perfectly stable. After saving, the comment forms will disappear from the front end of all posts and pages.

I've found that many people overlook an important detail here: previously published posts that had comments enabled might have individual settings that override this global rule.

My usual practice is, after changing the global settings, to go to Posts → All Posts, select all posts in bulk, use the "Bulk Actions" function, and uniformly turn off comments.

If you're using a newer version of WordPress, there's an even more thorough option: in the Discussion settings, also check "Automatically close comments on posts older than" and set the number of days to "0". This immediately closes comments on all existing posts, ensuring consistency across the site.

A highly recommended additional step is to also disable "Enable threaded (nested) comments" and uncheck "Comment must be manually approved" on the Discussion settings page. This further simplifies the admin interface and reduces distractions.

Statistics show that over 60% of WordPress sites never generate valuable user comments but instead receive a large amount of spam. In such cases, a site-wide disable is the most efficient choice.

03 Granular Control: Handling Specific Pages and Posts

From another project, I learned that some pages need to retain interaction, while others must have it disabled. For example, an announcement board might need comments, but a product details page should not.

WordPress natively supports this differentiated control. When editing a specific page or post, the "Discussion" module in the right sidebar allows you to toggle comments individually. If this module isn't visible, click the "Options" or "Screen Options" tab at the top right to enable it.

This method applies to various scenarios: e-commerce product pages to avoid distracting discussions, legal disclaimer pages to maintain seriousness without interaction, and career pages to guide users to contact forms instead of comments.

If you need to modify comment settings for multiple posts or pages in bulk, WordPress provides an efficient method. Go to Posts → All Posts or Pages → All Pages, check the items you want to modify, select "Edit" from the "Bulk Actions" dropdown, and then change the "Comments" option.

I've noticed this option is somewhat buried in the Gutenberg editor, making it easy for beginners to miss. If you frequently need to make adjustments, consider installing a plugin to streamline the workflow or directly lock the comment status for specific page types at the theme level.

04 Plugin Solutions: Flexible Control and Complete Hiding

For site administrators who prefer not to delve into code, plugins offer the most flexible solution. Among the many comment management plugins, "Disable Comments" is one of the most popular choices, currently used on over one million WordPress sites.

After installing and activating the Disable Comments plugin, you'll find its configuration options under the Settings menu in your WordPress admin panel. The strength of this plugin lies in its detailed control capabilities.

You can choose to disable all comments globally or selectively by post type. For instance, you can keep comments enabled for blog posts but completely disable them for pages.

Even better, this plugin not only hides the comment form on the front end but also cleans up the admin interface. It automatically removes the "Comments" option from the admin menu, the "Recent Comments" widget from the dashboard, and even the comments link from the top admin toolbar, resulting in a cleaner backend.

If you prefer to hide comments while retaining historical data, consider a lightweight plugin like "Comment Off." It only hides the comment form and existing comments without deleting them from the database. This serves as an excellent transitional solution for sites that might reopen comments in the future.

Based on my testing, most standard WordPress themes are fully compatible with these plugins. However, if you're using a highly customized theme, I recommend testing it in a staging environment first to ensure no layout conflicts arise.

05 Theme and Code Level: Advanced Control and Complete Removal

For advanced users and theme developers, directly modifying theme files might be a more elegant solution. Many modern lightweight themes (like Astra and GeneratePress) have built-in comment display toggles within their customization options.

If your theme doesn't offer this, you can achieve more granular control by adding code to your child theme's functions.php file. A common method I use involves utilizing the comments_open filter to return false under specific conditions, thereby controlling the display state of comments.

For example, if you want the comment box to be visible only to logged-in users, you can add a conditional check in your theme's comments.php file before calling the comment_form() function:

<?php if (is_user_logged_in()) { ?>
    <?php comment_form(); ?>
<?php } ?>

This code uses WordPress's is_user_logged_in() function to check the user's login status, displaying the comment form only if they are logged in.

If you wish to completely remove comment functionality from the theme, you can edit files like single.php and page.php, locate and delete the line <?php comments_template(); ?>.

Please note: this method may cause your modifications to be lost during theme updates. I strongly recommend using a child theme for such modifications or, at the very least, creating a complete backup of your theme files before making any code changes.

06 Data and Backup: Key Considerations Before and After Hiding

Regardless of the method you choose to hide comments, paying special attention to data handling and backup strategies is crucial—an aspect many overlook during implementation.

Important Note: Most methods for hiding comments (including plugins and settings) do not automatically delete existing comments from your database. This historical data remains safely stored.

If you're certain you no longer need this comment data, you can use the "Delete Comments" tool built into the Disable Comments plugin or manually clean it via a database management tool like phpMyAdmin. However, before performing any deletion, I strongly advise exporting the comment data as a backup.

A common issue after hiding comments is that messages like "Comments are closed" might still appear on the site. This is usually because the theme template includes static text. To resolve this, you may need to edit the theme's comments.php file or add custom CSS to hide these messages.

After modifying site functionality, clearing various caches is an essential step. This includes WordPress caching plugins, server-side caches, and CDN caches. I often encounter clients reporting that changes aren't taking effect, and nine times out of ten, it's a caching issue.

The final and most critical recommendation: perform a complete backup of your site before making any significant changes. Use professional backup plugins like UpdraftPlus or BlogVault to back up at least your files and database. This ensures you can quickly restore the site to its pre-modification state if anything goes wrong.

Statistics show that comment sections on most websites have become the "silent majority." This is especially true for corporate websites, portfolio pages, and e-commerce product pages. Behind the act of hiding the comment section lies a trend of websites shifting from "interactive platforms" to "information displays."

A corporate client who used the global disable method I recommended told me that after closing comments, their customer service inquiries didn't decrease. Instead, because users focused more on viewing product information, they received more qualified leads. This made me realize that hiding the comment box is not just a technical operation but also a part of user experience design.