Google’s lawsuit against SerpApi is about whether bypassing a bot-detection system can violate the DMCA—not whether all web scraping is illegal. On July 20, 2026, a federal court dismissed Google’s two DMCA claims: claims involving noncopyrighted search-result material were permanently dismissed, while claims involving licensed copyrighted material could be amended. The court reportedly found Google had plausibly alleged circumvention, but had not adequately alleged that copyright owners authorized SearchGuard to control access to their works. The ruling is a significant setback for Google’s claims, not a blanket legal clearance for SERP APIs or scraping.
What is SearchGuard?
SearchGuard is the name Google used in its complaint for a technological measure intended to restrict automated access to Google Search pages and copyrighted material displayed in results. The complaint characterizes it as a protection for search-result pages and licensed content. SerpApi disputed that framing, describing SearchGuard as a domain-level anti-bot measure triggered by suspected automated traffic, rather than a copyright-specific access control. The court’s reported ruling did not establish that SearchGuard is encryption, a login system, or a paywall.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Cybersecurity Law | $33.00 | Buy on Amazon |
| 2 |
|
Cybersecurity Law | $78.28 | Buy on Amazon |
| 3 |
|
Cybersecurity Law | $129.00 | Buy on Amazon |
| 4 |
|
THE ENCYCLOPEDIA OF GLOBAL CYBERSECURITY LAW AND DIGITAL GOVERNANCE: A Comprehensive Reference for... | $38.43 | Buy on Amazon |
| 5 |
|
Cybersecurity in Context: Technology, Policy, and Law | $84.95 | Buy on Amazon |
That distinction matters because Google brought claims under the Digital Millennium Copyright Act (DMCA), which addresses circumvention of certain technological measures protecting copyrighted works. Whether a system blocks bots is not, by itself, the same question as whether it controls access to copyrighted works in the way the DMCA requires.
What do Google and SerpApi do?
Google’s claim about its search results
Google operates Search and other search products that can display material owned by third parties, including licensed images. In its complaint, Google said SearchGuard restricted access to search-result pages and copyrighted content appearing within them. The complaint is Google’s account of its rights and the system; SerpApi challenged how far Google’s licenses and authority extend.
#1 Best Overall
SerpApi’s service
SerpApi sells APIs that return structured search results to customers. Google described the service as automatically accessing and appropriating Google results for resale. SerpApi said it provides programmatic access to information visible in an ordinary browser, does not bypass authentication or enter private accounts, and does not claim ownership of the underlying material. Those are SerpApi’s litigation and public statements, not findings that settle the legality of every customer’s use.
Developers and businesses use SERP data for ranking checks, local-search monitoring, competitor research, keyword analysis, advertising intelligence, content research, and AI-visibility tracking. The dispute therefore concerns more than one vendor: it could affect the collection, supply, and commercial use of search-result data.
What did Google allege?
Google filed suit against SerpApi, LLC, in the U.S. District Court for the Northern District of California on December 19, 2025. The complaint alleged that SerpApi submitted Google queries at very large scale, used evasions and misrepresentations to get around SearchGuard, accessed results containing licensed copyrighted material, and resold or redistributed data through its API.
Google relied on two provisions of DMCA Section 1201: subsection (a)(1), which addresses circumvention, and subsection (a)(2), which addresses trafficking in technology or services alleged to enable circumvention. These were allegations in a civil complaint, not facts established after trial.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #2
Google’s complaint sets out its claims. The case number shown on SerpApi’s motion is 4:25-cv-10826-YGR.
How did SerpApi respond?
In a motion to dismiss filed February 20, 2026, SerpApi argued that the DMCA is not a general anti-scraping law and that SearchGuard was a traffic-management measure, not a copyright access control. It said Google had not alleged the kind of technical lock-breaking conduct the statute requires, such as defeating encryption or authentication, and argued that its conduct involved browser-like access and distributing results.
SerpApi also argued that much of the information was publicly visible, that Google did not own or exclusively license every item in results, and that Google had not adequately pleaded that copyright owners authorized it to use SearchGuard to control access to their works. These were arguments for dismissal, not findings the court adopted wholesale. The filing is available as SerpApi’s motion to dismiss.
SerpApi’s broader policy argument is that Google itself systematically accesses and organizes information across the web while challenging automated access to its own results. That symmetry point is part of SerpApi’s position; it does not by itself establish a legal defense or excuse conduct the law otherwise prohibits.
Rank #3
What did the court decide in July 2026?
Reporting on the July 20, 2026 ruling describes a divided result. The court dismissed both DMCA claims, but the treatment differed depending on whether the results at issue contained copyrighted material.
| Issue | Reported result |
|---|---|
| Search-result material without copyrighted content | Claims permanently dismissed; Google could not amend those portions. |
| Results containing licensed copyrighted material | Claims dismissed, with an opportunity for Google to amend. |
| Alleged circumvention of SearchGuard | The court reportedly found Google had alleged enough to support an inference of circumvention at this stage; that is not a final finding after trial. |
| SerpApi’s categorical argument that Google lacked standing | The court reportedly rejected the argument that Google necessarily lacked DMCA standing simply because it did not own or exclusively license every item in search results. |
| Copyright-owner authorization | The complaint did not adequately allege that relevant copyright owners authorized SearchGuard to function as an access-control measure for their works. |
The pivotal pleading problem was therefore not simply whether Google had a bot barrier or whether SerpApi’s alleged technical conduct could amount to circumvention. The issue, as reported, was whether Google adequately connected that measure to authority from the owners of the copyrighted works it sought to protect under the DMCA.
Search Engine Land’s account of the ruling reported that Google had 21 days to amend the surviving portion of its case. Bloomberg Law’s summary also describes the authority issue. The reported dismissal is not proof that the entire dispute has ended; an amended complaint, later order, or appeal could change the case’s status.
Why did copyright-owner authorization matter?
Google’s complaint described licensed third-party content, including images shown in features such as Knowledge Panels, Maps, and Shopping. SerpApi argued that a license to display material does not necessarily give Google authority to control downstream access, copying, or distribution of the work. The court’s reported focus was whether Google had pleaded facts showing that copyright owners authorized SearchGuard to control access to their works—not merely whether Google had installed a measure that blocked automated traffic.
This is a narrower question than whether Google can manage traffic to its site. It is also distinct from whether a particular customer’s copying or reuse of an image violates copyright. The dismissal addressed Google’s pleaded DMCA claims and their stated basis; it did not decide every possible claim involving the underlying works.
Does the ruling make scraping Google legal?
No. The ruling is not a general declaration that scraping is legal, that public information is unrestricted, or that Google cannot block automated traffic. It concerns Google’s DMCA claims in this case and the sufficiency of the allegations supporting them. Other laws, contracts, rights, and jurisdictions may produce different results.
- Terms and contracts: Website terms or an API contract may impose obligations independent of the DMCA ruling.
- Computer-access laws: Questions about authorization and access can depend on the conduct and applicable statute.
- Copyright: Copying material Google owns or controls, or reusing third-party material, raises issues distinct from the claims dismissed here.
- Privacy and other rights: Personal data, confidential information, database rights, and unfair-competition rules may matter depending on the data and jurisdiction.
- Operational controls: Google or a provider can block requests, apply rate limits, suspend accounts, or end service even when a particular legal claim has not been established.
It would also be inaccurate to say the court found that SerpApi did not circumvent SearchGuard. The reported decision found Google’s circumvention allegations sufficiently pleaded while dismissing the claims on another legal pleading issue. Nor does the ruling settle the law for all scraping, AI training, or automated access.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What could the case mean for SEO, AI, and data businesses?
Rank trackers and other SEO tools depend on search data to monitor rankings, local results, competitors, and advertising. AI products and researchers may also use SERP data for visibility analysis, evaluation, or other research. The case could influence vendors’ collection methods, customer contracts, pricing, data retention, and fallback plans, but its commercial effects are not yet a settled legal outcome.
For buyers, the important distinction is between a provider’s ability to return Google results and the legal and contractual basis for doing so. A provider’s assurance that it can bypass anti-bot measures does not create a safe harbor for the provider or its customers.
How should a business assess a SERP-data provider?
Check provenance and terms
- Ask whether each endpoint uses an official API, licensed feed, direct scraping, or a mix; do not assume one answer applies to every product.
- Review the provider’s stated compliance posture, acceptable-use terms, handling of anti-bot systems, and any customer-use restrictions.
- Check whether your intended use permits caching, retention, redistribution, resale, and use across regions.
- Review what contractual assurances or indemnities are actually offered, and what they exclude. A vendor’s compliance language is not a court ruling.
Test whether the data fits the use case
- Verify location, language, device, and personalization controls, especially for local rank tracking.
- Check coverage for the specific features you need, such as Maps, Shopping, News, Images, or AI Overviews.
- Measure structured-data quality, freshness, latency, duplicate handling, and failure rates under your workload.
- Confirm whether historical results are available or whether the service returns only live queries.
Model the total cost and continuity risk
- Find out whether billing is based on requests, searches, records, credits, or another unit, and whether failed requests are charged.
- Compare concurrency limits, overage rates, minimum commitments, and charges for geographic targeting or rendering.
- Ask what happens if a search engine changes its layout or anti-automation controls, or a provider loses access to a vertical.
- Plan for vendor changes: unstable results, schema changes, or dependence on one provider can make a low headline price costly in practice.
For enterprise or high-volume commercial use, provenance, permitted uses, customer indemnity, continuity plans, and legal review may matter more than headline request pricing. Official Google APIs, licensed search-data feeds, and narrower first-party products may cover some needs; a hybrid approach can combine those sources with third-party data where appropriate. The relevant option depends on what data is actually available through each channel.
Case timeline and status
- December 19, 2025: Google filed suit against SerpApi in the Northern District of California.
- February 20, 2026: SerpApi filed its motion to dismiss.
- July 20, 2026: The court dismissed Google’s DMCA claims, with different outcomes for noncopyrighted and licensed copyrighted material.
- As reported July 22, 2026: Google had 21 days to amend the claims concerning licensed copyrighted material.
The case’s subsequent status is not established by those reported dates. Whether Google amended its complaint or pursued further proceedings must be checked against the current court docket.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
