Section 230 Explained: Why You Can’t Always Get Content Removed

Section 230 is a 1996 federal law that says a website is not legally the publisher of content its users post. In plain terms: if a stranger writes a false review or a damaging post about you on Yelp, Google, Reddit, or a gossip forum, you generally cannot sue the platform to force it down. Your legal target is the person who wrote it, not the site that hosts it. Understanding this one rule saves you weeks of chasing the wrong party, and it points you toward the approaches that actually work.

Almost everyone who finds something harmful about themselves online has the same first instinct: make the website take it down, and sue them if they refuse. It feels obvious. It is also, in most cases, a dead end, and Section 230 is the reason. Here is what the law actually says, what it does not cover, and what to do instead.

What Is Section 230?

Section 230 is part of the Communications Decency Act of 1996. Its core sentence is short: a provider of an “interactive computer service” cannot be treated as the publisher or speaker of information provided by someone else. Strip out the legal language and it means a website is not legally responsible for what its users write.

That covers a huge range of sites, not just the big platforms. It protects Yelp from a user’s harsh review, Facebook from a comment in a group, Reddit from a post in a thread, a local news site from what readers say below an article, and a volunteer-run hobby forum from its members’ arguments. If a site hosts content that other people created, Section 230 generally shields it from being sued over that content.

The law also does a second thing. It lets platforms moderate, meaning remove or filter posts, without losing that protection. A site can take down some posts and leave others up and still keep its immunity. This is why “you removed his post but not mine, so now you’re responsible for mine” is not an argument that works.

Why It Exists

Section 230 solved a specific problem from the early internet. Before it, courts had created a trap: a platform that ignored everything and moderated nothing was treated as a neutral distributor and escaped liability, but a platform that tried to clean up its worst content was treated as a publisher and became liable for everything its users posted. Moderating made you more legally exposed, not less.

That gave sites two bad choices: allow a free-for-all of spam and abuse, or face endless lawsuits for trying to keep things clean. Section 230 removed the trap by letting platforms host user content and moderate it in good faith without owning legal responsibility for every word. Supporters credit it with making the modern participatory internet possible: reviews, comments, forums, and social media all depend on it.

What It Means When You Want Something Removed

Here is the practical translation, and it is the part worth internalizing.

When someone posts something false and damaging about you, Section 230 means your legal recourse is against the author, not the platform. If a person writes a defamatory review about you on Google, you may be able to sue that person. You generally cannot sue Google. The same is true on Facebook, Reddit, Yelp, and complaint sites.

Two details make this stricter than most people expect:

• Notice does not change it. Even after you tell a platform that a specific post is false and defamatory, Section 230 generally still protects the platform if it decides to leave the post up. Unlike copyright law, ordinary defamation law does not force a platform to act once it is notified.
• Their refusal is usually legal. When a review site or forum declines your removal request, it is often standing on solid legal ground. Its entire business model is built on the fact that it is not liable for what users post. This is why complaint sites can be so stubborn.

None of this means the content is permanent or that you are powerless. It means the pressure point is not the platform’s legal liability. It is somewhere else, and we will get to where.

What Section 230 Does Not Protect

The shield is broad, but it has real edges. Section 230 does not cover several things, and these edges are exactly where your options live.

Not protected by Section 230	What that means for you
The person who wrote the content	The author is fully responsible for their own words. A defamation claim against them is not blocked.
Content the website created itself	If the site wrote the defamatory material, or materially developed it, it is not a neutral host and loses protection.
Intellectual property claims	Copyright is carved out. A DMCA takedown for your stolen photo or text works, and hosts must respond to it.
Federal criminal law	Section 230 does not immunize violations of federal criminal law, which is part of why laws targeting non-consensual intimate images can reach platforms.
Court orders	A court order finding specific content defamatory can be used to get search engines to deindex it, sidestepping the platform’s immunity entirely.

