SERP Defamation Campaigns

What a SERP defamation campaign is

Defamation is a false statement of fact, published to a third party, made with the requisite level of fault, that causes reputational harm. A SERP defamation campaign is defamation aimed at a search result: web pages built or amplified so that they rank in Google for your brand name, accusing you of fraud, scams, non-payment, harassment or crime. Written defamation is libel; spoken is slander. What makes the search version distinctive is not the accusation but the placement.

The target is not a competitive keyword. It is the query a customer types when they have already decided to buy from you and are running one last check. That is the highest-intent search anyone will ever perform about your business, and it is the one you have the least ability to control.

Three quite different things are filed under this heading, and they have completely different remedies:

• Third-party complaint platforms. Consumer grievance sites that accept user-submitted posts, publish them permanently, index heavily and rank well for brand-plus-modifier queries. The platform did not write the post. That fact turns out to be legally decisive.
• Purpose-built grievance sites. A domain registered specifically about you, or an account created to accumulate accusations. Here there is an identifiable author and a single point of legal contact, which makes this the most tractable version of the three.
• Amplified single posts. One accusation, with a sustained effort behind it to make that page rank for your name. This is the variant that most resembles classic negative SEO, because the ranking is engineered rather than earned.

The mechanism is unglamorous. Brand-name queries have very few documents that are genuinely about that brand, so Google has a thin set to rank. A page that names your company in its title, its heading and its body is topically relevant to your name whether you like it or not. Your own site usually holds the first three or four positions with sitelinks; the attack is aimed at five through ten, which is precisely where a nervous buyer scrolls.

Why this is the least contested attack on this site

Every other page here turns on an argument about what a search engine does with a signal. This one does not, and that is what earns the documented-threat verdict without qualification.

A SERP defamation campaign does not manipulate a ranking system. It creates a genuinely relevant document for a query with almost no competition. From Google's side, nothing spammy has happened: a page about a company appeared, and people search for that company. There is no spam classifier that neutralizes it, because there is nothing for a spam classifier to find. Google's own spam policies do not reach it, and filing a spam report is wasted effort.

Nor does Google treat a defamation allegation as a search quality matter. Its published removal policies for Search list the categories it will act on without a court order: images of minors, child sexual abuse material, personally identifiable information and doxxing content, personal sexual content, and content about a person on sites with exploitative removal practices. Business defamation is not on that list. Google's separate legal removal channel invites reports of content that violates the law, and in the United States that route means, in practice, a court order.

Where it works best. Against small and mid-size brands with a thin branded results page — one website, a social profile or two, no press coverage, no directory listings, no knowledge panel. Against a distinctive coined brand name, because there is no ambiguity to dilute the query. Against sectors where consumers actively search for the word "scam" beside a company name: finance, crypto, home services, coaching, supplements, debt relief. And against anyone whose own domain does not already occupy the whole first page.

Section 230 is why the platform will not help you

Most owners learn this expensively. Section 230 of the Communications Decency Act, 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 information provided by another information content provider. Subsection (e)(3) preempts inconsistent state law. Two decisions convert that statute into a practical rule for a defender.

Fakhrian v. Google Inc., 2016 WL 1650705 (Cal. Ct. App., 25 April 2016), held that Google is not required to de-index a complaint page. Section 230 immunity applies to search engines, and it applies even where the search engine has notice of the allegedly defamatory content. The claim was also time-barred: the post dated from 2008, the suit from 2014.

Hassell v. Bird, S235968 (Cal., 4 July 2018), closed the obvious workaround. The California Supreme Court reversed an order directing a non-party platform to remove reviews a court had already found defamatory, holding that lawsuits seeking to hold a service provider liable for its exercise of a publisher's traditional editorial functions are barred. You cannot obtain by injunction against the platform what section 230 forbids you to obtain by judgment. The United States Supreme Court declined further review in 2019, leaving the decision intact.

The consequence is the sentence people pay lawyers to hear: the only person you can sue is the author. And the author is frequently anonymous, judgment-proof, outside the jurisdiction, or all three.

