Tag: SerpAPI

SerpApi Challenges Reddit’s Allegations in Court Showdown

In a bold move, I’m witnessing firsthand how SerpApi is requesting a federal court to dismiss Reddit’s lawsuit. This legal battle centers around the alleged scraping of Reddit content from Google Search. From my perspective, SerpApi argues that Reddit is using copyright law to exert control over user posts and public search results.

Reddit’s initial complaint was amended in February, but I noticed that SerpApi remains firm. They argue that Reddit has not adequately demonstrated copyright ownership, technical circumvention, or tangible harm resulting from these actions.

SerpApi’s argument. From a blog post by SerpApi CEO Julien Khaleghy, I gather that the lawsuit is flawed for several reasons:

Reddit, interestingly enough, does not own the majority of the content in question, as user agreements clearly state that content ownership resides with the users themselves. It’s fascinating to see that Reddit only has a non-exclusive license to these posts.

The snippets Reddit presented, including dates and short fragments, don’t appear to be copyrightable at all from what I’ve read in the claims.

SerpApi’s stance is that they accessed Google Search pages, not directly interfacing with Reddit’s platform, which I believe weakens Reddit’s argument substantially.

DMCA concerns. In what I find a compelling argument, Khaleghy asserts that Reddit’s claim of a Digital Millennium Copyright Act (DMCA) violation lacks merit. SerpApi contends that their actions parallel what any user might see when conducting a Google search. Khaleghy strongly points out that:

There’s no evidence of encryption breaches or authentication bypass by SerpApi.

Accessing publicly available web pages doesn’t constitute “circumvention” under existing DMCA guidelines.

Reddit seems to be attempting to enforce copyright claims over content that doesn’t belong to them, which is an intriguing angle to this case.

Moreover, Reddit’s privacy policy acknowledges that public posts may surface in search results, supporting SerpApi’s use of the data.

Backstory. It’s clear to me that legal conflicts surrounding search scraping and AI data have gained high stakes lately:

Oct. 22: I came across information about Reddit filing lawsuits against SerpApi, Perplexity, Oxylabs, and AWMProxy, claiming they scraped large amounts of Reddit content through Google Search, referring to a decoy post created solely for Google’s crawler.

Oct. 29: SerpApi’s response, branding Reddit’s allegations as inflammatory, was a critical move, showcasing their resolve to defend access to public search data.

Dec. 19: Further intensifying the narrative, Google filed a lawsuit against SerpApi, accusing them of bypassing bot protections to scrape licensed search functionalities.

Feb. 23: SerpApi retaliated by requesting the court to dismiss the lawsuit filed by Google, arguing that Google is inappropriately leveraging the DMCA to limit access to public search results.

Importance. This case captivates me as it explores whether companies can legally extract information from Google’s search results without infringing on copyright laws or the DMCA, potentially impacting SEO tools and AI data training significantly.

Looking forward. I eagerly await the court’s decision on whether Reddit’s amended complaint holds up. A dismissal with prejudice would put an end to Reddit’s claims against SerpApi in this instance, which could send ripples through the industry.

SerpApi’s blog post. Check out Reddit’s Lawsuit is a Dangerous Attempt to Expand Platform Power for more on SerpApi’s perspective.

Inspired by this post on Search Engine Land.

March 13, 2026
SerpApi’s Legal Battle: Challenging Google’s Scraping Lawsuit

When I first learned about SerpApi’s move to dismiss Google’s lawsuit, my immediate thought was about the bold challenge SerpApi is undertaking. They’re arguing that Google is twisting copyright laws to restrict access to public search results all to protect their ad revenue, not copyrights.

The motion to dismiss was officially filed on February 20th, as mentioned in a recent blog post by SerpApi’s CEO, Julien Khaleghy. This legal battle stems from Google’s accusation in December that SerpApi bypassed security measures to scrape and resell content from Google Search.

The details: According to Khaleghy, Google is improperly applying the Digital Millennium Copyright Act (DMCA). Here’s what I found compelling:

The DMCA is meant to protect copyrighted works, not online platforms or advertising ventures. In addition, Google doesn’t actually own the content that appears in its search results, and accessing publicly available pages doesn’t qualify as “circumvention” under this law, SerpApi argues.

Google claims that SerpApi managed to evade bot-detection and crawling controls using rotating bot identities and large networks to scrape licensed content from features such as images and real-time data. However, SerpApi insists that they do not decrypt systems or breach authentication protocols, and merely gather the same data any user could see via a browser, without needing to log in.

Khaleghy also points out Google’s admission that its anti-bot systems primarily secure its advertising interests, which weakens the DMCA claim against SerpApi.

SerpApi references significant legal precedents, including the Ninth Circuit’s hiQ v. LinkedIn, which cautions against monopolizing public data, and the Sixth Circuit’s Impression Products v. Lexmark, reinforcing that public-facing content shouldn’t be blocked by merely technical measures.

Catch up quick: This lawsuit is the latest in a series of escalating legal clashes over data scraping and AI usage:

Back in October 2022, Reddit filed suits against SerpApi, among others, alleging they indirectly scraped content from Google Search. Reddit claims these companies obscured their identities and operated at an “industrial scale.” In turn, SerpApi has vowed to robustly defend itself, emphasizing that public data should remain accessible.