Read that table again as a menu rather than a list of limits. Every row is a door. The most useful ones for most people are the first (go after the author), the third (use copyright if it is your material), and the last (a court order unlocks search removal).

What to Do Instead

Once you accept that the platform usually will not be forced to act, the real options come into focus. There are four, and they work best together.

Go after the author, not the platform. If a provably false statement of fact is damaging you, the person who wrote it is fully responsible. A cease-and-desist letter or a defamation claim targets them, and a court order finding the statement defamatory can then compel search engines to remove it. Our guide on internet defamation covers when this is worth pursuing.

Use copyright if it is your material. Copyright is the biggest exception to Section 230. If a site reposted a photo you took or text you wrote, a DMCA takedown is a real legal lever the host must respond to. Our guide on filing a DMCA complaint walks through it.

Get it out of Google instead of off the site. You do not need the platform’s cooperation to change what people find. Google removes pages that expose personal data, and a court order can force broader deindexing. Removal from search often solves the practical problem even when the page still exists. See our pillar guide on removing content from Google search.

Outrank it. For content that is legal and simply unflattering, the most reliable fix is suppression: publishing stronger, accurate content that pushes the negative page down where few people look. This is the backbone of most reputation work, covered in our guides on reverse SEO and the full range of options in removing negative content from the internet.

When a site has flatly refused, our companion guide on what to do when a website won’t remove content lays out the escalation path step by step.

Is Section 230 Changing?

Section 230 turned 30 in 2026, and it is under more political and legal pressure than at any point in its history. Lawmakers from both parties have proposed narrowing or repealing it, and courts have begun testing its edges. Some recent cases suggest platforms might face liability tied to their own design choices, such as how their algorithms recommend content, rather than for the underlying user posts. Separately, courts are wrestling with whether AI-generated content produced by a platform’s own tools falls outside the shield, since the platform arguably created it.

For now, the core rule still stands: platforms are generally not liable for what their users post, and you usually cannot sue a site into removing third-party content. These developments are worth watching, but they have not changed the practical playbook. Plan around the law as it is today, not as it might become.

Frequently Asked Questions

What is Section 230 in simple terms?

Section 230 is a 1996 federal law that says websites are not legally the publisher of content their users post. In plain terms, if someone writes something false or harmful about you on a platform like Yelp, Google, Reddit, or Facebook, you generally cannot sue the platform over it. The law treats the website as a host, not the author, so responsibility falls on the person who actually wrote the content. It also lets platforms moderate posts without losing that protection.

Can I sue a website for a defamatory post about me?

Usually not the website itself, because Section 230 shields platforms from liability for content their users create, even after they are notified it is false. You can, however, sue the person who wrote the defamatory statement, since Section 230 does not protect the author at all. A court order finding the content defamatory can also be used to get it removed from Google search results. Because this is fact-specific, consult an attorney about your situation.

Does Section 230 mean nothing can be removed?

No. It means the platform usually cannot be forced to remove third-party content through a lawsuit, but you have other routes. You can pursue the author legally, file a DMCA takedown if the content uses your copyrighted material, ask Google to remove pages that expose personal data, obtain a court order to compel search removal, and suppress the content by outranking it. Section 230 limits one path, not all of them.

Why do complaint sites refuse to remove posts?

Because Section 230 lets them. Sites like complaint boards and gossip forums are generally not liable for what users post, even defamatory content, and even after being notified. Their entire business model relies on that immunity, so they often refuse removal requests on principle. This is legal on their part. The practical response is to target the author, use copyright or court orders where they apply, and suppress the content in search.

Is Section 230 going to be repealed?

It is under active debate. In 2026, lawmakers from both parties have proposed reforms, and courts are testing its edges around platform design, algorithms, and AI-generated content. But as of now it remains in force, and the core rule holds: platforms are generally not liable for user content. The developments are worth following, but they have not changed the practical steps for getting harmful content addressed, so plan around the law as it stands today.