Google Files DMCA Suit Over SerpApi’s SERP Scraping

Google has filed a DMCA lawsuit over SerpApi’s SERP scraping, alleging circumvention of anti-scraping protections and misuse of search data.

Google has launched a DMCA lawsuit against SerpApi, accusing the Texas-based API provider of unlawfully scraping and reselling Google Search results at industrial scale. At the heart of the case is Google’s argument that SerpApi bypassed a new anti-scraping system called SearchGuard to access licensed, copyrighted content embedded in search features.​

A DMCA Case, Not Just A Terms-of-Service Fight

What makes this lawsuit stand out is Google’s choice of legal weapon. Instead of centering the complaint on terms-of-service breaches or generic bot scraping, Google is leaning on the Digital Millennium Copyright Act (DMCA) specifically its anti-circumvention provisions.​

In court filings, Google describes SearchGuard as a “technological measure” that controls access to Search results pages and the copyrighted works they contain.

The system issues a JavaScript “challenge” to unfamiliar traffic and requires specific data to be returned as a “solve” before granting access. Google says it rolled out SearchGuard in January 2025, initially blocking SerpApi’s automated requests, after which SerpApi allegedly engineered ways around it.​

As Google puts it in the complaint:

“Google developed and deployed a technological measure, known as SearchGuard, that restricts access to its search results pages and the copyrighted content they contain. So that it could continue its free riding, however, SerpApi developed a means of circumventing SearchGuard. With the automated queries it submits, SerpApi engages in a wide variety of misrepresentations and evasions in order to bypass the technological protections Google deployed. But each time it employs these artifices, SerpApi violates federal law.”

DMCA Section 1201: Circumvention And “Trafficking”

Google’s complaint relies heavily on DMCA Section 1201, which governs both the act of bypassing access controls and the provision of tools or services that help others do so.​

The suit brings two main claims:

• One under Section 1201(a)(1), targeting the alleged circumvention of SearchGuard itself.
• Another under Section 1201(a)(2), accusing SerpApi of “trafficking” in a circumvention service by selling access to scraped Google results.​

Google notes that statutory damages could range from $200 to $2,500 per violation, and while it acknowledges reports that SerpApi generates “a few million dollars” in annual revenue, the company is clearly prioritising an injunction to halt the conduct over simply collecting money.

That emphasis on injunctive relief is important for anyone whose tools depend on third-party SERP data.​

Google’s Allegations: Fake Browsers, Massive Volume

According to the complaint, SerpApi allegedly developed a suite of techniques to get around SearchGuard, including:​

• Misrepresenting device, software, or location details to appear as legitimate users.
• Re-using or syndicating valid authorisations across large networks of machines.
• Deploying what SerpApi’s founder is quoted as calling:

The complaint quotes SerpApi’s founder describing the process as:

“creating fake browsers using a multitude of IP addresses that Google sees as normal users.”

Google estimates that SerpApi now sends “hundreds of millions” of automated search requests per day, and says that scraping volume has increased by as much as 25,000% over the past two years.

From Google’s perspective, this is no longer “light scraping” but industrial-scale replication and resale of its search interface and the content it aggregates.​

Licensed Content, Not Just Raw SERP Data

A key angle in Google’s narrative is that this isn’t only about snippets and blue links. The complaint emphasises that Search results frequently embed licensed assets from third parties and that these are part of what SerpApi is allegedly capturing and reselling.​

Examples cited include:

• Knowledge Panels containing copyrighted photographs licensed from external providers.
• Shopping results that display merchant-supplied product images.
• Maps and local features that incorporate third-party imagery.​

Google argues that SerpApi “scrape[s] this copyrighted content and more from Google” and then charges customers for access, without authorisation from either Google or the original rights holders. That framing is deliberate: it positions the case as defending not only Google’s platform, but also the underlying content ecosystem.​

Why SEO And Data Teams Should Pay Attention

For the SEO, martech, and analytics ecosystem, this isn’t just a legal curiosity it has potential operational consequences. If your workflows rely on third-party SERP APIs for rank tracking, SERP feature monitoring, or competitive visibility, this suit is worth watching closely.​

• Larger platforms typically operate their own collection infrastructure and may be less directly exposed.
• Smaller SaaS tools, internal dashboards, and custom scripts are much more likely to depend on external providers like SerpApi.

If a court issues the kind of injunction Google is asking for, including shutting down circumvention methods and destroying related technology, it could cut off a key data supply chain overnight.

In practical terms, teams may need to diversify their data sources or explore compliant, first‑party integrations to reduce single‑point‑of‑failure risk.​

A Broader Pattern: Scraping, AI, And Platform Control

This suit doesn’t exist in isolation. It follows a wave of litigation around web scraping, content reuse, and AI training data.​

• Reddit sued SerpApi and others in October, alleging they scraped Reddit content at scale sometimes in connection with AI startup Perplexity via Google Search.​
• Google’s own case notably does not mention Perplexity, focusing solely on SerpApi’s alleged circumvention of SearchGuard and resale of copyrighted content.​

All of this lands in the shadow of U.S. search antitrust proceedings, where Judge Amit Mehta’s 2024 liability ruling and subsequent remedies probe how much power Google can exert over defaults and distribution.

Industry Reactions

Some commentators on X have reacted through the post calling it “the end of ChatGPT” or a death blow to AI products that depend on downstream SERP access. Understandably, there’s genuine anxiety about data pipelines becoming legally fragile. But the actual filing is narrower than some of the social-media rhetoric.​

Google’s claim is specifically about:

• Circumventing SearchGuard (a defined technical control).
• Reselling copyrighted, licensed content embedded within Google Search.​

SerpApi, for its part, has said it will “vigorously defend” the case and frames Google’s move as an attempt to constrain competition from companies building “next-generation AI” and related applications on top of web-scale data.

That defence narrative taps into a broader concern: that copyright and anti-circumvention law could be deployed in ways that entrench incumbent data gatekeepers.​

What Happens Next

In terms of remedies, Google is asking the court for:​

• Monetary damages, including the option to elect statutory damages per violation.
• A permanent injunction barring SerpApi from any further circumvention.
• An order requiring SerpApi to destroy any technology, tools, or products used to bypass SearchGuard.

If the case advances, a central legal issue will be whether SearchGuard qualifies as a DMCA-protected “access control” for copyrighted works; in other words, a technological measure that “effectively controls access” within the meaning of Section 1201.​

SerpApi is likely to argue that SearchGuard functions more like a bot-management or rate-limiting system than a gate to specific copyrighted works, and that treating it as a DMCA access control would stretch the statute into general-purpose anti-scraping territory.

Bottom Line

The courts’ interpretation of that distinction is likely to extend well beyond this dispute, with significant consequences for SEO tools, analytics platforms, and AI products built on structured access to public-facing web interfaces.