Disable WordPress Comments by Post Type
A website does not need the same discussion policy everywhere. A publication might welcome comments on articles while keeping service pages free of discussion. A business site may want neither posts nor pages to accept comments, while a separate public content type still has a legitimate use for them. Treating these situations as one global switch can remove useful functionality along with the parts you intended to close.
Disable Comments lets you make that decision at the post-type level. Select the eligible types that should no longer accept comments and leave the others alone. An empty selection means the module does nothing. On a site using Custom Post Type Builder, this provides a separate control over discussion for the content structures you create rather than assuming every new type should follow the same publishing policy.
Remove the Discussion Experience, Not Just Its Form
Closing new comments alone can still leave a visible list of old replies, comment-count links, and editing options that suggest discussion is part of the site. That may be appropriate for an archived conversation, but it is not the result every business website wants. When a type is disabled here, WP PowerSuite closes the form, hides existing frontend comments, and reports a zero comment count for the affected content.
Stored comments are not deleted. The distinction matters when you are redesigning a site, changing its public communication strategy, or testing whether discussion should remain visible. You can remove the frontend experience without treating that decision as a database-cleanup operation. The module also does not overwrite WordPress's global default comment-status option, keeping its targeted restrictions separate from the site's underlying Discussion preferences.
Give Editors a Cleaner Dashboard
A comment-free website does not need to keep directing editors toward unused discussion tools. Disable Comments removes comment and trackback editing support for affected types and can remove their comment columns from list tables. The Recent Comments widget can also be removed from the Dashboard, helping the administration interface reflect how the website is actually managed.
The Comments menu is removed when its cleanup option is enabled or when all comment-capable public types are disabled. Access to the Comments screen is redirected in those circumstances, and the toolbar Comments item disappears whenever any types are disabled. On a mixed site that still uses comments elsewhere, review the menu-removal choice so administrators keep a sensible route to the discussion they manage. Admin Menu Organizer can handle broader sidebar organization without changing this module's comment policy.
Keep API Behavior Aligned With Your Comment Policy
A missing frontend form should not be the only barrier to comment creation. For selected disabled types, WP PowerSuite blocks REST comment inserts as well. This makes the restriction apply to the supported submission process rather than depending on whether a visitor can see a comment box in the theme.
The broader API removal is intentionally conditional. Only when every comment-capable public type is disabled does the module remove the core comments REST routes and XML-RPC new-comment method. When discussion still belongs on another type, those interfaces remain available subject to the per-type restrictions. This is not a complete REST or XML-RPC shutdown; it is a comment-specific policy that avoids disabling unrelated WordPress functionality.
Keep Communication Channels Appropriate to the Site
Disabling comments is useful when discussion is not part of a particular page's purpose. It is not a substitute for moderating conversations you actually want to keep. A support article with a valuable public discussion may deserve a different choice from a service landing page, and the module's selected-type approach lets those decisions coexist.
For a broader overview of stored content and comment statuses, Content Report Widget provides dashboard counts. Those counts describe stored records, whereas Disable Comments changes whether affected discussions are available on the frontend. Hiding comments should therefore not be mistaken for removing them from the database or clearing a moderation backlog. Choose the module when the aim is to turn the discussion feature off, not to rewrite or evaluate past conversations.
