Summary of an article published on The Web Scraping Club on 2026-03-08 (free to read). Read the full article

On December 19, 2025, Google sued SerpApi in the Northern District of California. It did not use the CFAA, which hiQ v. LinkedIn weakened for public data. It used DMCA Section 1201, the anti-circumvention provision written with DVD encryption in mind. The target is SearchGuard, Google’s JavaScript challenge system, treated as a technological protection measure. For anyone who solves CAPTCHAs, runs JavaScript or rotates IPs to get past bot detection, the legal theory matters as much as the technical one.

We read the complaint and related filings, and we asked both parties for comment. Google did not answer. SerpApi did, and we quote it where relevant. We walk through Google’s argument chain and the statutory damages it implies, and SerpApi’s motion to dismiss. We then place the case next to Reddit’s complaint against SerpApi, Perplexity, Oxylabs and AWMProxy, and the Ziff Davis v. OpenAI ruling on robots.txt. We also cover the AI angle and the court dates ahead. We are not lawyers, and we say so.

What’s inside

  • Why Google skipped the CFAA after hiQ and how the two subsections of Section 1201 fit its argument.
  • How statutory damages per circumvention scale into figures far above SerpApi’s reported revenue.
  • Why the Ziff Davis ruling on robots.txt does not settle whether an active system like SearchGuard “effectively controls access”.
  • The Lexmark “front door/back door” argument and the so-called “DMCA 1201 scraping strategy” of deploy, document, sue.

In the full article: The full quotes from SerpApi, the detail of Reddit’s complaint and its hidden test post, the expert commentary from Eric Goldman’s blog and the EFF, the AI competition analysis and the court calendar for the case.

Read the full article on The Web Scraping Club