The real question behind the question
Whether to allow comments is not really about comments. It is about whether you have the attention to run them and whether your audience is the kind that benefits from talking back. Plenty of good sites disable comments and are right to. Plenty of others leave money and loyalty on the table by staying silent. The answer depends on your situation, so look at both sides honestly before deciding.
The case for allowing comments
Comments turn a one-way page into a place where readers do something. That has a few concrete benefits.
- Engagement and return visits. A reader who leaves a comment has a reason to come back and see the reply, which builds a habit around your site.
- Trust and social proof. A thread of genuine questions and answers shows a new visitor that real people read and value your work.
- Better content. Comments surface gaps, corrections, and follow-up questions that tell you what to write next.
- Fresh, relevant text on the page. Genuine discussion adds content that can help a page stay useful over time, as long as it is real and moderated.
The case against
Comments are not free. They cost attention and carry risk.
- Moderation time. An unwatched comment section fills with spam and, sometimes, hostility. If you cannot commit to checking it, do not open it.
- Tone risk. A few bad actors can make a thread ugly and reflect badly on your brand, even when most readers are fine.
- Performance and privacy. A heavy, tracking-laden comment widget slows your pages and exposes readers. A poor tool makes the whole idea worse than it needs to be.
- Low volume can look worse than none. An empty comment box under every post can read as a quiet room. This is fixable with time, but worth knowing.
When to say no
Turn comments off, or leave them off, if your content invites more heat than light, if you genuinely have no time to moderate, or if your pages are conversion-focused landing pages where discussion adds nothing. It is also fine to allow comments on some pages and not others. You do not have to make one blanket decision for the whole site.
If you say yes, run them well
Most of the downsides come from running comments badly, not from having them. A few choices make the difference.
Pick a moderation mode that matches your risk
You do not have to approve every comment by hand forever. A sensible progression is to pre-moderate everything at the start, then move to auto-approving returning verified people while still holding anonymous posts for review. Gabden supports exactly these modes: pre-moderate everything, auto-approve, auto-approve returning verified people, or moderate only anonymous users. A blocked-word filter and a spam queue take care of the routine junk so you spend your time on real replies.
Lower the barrier to the first comment
Forcing an account before someone can speak kills participation. Let readers post anonymously, as a guest with a name and email, or with a Google or GitHub sign-in if they want a persistent identity. Give people the fast path and more of them will use it.
Keep it light and private
A comment section should not slow your pages or track your readers. Gabden's embed is around 10KB and loads asynchronously, uses no tracking cookies and no fingerprinting, and reports only anonymous aggregate analytics. That removes two of the strongest arguments against allowing comments in the first place.
Turn them off where they do not belong
Allow comments where discussion helps and switch them off where it does not. Per-page rules let you disable comments on specific URLs, so your landing pages stay clean while your articles stay open.
A practical default
For most blogs the answer is yes, on your articles, with moderation set to hold anonymous and new posts while trusting returning people, using a tool that stays light and does not track. That captures the engagement without most of the cost. If you decide to try it, you can create an account and add one script tag, or read how to get more blog comments for tactics once comments are on.
Join the discussion