Table of Contents
How to disable comments in WordPress is the process of turning off native discussion features at global, post-type and legacy-content levels so no new threads open and old ones close or vanish. A good implementation removes front-end forms, closes existing threads and cleans database rows. A bad one hides the form but leaves comment feeds, REST endpoints and spam vectors active.
Vendors differ sharply on scope. Some toggle one setting. Others run SQL cleanup, patch WordPress site monitoring rules and lock future re-enables. Buyers should ask for a written scope before signing. Budget ranges below show what money actually buys in 2026.
Why Disabling Comments Is a Vendor Decision
Site owners rarely need comments in 2026. Corporate sites, portfolios and foreign trade stores use forms instead. Comments add 40-70 ms of server time per uncached page. They add 12-30 spam rows daily on a small site. They expose wp-comments-post.php to bots. A vendor must remove load, not just the box.
Cheap vendors use a plugin. Strong vendors edit settings, then clean data. Ask which approach you get. Plugin-only work fails audits. Manual work survives them.
How to Disable Comments in WordPress: 5 Steps
- Go to Settings then Discussion and uncheck “Allow people to submit comments on new posts” to stop future threads.
- Edit each existing post type in bulk: set comment status to closed for every legacy item via Quick Edit or SQL.
- Remove comment form markup from theme files if your vendor built a custom child theme.
- Run a database cleanup to delete orphan comment meta rows and reduce table bloat.
- Verify by loading a post URL and checking the REST API for no open comment endpoints.
Each step takes 10-40 minutes on a 500-page site. Skip step 4 and you keep 300 MB of junk. Skip step 5 and you miss open feeds.
Vendor Options Compared
Get a Quote
Email + requirement + budget range — we reply with a quote within 24 hours.
| Scope Level | Price Range 2026 | Deliverables | Risk Left |
|---|---|---|---|
| Plugin toggle only | $50 – $150 | Disable Comments plugin installed | Data rows remain, REST open |
| Settings + bulk close | $200 – $450 | Global off, legacy closed, form removed | Meta rows stay |
| Full cleanup | $500 – $900 | Settings, SQL trim, endpoint lock, QA | Near zero |
| Enterprise hardening | $1,200+ | Above plus WAF rules and monitoring | None |
Most buyers pick full cleanup. It costs 2-4 hours of senior time. Plugin-only work is 20 minutes and fails later.
Methods Vendors Use
Plugin Route
A vendor installs a disable plugin. It hides forms fast. It does not delete rows. It can break if a plugin updates. Use it only on a staging test.
Manual Route
The vendor edits Discussion settings, runs bulk edit and trims SQL. This is what our Custom WordPress Development team does. End-to-end website development with tailored themes, SEO-ready architecture and security hardening is included. Result is clean and audit-ready.
Code Route
Vendor adds filters in functions.php to close comments by post type. Good for custom builds. See WordPress developer docs for hooks. Risk is a typo breaking the site.
Common Mistakes
- Hiding the form with CSS only: bots still post to the endpoint. Avoid by closing status in the database.
- Forgetting legacy posts: old pages keep open threads. Avoid bulk Quick Edit on all post types.
- Leaving comment feeds live: RSS spam continues. Avoid by disabling feed endpoints in settings.
- Ignoring REST API: mobile apps can still read comments. Avoid by locking endpoints during cleanup.
- Skipping backup: a bad SQL run loses data. Avoid by taking a full dump before any delete.
Related Build Choices
If you plan a new site, read How to Build a Website with WordPress in 2026: Vendor Guide first. It shows where comment setup fits the wider build. Sites for export also face template choices; see the foreign trade vendor guide for scope tips.
FAQ
How long does a full disable take?
Two to four hours for 500 pages. Includes settings, bulk close, SQL trim and endpoint check.
Do I lose old comment content?
Yes on cleanup. Back up first if you want archive. Most corporate sites delete rows to cut load.
Can comments be re-enabled later?
Yes in settings. A hardened vendor locks this with role caps so only admins can flip it back.
CTA
Need clean comment removal as part of a bigger build? Talk to our team at https://runokwp.com/en/contact/. We scope, clean and harden in one engagement for 2026 sites.
