Comparisons

Choosing a commenting system for news sites

What a news site needs from comments: moderation that scales, privacy, and speed that holds up at volume.

Choosing a commenting system for news sites

News comments are a different problem

Comments on a news site behave nothing like comments on a hobby blog. Stories break fast, threads fill in minutes, topics get heated, and the traffic can spike an order of magnitude on a single article. A comment system that is fine for a personal blog can buckle here, on moderation load, on page speed, or on the privacy exposure of running trackers across a large readership. Choosing well means planning for the hard days, not the quiet ones.

Moderation that scales with volume

The core requirement is moderation that does not depend on someone watching every thread. On a busy news site you need layered controls:

  • Modes you can dial by risk: pre-moderate everything on sensitive stories, auto-approve returning verified people on routine ones, or moderate only anonymous users.
  • A blocked-word filter to catch slurs and known bad terms before they publish.
  • A spam and pending queue your team can clear quickly.
  • Per-page rules so you can close comments on a specific story that has turned toxic without shutting the whole site's comments off.
  • Team roles with per-module permissions, so moderators can review without touching billing or configuration, and you can add newsroom staff as needed.

The ability to close comments on one URL is worth calling out. On news sites, the problem is usually one story, not the whole section. Per-page control lets you handle the flare-up surgically.

Privacy at scale is a bigger deal

A tracking-heavy comment widget is a liability anywhere, but on a high-traffic news site the exposure is larger and the compliance stakes are higher. A system with no tracking cookies, no fingerprinting, and no cross-site tracking keeps your readers' data out of the ad ecosystem and keeps you out of a category of consent and regulatory headaches. Analytics should be anonymous aggregate counts, not per-reader profiles you now have to account for. For a newsroom that reports on privacy, running a reader-tracking widget is also just a bad look.

Speed under load

News readers arrive fast and judge fast. A heavy comment script that adds hundreds of kilobytes will hurt your Core Web Vitals on exactly the articles getting the most traffic. A small embed, around 10KB, that loads without blocking the page keeps comments from becoming a performance tax during a spike. Page speed is not a nice-to-have for publishers; it feeds both reader retention and search ranking.

Identity that fits a broad public audience

News audiences are wide and not especially patient. Requiring an account before anyone can react to a story suppresses participation. A system that lets readers post anonymously, as a guest with a name and email, or signed in with Google or GitHub covers the range, from the drive-by reader who wants to say one thing to the regular who wants a consistent identity. Hosted profiles help your regular commenters build recognition, which tends to raise the quality of a comment section over time.

Owning the archive

Comment history has value to a publisher: it is reader engagement, context, and sometimes a record. A system that lets you export everything as JSON or CSV means the archive is yours. It also means you can migrate in without starting empty. Gabden can import existing comments from Disqus, native WordPress, and other systems, mapped to each page's URL, so a newsroom switching platforms keeps its threads attached to the right stories.

Where Gabden fits

For a news site, the shortlist is privacy, moderation range, and speed, and Gabden is built on those. One script tag, keyed to each article's canonical URL, adds a thread that loads light and tracks nobody. Moderation covers the modes, the blocked-word filter, the queue, per-page rules, and team roles you need for a busy section. Pricing stays predictable: free up to 100,000 widget views per month per website, and 5 dollars per month per website for unlimited views with the mark removed. For a high-traffic publisher that will likely mean the Plus plan per property, which you can see on the pricing page.

The right test is a real one. Put the widget on a live article and watch how it handles a busy thread. You can create an account and try it, and the docs cover the moderation settings a newsroom will want to tune first.

Join the discussion