Get your free SEO audit today — Call 91 060 30 90
</>Technical Guide · 27 min read

Negative SEO and link protection: disavow, spam attacks and how to defend yourself

Negative SEO is the set of deliberate actions a third party carries out to try to damage the rankings of someone else's website, usually a competitor's. The distinction matters because it is used far too often as a catch-all excuse for traffic drops that actually have an internal cause (an algorithm update, a technical mistake, weak content): real negative SEO implies intent and an external origin, not a mistake made by the site's own team.

Before getting into the techniques it's worth settling something clearly, because it's the question that generates the most anxiety and gets answered worst in forums: Google has stated publicly, through its own spokespeople (John Mueller and Gary Illyes, in Office Hours and on social media), that the vast majority of attempts to "attack" a site with links have no real effect. The reason is Penguin, the system launched in 2012 to devalue manipulative link profiles, which since 2016 has been part of Google's core algorithm, updating in real time. Penguin isn't designed to actively penalize the site receiving the spam links, but to identify them and simply ignore or devalue them when calculating authority. In practice, if a third party buys ten thousand links from link farms pointing at your domain, Google will most likely detect them for what they are and discard them from the calculation, with no direct harm to your site from their existence.

If you need professional help with this, at 3CWeb we offer an SEO audit service.

That said, "most attacks don't work" isn't the same as "no attack ever works." It's worth acting when Google notifies a real manual action in Search Console mentioning unnatural links to your site (something that happens, less often than people believe), when there is reasonable certainty of active, sustained manipulation over time, or when the attack isn't about links at all but of another kind (a hack injecting content) with direct technical consequences. The rest of the cases, the vast majority, don't call for any drastic action, and even less for using the Disavow Tool at the first sign of a strange-looking link.

The most common attack techniques

The best-known technique is flooding the target site with thousands of low-quality links from link farms or PBNs (private blog networks, networks of blogs created artificially just to link to each other and to third parties). The attacker's goal is to simulate a manipulative link profile in the hope that Google will mistake it for the target site's own practice and act accordingly. As explained above, this rarely achieves anything because Penguin is specifically designed to recognize and neutralize exactly this pattern.

A second technique is scraping: copying articles, product pages or entire pages from the target site and republishing them unchanged across dozens or hundreds of low-quality domains. It doesn't directly attack your rankings (Google is usually good at identifying the original source versus the copy, especially if your content was indexed first), but it can create brand noise or siphon off traffic in markets where your original site has no presence.

The third common technique is campaigns of mass spam comments on other people's forums, blogs and directories, always linking to the same target domain with the same anchor text, so it looks as if the site itself is promoting itself in a manipulative way. It's cheaper and easier to run than setting up a PBN, which is why it's also the most common choice in low-budget attacks, usually launched by small competitors rather than sophisticated actors.

The fourth, and the only one that leaves the purely link-based territory to enter the territory of security, is directly hacking the target site to inject hidden links, new spam pages or disguised redirects that only crawlers see (cloaking). This is by far the most serious variant of all, because it doesn't depend on Google being able to tell what's external from what's your own: if the injected code lives inside your own domain, Google treats it as your content until it is cleaned up and the cleanup is verified.

How to detect a real attack (and not an imaginary one)

The only reliable way to know whether something is going on is periodic monitoring of your link profile, not a one-off reaction when someone "notices something odd." The reference tools for this are the link report in Google Search Console (free, with data straight from Google, though with some delay), and third-party tools with their own crawl of the web such as Ahrefs, Semrush or Majestic, which show historical volume, estimated quality of the originating domains and the speed at which new links appear in more detail than Search Console.

The real warning signs, as opposed to the normal noise of any link profile, are: a sudden, very pronounced spike of new links in a short period (days, not months) from domains with almost no authority or with no topical relation to your industry; the exact same anchor text repeated unnaturally across hundreds of links, something that almost never happens in an organic profile; and mass links from languages or topics with no logical connection to your business (for example, spikes of links in Russian or Chinese to a local Spanish business with no international presence). No single signal on its own is proof of an attack, but their combination, especially if it coincides with a drop in visibility, does justify a deeper investigation.

Google Search Console's Disavow Tool

The Disavow Tool explicitly asks Google to ignore certain URLs or entire domains when evaluating your link profile. It doesn't remove the links (that isn't within your power if you don't control the originating domain) and it doesn't guarantee anything on its own: it's a request, not an order, though Google honors it in practice when used correctly.

The technical mechanics are simple: you upload a plain text file (.txt), one entry per line, which can be an exact URL or an entire domain prefixed with domain:. Lines starting with # are treated as comments and Google ignores them. A real example of valid format:

# Links disavowed for mydomain.com - 2026 review
# Link farm detected in November
domain:spamfarm-example.com
domain:junklinksite.net
domain:pbn-links-example.com

# A one-off spam comment on a forum, not the whole domain
http://forum-example.com/thread-with-spam-comment-12345

