Two statements on this page matter more than the rest, so they come first and without qualification.
Nothing on this site is legal advice, and I am not a lawyer. Several pages here discuss statutes, causes of action, court filings, regulator actions, copyright notices and reporting channels, because a reference on negative SEO that ignored the legal picture would be useless to the people who need it most. That material is written as a practitioner's description of how these mechanisms have actually been used, from sourced and dated material. It is not an opinion about your matter, it is not a substitute for counsel, and it should not be relied on to decide whether to send a notice, file a claim, respond to one, or let a limitation period run. If a legal question is live for you, take it to a lawyer licensed in your jurisdiction. My own work in litigation is as a testifying expert, which is a different role from an attorney's and does not include advising you on the law.
Nothing on this site is an offer to perform, broker or assist any attack. This practice sells negative SEO recovery and nothing else. It does not run attacks, does not arrange for anyone else to run them, does not sell links, and does not consult on how to damage a competitor. The attack profiles exist so that a defender can recognize a mechanism and undo it, and they are written to that limit deliberately: no tool configurations, no vendor or marketplace names, no operational procedures. A meaningful number of the searches that reach this domain every month come from people trying to hire an attacker, and the page written for those readers tells them no, on the facts.
No guarantee of any outcome
Recovery from a genuine attack is not guaranteeable by anyone, and a promise of restored rankings, traffic or revenue is the clearest warning sign in this field. Search engines control their own indexes and their own timelines, platform complaint processes reach their own conclusions, and no practitioner controls any of it. What can be promised is method: establishing what actually happened, documenting it while the evidence still exists, and doing the remediation the evidence supports. Where the evidence supports doing nothing, that is what I will tell you, and it is the most valuable sentence in most engagements.
Information, not diagnosis
The pages here are general. Your case has a history, a market, a link profile, a hosting arrangement and a records position that I have not seen, and any of those can invert the right answer. A disavow file is the standing example: for most sites it is unnecessary and Google's own documentation says so, but there are narrow circumstances where it is correct, and a page cannot tell you which side of that line you are on. Read this site to understand the mechanisms and to frame better questions, not as a diagnosis of your own situation.
Accuracy, dates and sources
Every factual claim here comes from a source, and effectiveness claims carry dates because on this subject the answer changed: attacks that demonstrably worked between 2012 and 2016 mostly do not work now, and stating a 2013 fact in the present tense produces a wrong fact. Quotations from search engine documentation are attributed and linked so you can check them, and where an account is self-reported or has never been independently tested, the page says so rather than dressing it up. Even so, documentation gets rewritten, platforms change their processes, and pages here can fall out of date between revisions. If you find something wrong, tell me through the contact page and it will be corrected.
Third parties and named cases
This site takes no position on any identifiable third party and accuses no named company of running an attack. Where documented incidents are described, they are drawn from published, sourced accounts — court filings, regulator actions, platform announcements, named published experiments — and are described with their limitations, including whether anything was ever independently verified. Platform and product names appear descriptively; no affiliation with or endorsement by any platform is claimed.
Limitation
I do not accept liability for loss or damage arising from reliance on anything published here. Use of the site is on the terms set out on the terms of use page, which should be read alongside this one. Nothing here limits any liability that cannot lawfully be limited.