Someone Used a Fake Copyright Claim to Remove a Search Engine Land Article from Google

Within 24 hours of publishing an investigation into AI-generated gambling content on hijacked news domains, Search Engine Land had the article removed from Google's search results. Not because of a Google penalty. Not because of a content policy violation. Because someone filed a copyright complaint claiming the article stole their content, word for word.

The complaint was false. The article contained no images, despite the filing claiming "unlawful use of proprietary images." Text analysis showed no copied content. The filer identified themselves only as "US Webspam," with no verifiable identity. And the most telling detail: they claimed "multiple good-faith efforts" to resolve the matter before filing. No such contact had ever been made.

This isn't a quirky anecdote about one bad DMCA filing. It's a pattern. And it has real implications for anyone who publishes content that someone else would prefer didn't exist in Google's index.

The same playbook, used twice in the same week

The Search Engine Land article being targeted was a report on Press Gazette's investigation into Clickout Media, a company allegedly turning expired or acquired news domains into AI-generated gambling hubs. Press Gazette published their original investigation first. Then Search Engine Land covered it.

Both publications got hit with nearly identical DMCA takedown requests. Press Gazette's complaint falsely claimed infringement of a 2024 article from The Verge. Search Engine Land's complaint claimed wholesale content theft from a source that doesn't appear to exist in any meaningful way.

Two different publications. Two separate copyright complaints. Same target story. Same playbook. Both filed within days of publication, before either piece had time to gain significant search visibility. The timing alone makes the intent fairly transparent.

Why this works so well for bad actors

Google's DMCA process follows the standard notice-and-takedown framework required by law. When Google receives a copyright complaint that meets the basic formal requirements, it removes the accused content from search results. The content owner can file a counter-notification, but the process takes time. Google's own documentation suggests a 10 to 14 business day window before content can be restored after a counter-notice.

That gap is the weapon. A bad actor doesn't need the complaint to be valid. They just need it to be filed. For roughly two weeks, the targeted content disappears from Google while the process plays out. For a news article that depends on search visibility in its first few days, two weeks might as well be permanent. The news cycle has moved on. The damage is done.

The barrier to filing is remarkably low. You need a name (which can be fake, apparently), an assertion of ownership, and the URLs you want removed. There's no meaningful verification step before the takedown happens. Google checks that the form is filled out correctly. They don't check whether the claim is true.

I think most publishers assume this couldn't happen to them because they don't steal content. That assumption misses the point entirely. The complaint doesn't need to be accurate. It needs to exist.

Competitive suppression, not copyright enforcement

False DMCA claims have been around for years, and they've always been a problem at some level. What's changing is who's using them and why. This isn't someone filing a bogus complaint over a personal grudge. This is coordinated suppression of investigative journalism that threatens a specific business operation.

The Clickout Media investigation was documenting alleged site reputation abuse, one of Google's stated targets in recent spam policy updates. The articles being removed were essentially doing Google's enforcement work for them, identifying the exact kind of abuse Google says it's trying to stop. And the current DMCA process let someone suppress that work using Google's own compliance machinery.

There's something uncomfortable about that dynamic, and I don't think Google has fully reckoned with it yet. The DMCA system was designed to protect copyright holders from actual infringement. Using it to silence journalism about spam operations is a corruption of the mechanism's intent. But the mechanism doesn't distinguish between the two use cases. A form is a form.

For anyone whose business depends on content visibility in search, and that probably includes everyone reading this, the idea that a competitor or bad actor could remove your content from Google for two weeks with a fake form should be concerning. Especially if your content happens to be critical of someone with the resources and motivation to file one.

Your defense is speed, not prevention

The honest answer is that there's no way to prevent a false DMCA filing. Anyone can submit one at any time targeting any URL. But you can reduce your response time and build a paper trail that makes counter-notifications faster and more effective.

First, set up Google Search Console alerts and check them regularly. If a page gets removed due to a DMCA complaint, you'll see it flagged. The sooner you know about it, the sooner you can respond. Days matter here.

Second, familiarize yourself with the counter-notification process before you need it. When you're dealing with a live takedown, you don't want to be reading the documentation for the first time. Google's counter-notice form requires specific legal language, and mistakes or omissions can delay reinstatement.

Third, consider registering your content with the U.S. Copyright Office for high-value pages. Registered copyrights create a stronger legal foundation for counter-notifications and make it harder for frivolous claims to stick. It costs $65 per registration and takes a few weeks to process. Not practical for every blog post, obviously. But for cornerstone content that drives significant organic traffic, it's worth the investment.

Fourth, and this is the one that seems to work best in practice: document your content creation process. Timestamps on drafts, editorial notes, version history in your CMS. If you ever need to prove that your content is original (and given this trend, that "if" is becoming "when"), having a documented chain of creation is the fastest way to resolve a dispute.

The enforcement gap Google probably needs to close

Google publishes a transparency report on DMCA requests. In recent years, they've processed billions of URL removal requests. At that volume, meaningful human verification of every claim is impossible. Google knows this. Everyone in the industry knows this.

But there's a difference between "we can't verify every claim" and "we can't flag claims that are obviously fraudulent." A complaint filed by an entity called "US Webspam" with no verifiable contact information, targeting a news article published 24 hours earlier, citing stolen images that don't exist in the article... that should trigger some kind of automated fraud signal. It didn't.

Search Engine Land eventually got their article reinstated after reaching out to Google directly. Press Gazette did the same. But both publications have the industry visibility and connections to escalate quickly. A smaller publisher, an independent blogger, a niche site covering a topic someone wants suppressed, they might not have that access. For them, two weeks of lost search visibility on a time-sensitive article is effectively a kill shot to that content's organic potential.

Google's DMCA process has quietly become a tool for the people it was designed to protect against. Until there's some kind of meaningful friction for complaints that meet obvious fraud signals, a basic automated check for impossible claims, a brief verification delay for first-time filers, something, it will keep happening. The targets will just get smaller and quieter each time.