The difference between disavowing a specific URL and disavowing with domain: matters and is often used incorrectly: disavowing the whole domain discards all present and future links from that domain, the right choice when the spam pattern is systematic and affects the entire originating site (a whole PBN, a link farm). Disavowing just a specific URL makes sense when the rest of the domain is legitimate and only an isolated page (for example, a spam comment on an otherwise normal, respectable forum) is the problem.

The warning Google itself gives about this tool, documented as such in its own help center, is that it's an advanced tool that, used badly, can do more harm than good. The main risk isn't leaving out some bad link (Penguin was probably already ignoring it anyway), but mistakenly disavowing legitimate, valuable links that were contributing positively to your rankings, losing real authority over an unnecessary precaution. That's why Google explicitly recommends using the Disavow Tool only in two scenarios: when there's a real manual action notified in Search Console related to unnatural links, or when there's reasonable certainty (not a vague suspicion) that active, large-scale manipulation is taking place. It is not recommended, and can actually be counterproductive, to use it preventively against any link that simply "looks odd" at first glance.

Practical steps in the face of a real attack

If, after monitoring your link profile, there are serious signs of a real attack, the recommended order of action is as follows. First, document and capture evidence as soon as possible: screenshots of the links, of the originating pages and of the dates, because spam sites and PBNs tend to disappear or clean themselves up right when they start drawing attention, and without evidence it's hard to prove anything afterward.

Second, and before touching the Disavow Tool, try to contact the webmasters of the originating sites to ask for the links to be removed. It's the recommended first option because it actually fixes the problem at the root instead of just asking Google to ignore it; in practice it works mainly with legitimate sites that have also been victimized (a hacked forum that doesn't know it's serving as a spam platform), not with PBNs built specifically to attack, where nobody is going to reply.

Third, check Search Console for any notified manual action. This is checked in the Manual Actions section inside Search Console: if there's no active notification, in most cases there's nothing urgent to fix beyond continuing to monitor, however alarming the link spike may look at first sight.

Only then, as a last resort and never as a first step, should disavowing be considered. The list should be well bounded: prefer domain: over individual URLs when the spam pattern is domain-wide (the most common case in real link-farm or PBN attacks), review every entry at least twice before uploading the file, and avoid the temptation to add domains "just in case" that haven't actually been verified as part of the attack.

Preventive protection

Beyond reacting to an attack already under way, there are reasonable preventive measures. The first is avoiding publicly exposing sensitive internal linking structures or SEO reports that reveal which pages you consider most valuable, because that same information you use to prioritize your own strategy is exactly what an attacker would use to decide where to strike most precisely.

The second is watching the site itself with security alerts, for the specific case of a hack injecting links: file integrity monitoring services, alerts for unexpected changes in code or in the database, and periodic reviews of Search Console's own outgoing links report, which is sometimes the first visible sign that the site is serving links nobody on the team put there.

The third, and the one most often overlooked, is the importance of not attacking yourself by mistake. There have been real cases of "aggressive" audits that, through poor handling of the disavow file or by confusing one's own domain with the target's, ended up disavowing legitimate links on the auditor's own site. Carefully reviewing every line of the file before uploading it, and remembering that the tool acts on your own domain in Search Console (not the competitor's), avoids this mistake, which is as avoidable as it is common.

Frequently asked questions

Can a competitor sink my site with links alone?

In the vast majority of cases, no. Penguin, part of Google's core algorithm since 2016, is specifically designed to detect manipulative link profiles and devalue or ignore them when calculating authority, not to actively penalize the site receiving them. A competitor can spend money and time on a link farm without your rankings being affected at all.

When should you use the Disavow Tool, and when is it better not to touch anything?

Google recommends using it only in the face of a real manual action notified in Search Console for unnatural links, or a reasonable certainty (not a suspicion) of large-scale active manipulation. Outside those two scenarios, the safest option is to leave it alone: the risk of mistakenly disavowing legitimate links and losing real authority is greater than the benefit of "cleaning up" links Google is probably already ignoring on its own.

How do I know if I've received a manual action for links?

It's checked directly in Search Console, under the Manual Actions section. If Google has detected and acted on an unnatural-links problem affecting your site, an explicit notification appears there, with details about the type of issue. If that section is empty, there's no active manual action, whatever the link report might show.

Does scraped content from my site hurt me in SEO?

Usually not directly: Google is generally good at identifying the original source versus a copy, especially if your content was indexed first and keeps its own authorship and authority signals. Aggressive scraping can create brand noise or siphon off traffic in markets where your original site has no presence, but it rarely causes a ranking drop on your original page.

Is it worth hiring a preventive link audit even if I haven't noticed any problem?

For most sites, a reasonable periodic review of Search Console's link report is enough, and it's free. A deeper audit with tools like Ahrefs, Semrush or Majestic makes more sense for sites with a lot of visibility, aggressive competition in their industry, or a real history of having suffered something similar, not as a generic measure for any small site with no prior warning signs.

Want to talk about technical SEO for your site?

Tell us about your project and we'll tell you how we can help, no strings attached.

Call 91 060 30 90