The short answer for US plaintiffs is no. 47 U.S.C. § 230(c)(1) provides that no provider or user of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider. Courts have applied this to immunize search engines, social-media platforms, hosting providers, and review sites from liability for third-party content. Google's role in indexing and surfacing content created by others falls squarely within § 230 immunity in nearly every reported case.
The longer answer is that the immunity is broad but not unlimited. Six narrow categories of conduct have produced exceptions in published opinions over the past two decades, and a handful of those exceptions have generated meaningful judgments against Google or similar platforms. This guide explains the immunity, walks through each exception with the leading case, and covers the parallel rules in the UK, EU, and a few other jurisdictions where the answer is meaningfully different.
The structural question for any plaintiff considering action against Google is also covered: what to do instead. The realistic remedies for a defamation victim whose reputation has been damaged by content surfaced through Google Search are different from a defamation lawsuit, but they are real and well-defined.
What Section 230 actually does
Section 230(c)(1) immunizes interactive computer services from being treated as the publisher or speaker of third-party content. Section 230(c)(2) immunizes good-faith content moderation. Section 230(e) carves out specific federal-law areas where the immunity does not apply: federal criminal law, intellectual-property law, the Electronic Communications Privacy Act, and (since FOSTA in 2018) sex-trafficking law.
The leading case construing § 230 is Zeran v. America Online (4th Cir. 1997), which established that the immunity applies to claims based on the platform's role as the distributor or publisher of third-party content, including knowledge-based theories of liability after notice. The Zeran approach has been followed by every federal circuit and most state supreme courts.
For Google specifically, the immunity has been applied to suits over Search results (Parker v. Google, E.D. Pa. 2007), autocomplete suggestions (Hassell v. Bird, Cal. 2018, partially), Knowledge Panel content sourced from third-party data (multiple unreported cases), and Google Maps user reviews (multiple unreported cases). The pattern is consistent: where Google is acting as a conduit for third-party content, § 230 immunity applies.
The six exceptions and what each requires
Six fact patterns have produced exceptions to § 230 immunity in published opinions. Each is narrow and difficult to satisfy in a defamation context against Google.
First, the platform's own content. § 230 immunizes liability for third-party content, not for content the platform itself created. Where Google creates and publishes content (Knowledge Panel summaries that Google authored, Google's own statements in product help articles), § 230 does not apply. Practical reach for defamation plaintiffs is narrow because Knowledge Panel content is overwhelmingly aggregated from third-party sources.
Second, material development by the platform. Where the platform materially contributes to the alleged unlawfulness of the content (not just hosts it but adds substantively to its illegality), Roommates.com (9th Cir. 2008) held that § 230 does not apply. The standard is high; ordinary indexing, ranking, and surfacing do not count.
Third, federal intellectual-property claims. § 230(e)(2) excludes IP law from the immunity. Copyright and trademark claims against Google are not barred by § 230, though they typically must navigate the DMCA safe harbor (§ 512) or trademark fair-use doctrine separately.
Fourth, federal criminal law. § 230(e)(1) excludes federal criminal liability. Civil suits piggybacking on federal criminal statutes (RICO, certain ECPA provisions) have produced occasional non-immunized claims.
Fifth, FOSTA-SESTA. § 230(e)(5), added in 2018, excludes claims based on sex trafficking under 18 U.S.C. § 1591 and related state laws.
Sixth, contract and promissory-estoppel claims based on the platform's specific commitments. Where the platform made specific representations to the plaintiff ("we will remove this content if you provide X documentation") and breached those representations, contract and promissory-estoppel claims have occasionally survived § 230 motions - but only on the contract theory, not on a defamation theory.
Hassell v. Bird and the limit of removal orders
Hassell v. Bird (Cal. 2018) is the leading case on whether a court can order Google or a similar platform to remove third-party content based on a defamation judgment against the speaker. The plaintiff sued the original speaker (a reviewer who had posted negative content about her law firm on Yelp), obtained a default judgment, and then sought to enforce the judgment by ordering Yelp to remove the review. The California Supreme Court held that § 230 barred the order; even where the underlying speaker has been adjudicated to have defamed the plaintiff, the platform retains its immunity and cannot be ordered to remove the content.
Hassell substantially limits the practical value of a defamation judgment in cases where the goal is removal. Plaintiffs who win against the original speaker often find that the platform will voluntarily remove the content in response to the judgment, but they cannot compel removal through court order in jurisdictions following Hassell.
Some state courts have reached different conclusions in narrower contexts (orders directly to the speaker requiring the speaker to remove their own post are not foreclosed by Hassell), but the broad rule - no compelled removal of third-party content from the platform - has held in most jurisdictions.
Hassell v. Bird (Cal. 2018) substantially limits the practical value of a defamation judgment for removal purposes: even where the original speaker has been adjudicated to have defamed the plaintiff, the platform retains its Section 230 immunity and cannot be ordered to remove the content.
Gonzalez v. Google and Twitter v. Taamneh
The Supreme Court's 2023 term included two cases watched closely for their potential to reshape § 230. Gonzalez v. Google asked whether § 230 immunity extends to algorithmic recommendation of third-party content. Twitter v. Taamneh asked whether platforms could be liable as aiders and abettors of terrorism under 18 U.S.C. § 2333 for hosting ISIS content. The Court's decisions left § 230 substantially undisturbed: Taamneh resolved on aiding-and-abetting grounds without reaching § 230, and Gonzalez was remanded in light of Taamneh without a § 230 ruling.
The combined effect was to stabilize § 230 jurisprudence in the short term. The plaintiffs' bar's expectation that algorithmic recommendation would be a § 230 exception has not materialized in any reported circuit opinion since. Pending challenges in the lower courts continue, and several proposed federal bills (Justice Against Malicious Algorithms Act, EARN IT Act variants) would carve out additional categories, but as of mid-2026 the immunity remains broad.
Outside the US: UK, EU, and Australia
UK law applies a narrower immunity. The Defamation Act 2013 § 5 provides a defense for website operators who follow specified procedures when they receive a defamation complaint about user-posted content, including identifying the poster where possible. UK plaintiffs have successfully sued Google in cases involving search-result snippets that contained defamatory text (Metropolitan International Schools v. Google UK, 2009; Tamiz v. Google, 2013). Where the snippet itself contains the defamation, Google's role as the publisher of the snippet has been recognized.
EU law treats search engines as data controllers under the GDPR with respect to the personal data they index. The Google Spain v. AEPD decision (2014) established the right of EU residents to request delisting of inadequate, irrelevant, or excessive search results. Defamation claims against Google in EU jurisdictions are typically pursued through the GDPR delisting framework rather than tort litigation.
Australian law historically allowed defamation claims against search engines for results returned (Trkulja v. Google, 2018), though the 2021 amendments to the Defamation Act created a safe-harbor-style defense for digital intermediaries. Australia remains one of the more plaintiff-friendly jurisdictions for search-engine defamation claims.
What to do instead
For US plaintiffs whose reputation has been damaged by content surfaced through Google Search, the realistic remedies do not include suing Google. They include suing the original speaker (who has no Section 230 protection), filing DMCA takedown notices for content that infringes the plaintiff's copyrighted material (Section 230 does not preempt the DMCA), filing right-to-be-forgotten / personal-information-removal requests through Google's expanded 2022-2024 personal-data-removal policy, and suppressing the content through SEO tactics that push it down in search results.
For EU and UK residents, the GDPR Article 17 erasure right and the Google Spain delisting framework provide direct paths to remove content from search results without any defamation litigation. The EU framework operates on a higher denial-rate but-with-meaningful-success-rate basis (Google's published statistics show 47-51% of delisting requests succeed), and the regulatory escalation path through national supervisory authorities provides a real second-tier remedy.
The combined approach for most plaintiffs is to pursue the original speaker through traditional defamation channels while in parallel using the platform-specific removal channels (DMCA, GDPR, personal-information removal, fake-review reporting) to address the visibility problem. Suing Google is rarely a successful strategy and almost never the most efficient one.