By December, Google further escalated the legal situation by suing SerpApi for ignoring its security measures and attempting to resell protected content. SerpApi stands firm, citing lawful operation and First Amendment rights to access public search data.

By the numbers: If Google’s interpretation of the DMCA holds, SerpApi suggests potential damages could skyrocket to $7.06 trillion — more than the entire U.S. GDP. However, this staggering figure is a theoretical estimate based on potential penalties, not an actual demand.

What’s next: It all boils down to the court’s decision on whether Google’s claims should move forward. Depending on the outcome, this case could significantly impact how SEO platforms, AI tools, and competitive intelligence software access search results data in the future.

A triumph for Google might hinder third-party access to search data, while a victory for SerpApi could reinforce that publicly accessible search outcomes are indeed fair game.

For deeper insights, I recommend reading Google v. SerpApi: We’re filing a Motion to Dismiss. Here’s why we’re in the right.

Don’t miss Inside SearchGuard: How Google detects bots and what the SerpAPI lawsuit reveals for in-depth analysis.

Inspired by this post on Search Engine Land.

February 23, 2026
Inside Google SearchGuard: Decoding Bot Detection Secrets
I recently explored Google’s SearchGuard, an advanced system that safeguards Google Search from bots. This groundbreaking technology has been thrust into the limelight due to a lawsuit against SerpAPI, revealing how Google differentiates between human users and automated scripts.

After meticulously dissecting the JavaScript code, I gained rare insights into how Google distinguishes humans from automated scrapers in real-time.

What happened: On December 19, Google filed a lawsuit against SerpAPI, accusing them of bypassing SearchGuard to extract copyrighted data from Google Search results on a colossal scale. Instead of focusing on terms-of-service breaches, Google cited DMCA Section 1201, emphasizing anti-circumvention clauses.

This case underscores what Google deems worth protecting, which is crucial for anyone in the SEO and marketing sectors who might be using tools that interact with Google Search.

Why we care: Understanding SearchGuard is vital because any large-scale automation with Google Search invokes this system. If you’re using scraping tools, this is the barrier they encounter.

Here’s where it gets interesting: SerpAPI isn’t just another scraper. OpenAI utilized Google search results, obtained through SerpAPI, to enhance ChatGPT’s capabilities. Although OpenAI’s request for direct access to Google’s index was flatly denied in 2024, they still needed real-time data.

This situation highlights a strategic move by Google, focusing on a key element in the competition’s data supply chain.

In investigating SearchGuard, I fully decrypted version 41 of the BotGuard script, which started with an unexpected greeting:
```
Anti-spam. Want to say hello? Contact botguard-contact@google.com
```
Don’t let the friendly tone fool you; behind it lies one of the most complex bot detection systems ever created.

BotGuard vs. SearchGuard: BotGuard, internally termed Web Application Attestation (WAA), shields most Google services. Google’s legal complaint disclosed that the specific system guarding Search is known as SearchGuard, which when implemented in early 2025, disrupted nearly all SERP scrapers.

Unlike traditional CAPTCHAs, BotGuard operates invisibly, seamlessly analyzing user behavior using sophisticated algorithms to separate bots from people.

It leverages a highly protected bytecode virtual machine to ensure it remains impervious to reverse engineering.

How Google knows you’re human: The system evaluates multiple behavioral metrics in real-time, including mouse movements, keyboard rhythm, scroll behavior, and timing jitter, painting a comprehensive picture of a user’s natural interactions.

Mouse movements

Google observes the fluidity of mouse motions, capturing deviations that indicate a human touch, unlike the straight paths typical of bots.
- Path shape
- Speed
- Acceleration changes
- Micro-tremors
A perfectly linear mouse action raises alarms, as it is atypical of human movement, usually characterized by imperfections.

Keyboard rhythm: Everyone types differently. Google captures inter-keystroke intervals, error patterns, and post-punctuation pauses to form a user’s unique typing ‘fingerprint.’
- Time between keys
- Keypress duration
- Error sequences
- Pauses after punctuation
The aspects of natural scrolling and timing jitter are also scrutinized, as context-specific nuances help discern human from machine.

Google’s system even enlists over 100 HTML elements for browser environment fingerprinting to further ensure authenticity.

Performance monitoring: Google captures intricate details such as navigator properties, screen metrics, and engagement with browser APIs for an exhaustive analysis.

Despite efforts to outsmart it, SearchGuard employs cryptographic measures similar to those developed by the NSA to protect its integrity, making circumvention fleeting at best.

The statistical ingenuity behind SearchGuard: Algorithms like Welford’s and reservoir sampling give SearchGuard the upper hand, continuously refreshing a composite profile of expected user behavior.

SerpAPI’s stance: Julien Khaleghy, CEO of SerpAPI, notes Google never reached out before filing the lawsuit, suggesting it’s an attempt to stifle competition from innovative services using their platform to power advanced applications.

Google’s assertiveness poses a monumental challenge to the SEO industry, redefining how anti-scraping measures might be perceived legally. Should SearchGuard be recognized as a legitimate protective measure under DMCA, it could set significant precedent.

Inspired by this post on Search Engine Land.
January 19, 2026