There is one materially better case, and it is worth checking for before anything else. Where the party behind the grievance page is a competitor rather than a consumer, the Lanham Act, 15 U.S.C. §1125(a), reaches false or misleading statements of fact made about your goods or services in commercial advertising or promotion. A commercial rival's manufactured grievance site is a far stronger claim than an angry customer's post, it carries a federal forum, and it usually travels with a state tortious interference claim. Establishing who is behind the page is therefore not idle curiosity; it changes which body of law you are in.

The court-order remedy, and the scandal that damaged it

The obvious remaining move is to sue the author, obtain an order declaring the content defamatory, and send that order to Google. This page will not tell you that produces de-indexing, because the record does not support it and because of what happened to the remedy in 2017.

Eugene Volokh of UCLA and Paul Alan Levy of Public Citizen documented roughly two dozen libel suits filed against apparently fabricated defendants. In each, a "defendant" who could not be located at the address given promptly consented to an order declaring the material libelous, and the order was then sent to Google. Named matters included Smith v. Garcia in the District of Rhode Island, which was vacated for fraud, along with Financial Rescue LLC v. Smith, Rescue 1 Financial LLC v. Doe and Visionstar, Inc. v. Perez. Richart Ruddie and SEO Profile Defender Network LLC settled, agreeing to pay $71,000 and to vacate orders in related cases. Volokh published the account in The Volokh Conspiracy on 17 May 2017.

Google's handling of unlitigated defamation orders tightened materially once that became public, and the effect is still felt. So the honest statement of the remedy is this: a court order is the eventual instrument, not a guaranteed outcome. Google's own policy pages do not commit to honoring United States defamation orders, practitioners report varying results, and every order now arrives at a company that has been shown forged ones. Anyone offering you guaranteed de-indexing through a court order in this environment is describing a route into a fraud investigation, not a service.

The timeline, compressed: section 230 enacted in 1996 makes the platforms immune. The forged-order scheme is exposed in 2016 and 2017, and the court-order route becomes slower and more scrutinized. Hassell in 2018 forecloses injunctions aimed at non-party platforms in California. In 2022 Google broadens its personal-information removals and adds the exploitative-removal-practices policy.

What Google will remove, and the exclusion that matters most

There is one Google policy written for exactly the fact pattern of a site that publishes accusations and then charges to take them down. It is narrower than it sounds, and the limiting condition is the part nobody reads.

Google's policy on content on sites with exploitative removal practices states three conditions that must all hold, and one of them is that the website is not a business review site. Complaint platforms that present themselves as review sites are therefore largely outside this route, and that is the single most common disappointment on this topic. The policy exists; it is real; it will very often not cover the page in front of you.

Google also operates removal-based demotion systems. Per its ranking systems guide, where Google processes a significant volume of personal-information removals involving a site with exploitative removal practices, it demotes other content from that site, with a parallel mechanism for high volumes of valid copyright removals. The threshold for "significant volume" is not quantified anywhere, and no source I found documents a specific instance of a named complaint platform being visibly demoted. Treat it as a mechanism Google describes, not as a lever you can pull.

What does not help, and is worth listing because each of these is attempted daily: disavowing links pointing at the grievance page, which the disavow tool cannot do and would not demote them if it could; filing a spam report, because the page is not spam under Google's policies; filing a reconsideration request, because there is no manual action; buying removal from anyone promising guaranteed de-indexing; and arguing in the comments.

Telling an attack from an unhappy customer

One boundary first, because the two get confused constantly: coordinated fake ratings on a map listing or a review platform are a fake negative review attack, governed by the platform's own user-generated-content policies and removable through them. This page is about organic web results ranking for your name, governed by section 230 and defamation law, where no such removal route exists. Different attack, different remedy, and the wrong one wastes weeks.

Beyond that, this is the most important distinction on the page and the one most often got wrong. An honest negative review is not defamation, is not negative SEO, and attacking it is the fastest way to convert a small problem into a large one. Establish which you have before doing anything.

Detection here happens on the results page, not in Search Console.

