Comment moderation on agency social media: what the law allows

Reference article · 5 min read

An agency that turns on comments creates more than a communications channel. It opens a space where the public speaks, and where the First Amendment limits what the agency may do about what is said. The people moderating it are usually communications staff, not attorneys, using tools built for private brands that can delete whatever they want.

What follows is how courts treat agency comment sections, what the blocking cases decided, a moderation standard you can defend, and the logging that lets you explain a removal later. Forum doctrine is fact specific and still developing, so have counsel review any policy before you publish it.

Why an open comment section is a limited public forum

Courts analyze restrictions on speech in spaces government opens for expressive activity under public forum doctrine. Federal appellate courts have applied that framework to the interactive portions of official social media accounts, generally treating comment threads as a designated or limited public forum.

The distinction that matters most is between content and viewpoint. In a limited public forum an agency may impose reasonable restrictions consistent with the forum's purpose, including subject matter limits. It may not discriminate based on viewpoint in any forum. You can require that comments relate to the subject of the post. You cannot remove critical comments while leaving supportive ones up. The agency's own posts are government speech. The forum is in the replies.

What the blocking cases decided

In 2024 the Supreme Court decided Lindke v. Freed and, the same day, O'Connor-Ratcliff v. Garnier. Lindke set the test for when an individual official's social media activity counts as state action: the official must have actual authority to speak for the government on the matter, and must have purported to exercise it in the posts at issue. Garnier was returned for reconsideration under that test.

• Those cases concern individual officials' mixed use accounts. An account the agency owns and operates is government activity, so the forum analysis applies directly.
• Blocking is blunt. It removes a person's ability to comment on every post, including posts that do not exist yet, which is far harder to justify than removing one comment.

Officials with personal accounts should label them personal, keep agency business off them, and route announcements to the agency account.

A moderation standard you can defend

Write rules about the form of a comment rather than the opinion it expresses, and apply them the same way no matter who is speaking.

• Off topic. Comments unrelated to the subject of the post.
• True threats, incitement, and targeted harassment. Aimed at an identifiable person.
• Obscenity. The narrow legal category, not profanity generally, unless you filter all profanity uniformly.
• Personal information. Social Security numbers, medical details, home addresses, and anything state law protects.
• Spam. Enforced against all sellers, not only unwelcome ones.

Avoid categories like inappropriate, offensive, disrespectful, or false. They invite viewpoint based application and have not held up well when challenged. Escalate in order: leave the comment, reply with a correction, hide, delete, and only then block, with notice, for repeated conduct and for a defined period.

Keyword filters without viewpoint discrimination

Most platforms let you auto hide comments containing terms on a blocked word list. That is useful, and it is where agencies most often get into trouble.

• Filter categories, not critics. A uniform profanity list is defensible. A list containing an official's name, a program name, or words that appear mainly in complaints functions as viewpoint suppression.
• Watch the queue. Held comments are often invisible to staff too. Assign someone to review them on a schedule and release the ones that break no rule.
• Version the list. Record each term, the date added, and the reason. A list assembled during a controversy is difficult to explain afterward.
• Know what hiding does. On several platforms the author still sees their own hidden comment, so the complaint arrives later rather than never.

Logging that lets you show your work

The question you will eventually be asked is why a specific comment disappeared. Build the answer as you act.

• Capture the comment before you act: full text, author handle, timestamp, and the post it replied to.
• Record which published rule applied, who decided, and what action was taken.
• Retain the record under your retention schedule. Comments on official accounts are often public records under state law, including ones you removed. Definitions and schedules vary, so confirm yours with your records officer.
• Prefer a tool that archives threads continuously over screenshots taken after the fact.
• Publish a way to ask for review, and answer those requests.

How to start, and what to ask vendors

1. Inventory every account carrying the agency's name, including ones staff created and forgot.
2. Adopt one counsel reviewed policy and link it from each account profile, so it is visible before someone comments.
3. Limit delete and block permissions to named, trained staff.
4. Decide how threads will be archived before the next high volume post.

For an archiving or moderation product, ask:

• Capture before moderation. Does it record the original comment and the removal event, including comments the author deletes?
• Export. Can you produce a single thread, with metadata, in a form that answers a records request?
• Filter history. Does it log changes to the blocked word list and who made them?
• Retention, holds, and roles. Is retention configurable to your schedule, with legal hold, and are block and delete restricted and logged per user?

Put data ownership, export on termination, configurable retention, and audit logging in the contract rather than in product settings a later release may change.

HQT builds and integrates software for state and local agencies, including records capture and disclosure workflows behind public facing systems.

Frequently asked questions