Disable Comments

Quick take

A practical administrative tool when comments are not part of the site strategy. Its strength is enforcing one clear policy instead of leaving comment settings scattered across WordPress.

Best fit: Business, brochure, documentation, multisite, and other WordPress installations that do not need public comments or only need them on clearly defined content types. I would choose a different option for publishers that want fine-grained discussion on individual posts while keeping comments active broadly across the site.

On sites that never use comments, leaving discussion features active creates unnecessary moderation work, spam exposure, and admin clutter. Disable Comments turns those systems off more comprehensively than changing one post at a time.

How it works

Disable Comments centralizes comment controls for WordPress. It can disable discussion across selected post types, remove comments-related UI, delete existing comments, and block comment submission through REST API and XML-RPC routes.

Choose whether comments should be disabled everywhere or for selected content types. The plugin then applies the policy across the admin and frontend, with additional controls for deleting existing comments and blocking external comment submission routes.

Features that matter

• Disable comments globally or by post type: Applies one comment policy across the whole site or selected content types.
• Remove comments-related admin UI: Removes discussion controls from admin areas where they are no longer needed.
• Bulk-delete existing comments: Can clear comments that were stored before the policy changed.
• REST API comment blocking: Extends the disabled-comment policy beyond the visible front-end form.
• XML-RPC comment blocking: Keeps the same policy across older remote-publishing routes.
• Multisite support: Supports consistent comment settings across multisite installations.

Where centralized comment control helps

The value is consistency. On sites that never use public discussion, disabling comments individually leaves room for new post types, templates, or imported content to reintroduce comment UI later. A centralized policy is easier for administrators to understand and maintain.

Where the trade-offs show up

Publishers that want fine-grained discussion on individual posts while keeping comments active broadly across the site should compare alternatives carefully. Overkill for a few individual posts. Deleting comments is destructive and should be reviewed first. Product-review workflows need careful testing.

Practical considerations

Before disabling comments everywhere, check whether WooCommerce reviews, custom post types, membership discussions, or editorial workflows rely on WordPress comments behind the scenes. A global switch is convenient, but it can also remove functionality that a plugin or theme expects, so staging is the right place to validate the policy. Document the decision as well, so future administrators understand that comments were intentionally disabled rather than broken.

Pricing

The core Disable Comments plugin is free on WordPress.org.

Who should consider it

Business, brochure, documentation, multisite, and other WordPress installations that do not need public comments or only need them on clearly defined content types.

What to compare before choosing

If you still want comments but mainly need spam filtering, compare Antispam Bee or Akismet instead. Disable Comments is for removing the discussion feature, not moderating it.

PluginSuggest verdict

A practical administrative tool when comments are not part of the site strategy. Its strength is enforcing one clear policy instead of leaving comment settings scattered across WordPress.

Disable Comments FAQs