• Search your own brand name logged out, in a private window, on desktop and on mobile, and page past the first ten results. Then search the modifier set: your brand with scam, complaints, reviews, lawsuit, fraud, fake, and your founder's personal name on its own.
• Search Console, Performance, Queries, filtered to your brand. Rising volume on brand-plus-negative-modifier queries with falling clicks to your site means people are finding, and clicking, something that is not you.
• Alerts and brand monitoring on the company name, the executives' names and the product names. The earliest signal is the page appearing, days or weeks before it ranks, and that head start is worth more than any later remedy.
• Referral logs. A grievance page that links to you sends a trickle of traffic; the referrer shows up before the ranking does.
• A link tool's new-referring-domains report, pointed at the other page. The amplified-single-post variant is visible as a burst of links aimed at a third-party URL that mentions you. Almost nobody checks this, because owners monitor links to their own domain only.
• Registration records. For a purpose-built grievance domain, the creation date establishes when the campaign began, which matters evidentially even when the registrant is masked.

What it is mistaken for. Genuine dissatisfied customers, above all. Also: an ordinary ranking loss, where your own pages fell and nothing rose against you; a competitor's comparison page, which is lawful comparative marketing; and an old dormant complaint that simply moved up because your supporting pages weakened. If your own positions dropped and the grievance page did not move, you have a ranking problem, not an attacker.

How it is undone, in order

The order is the advice. Steps taken out of sequence are how this gets worse.

1. Read it and decide honestly whether it is true. If the underlying complaint is substantially accurate, no legal or search remedy is available or deserved. Fix the underlying problem and respond publicly and calmly.
2. Preserve evidence before touching anything. Full-page captures with the visible URL and timestamp, independent web archive captures, registration records, and a screenshot of the results page showing the position. Everything you might do next can cause the content to change or vanish.
3. Suppression before litigation. This is unglamorous and it is what actually works. A branded results page with four or five documents about you is the vulnerability; owning eight or ten is the fix. Your own supporting pages, verified profiles on platforms you control, earned press, industry and association listings, executive profiles, structured data supporting a knowledge panel. It is slow, it depends on nobody's cooperation, and it is the only part of this that compounds. No controlled study of how fast suppression works has ever been published, so any timeline you are quoted is a sales figure, mine included, which is why I do not quote one.
4. Approach the author, not the platform — and only with advice. A polite correction sometimes works. A legal threat to a private individual over a review can trigger a far larger audience than the review had, and in states with anti-SLAPP statutes it can end in an adverse fee award against you.
5. Use the platform's own process where one exists, understanding that it is entirely discretionary. Section 230 protects the platform whether it removes the post or refuses to.
6. Google policy removals, for the narrow categories Google acts on without a court order, remembering the business-review-site exclusion above.
7. Litigation against the author, where identifiable and solvent, with an order sought as the eventual de-indexing instrument. Expect it to be slow, expect the order to be scrutinized, and expect discovery to make everything public.

The downside risks nobody warns you about

This is the one topic on this site where the wrong response costs more than the attack.

Anti-SLAPP fee-shifting. A majority of states have statutes designed to end lawsuits aimed at protected speech early. Lose one and you can be ordered to pay the other side's legal fees. That is the largest single downside in this subject, and it is created entirely by your own decision to sue.

Publication of the removal attempt. Legal removal requests and court orders sent to Google are frequently published to the Lumen Database. The attempt itself becomes a public, searchable document, and it names you.

The Consumer Review Fairness Act, 15 U.S.C. §45b. This one cuts against the business, which is why it belongs here. The CRFA prohibits non-disparagement provisions in consumer form contracts: you cannot use standard terms to stop customers publishing negative reviews or to threaten them for doing so. The FTC brought its first actions exclusively under the CRFA on 8 May 2019, against three companies. Reacting to a complaint campaign by tightening your customer contract is walking into federal enforcement risk.

Paying for removal. It funds the model, it is the exact conduct Google's exploitative-removal policy was written for, and it marks you as a paying target. Where removal is offered for money, that is a criminal matter, and it should be treated as one rather than as a pricing negotiation.

Publishing a furious rebuttal that repeats the accusation. You have now created a second page ranking for your brand name beside the word scam, and this one is yours, on your own domain, with your own authority behind it.

Two smaller ones worth naming. Mass-registering defensive domains and filling them with thin pages does not work; Google ranks few of them and the pattern is itself a quality problem. And the phrase "right to be forgotten" is European, has no direct United States equivalent, and is invoked constantly by people who are about to be disappointed.

Frequently asked questions