TL;DR

Google's lawsuit against SerpApi — the one alleging that SerpApi's scraping of Google search results violated the DMCA — was dismissed on July 21, 2026. According to Bloomberg Law's reporting, the court granted SerpApi's motion to dismiss because Google failed to demonstrate it had the proper authority to bring (some of) its claims, described as an "authority issue." That is a procedural outcome, not a ruling that scraping search results is legal — the case never reached a decision on the actual merits. It's also one data point in a broader wave of 2026 scraping litigation that has touched Snap and Meta, among others, and that wave isn't over. For most people using a browser-based tool like ScrapeMaster, the sensible posture hasn't changed: stick to publicly visible data, don't circumvent access controls, and don't build a business on reselling someone else's proprietary database. This is general information, not legal advice.

Quick recap: how we got here

If you haven't been following this case, the short version, covered in more depth in our original case explainer and our May 19 hearing preview:

  • Google sued SerpApi, a company that sells structured access to Google search results through an API, alleging DMCA anti-circumvention violations — the theory being that SerpApi bypassed Google's anti-bot defenses (reported as "SearchGuard") to extract search results at massive scale.
  • SerpApi filed a motion to dismiss in February 2026, arguing (among other things) that Google hadn't shown concrete harm and that accessing publicly visible search results isn't "circumvention" in the DMCA sense.
  • A hearing on that motion was held May 19, 2026.
  • On July 21, 2026, the court granted the motion and dismissed the case.

We're not going to re-run the DMCA background or the server-side-vs-browser-based breakdown here — both of those earlier posts still hold up and are worth reading if you want the full context. This post is about what actually happened on July 21 and what it changes.

What "dismissed over an authority issue" actually means

"Authority issue" isn't legal boilerplate you see in every ruling, but the underlying idea is common enough. Courts don't just ask "is this conduct wrong?" — they first ask "is this the right plaintiff, bringing the right claim, in the right way, at the right time?" That's a gatekeeping question, separate from whether the underlying behavior (in this case, SerpApi's scraping) was actually lawful or unlawful.

According to Bloomberg Law's reporting, that's what happened here: Google didn't clear the bar of showing it had the proper authority to bring some of the claims in its complaint. Practically, think of it like this — if you tried to sue on behalf of a neighborhood association without actually being authorized to represent it, a court could throw the case out on that basis alone, without ever getting into whether the association had a legitimate grievance. The dismissal here is that kind of ruling: a bar Google didn't clear, not a verdict on the underlying scraping dispute.

A few things worth being precise about, since it's easy to overstate a headline like "Google's lawsuit against SerpApi dismissed":

  • We don't know the exact statutory or procedural basis beyond "authority issue" as described in reporting — we're not going to guess at the specific doctrine.
  • We don't know whether Google can or will appeal, or whether it plans to refile a narrower version of the claims. Nothing in current reporting addresses next steps, so we're not speculating.
  • We don't know case specifics like a judge's name or any monetary figures, and none of that has been reported in a way we can responsibly repeat here.

If you read one thing about this dismissal, read it as: this particular lawsuit, filed the way Google filed it, didn't clear a preliminary bar. That's a narrower statement than "a court ruled scraping Google is legal," and the difference matters for how much weight you should put on this outcome.

This is the part that's easy to get wrong if you only see the headline. A dismissal on a procedural or technical ground — like an authority issue — is fundamentally different from a ruling on the merits.

A merits ruling would mean the court actually evaluated the substance of Google's DMCA anti-circumvention theory: is a search results page copyrighted in the relevant sense, does an anti-bot system count as a "technological measure," and did SerpApi's methods amount to "circumvention" under the statute. That kind of ruling would set real precedent — it would tell every other company running a scraping operation, and every website trying to fend one off, how a court weighs those specific questions.

A procedural dismissal — what reportedly happened here — means the court never got that far. The case ended on a threshold question about whether Google was entitled to bring the claims as brought, not on whether SerpApi's scraping was ultimately lawful or unlawful. Nothing in this outcome establishes that bypassing anti-bot systems is fine, and nothing in it establishes that Google's underlying legal theory was wrong on the merits either. Both of those questions remain open.

Put another way: SerpApi won this round, but it won it on a technicality about how Google brought the case, not because a judge said scraping Google Search is legal. If Google refiles with the authority issue fixed — assuming that's even possible — the same substantive DMCA questions could come right back.

This distinction is exactly why our earlier coverage was careful to frame the DMCA angle as "novel and untested" rather than settled. It still is. This dismissal doesn't resolve the DMCA-anti-circumvention-for-scraping question one way or the other — it just means this particular lawsuit didn't answer it.

What it signals for the broader wave of scraping litigation

Zoom out, and this dismissal is one data point in a much larger pattern. As we covered in our roundup of the 2026 scraping lawsuit pile, Google v. SerpApi was never an isolated case — it sat alongside Reddit's suit against Perplexity, SerpApi, Oxylabs, and AWMProxy, and separate DMCA-scraping suits filed by YouTube creators against Snap and Meta. According to reporting, that broader wave of litigation is continuing to touch companies like Snap and Meta.

A single dismissal on procedural grounds doesn't deflate that wave. Each of those cases has its own plaintiff, its own claims, and its own procedural posture — an "authority issue" in Google's specific complaint doesn't automatically apply to Reddit's complaint against a different set of defendants, or to the YouTube creators' claims against Snap and Meta. If anything, the more interesting question going forward is whether other plaintiffs in this wave have shored up the kind of authority or standing gap that reportedly tripped up Google's case, or whether this becomes a cautionary tale about complaint-drafting that shows up in how future suits are filed.

What's more durable than any single ruling is the trend underneath all of it: large platforms are actively testing legal theories against server-side, anti-bot-bypassing scraping operations, and 2026 has produced more of these cases than any prior year. That pressure doesn't go away because one case got dismissed on a technicality.

What this means if you scrape data with a tool like ScrapeMaster

Here's the practical part. If you're using a browser-based tool to pull structured data off public pages — product listings, job postings, directory entries, competitor pricing — this dismissal doesn't change the calculus much, because the case was never squarely about you in the first place. It targeted a commercial API vendor running server-side infrastructure that allegedly rotated IPs and mimicked human behavior at massive scale to bypass Google's own anti-bot systems. That's a structurally different activity from opening a page in your own browser and reading what's already rendered on your screen.

The standard cautious posture we've recommended throughout this whole saga still applies, dismissal or no dismissal:

  • Stick to publicly visible data. If you can see it in your browser without logging in, or you're viewing it as an authenticated user with legitimate access, you're on much firmer ground than someone trying to reach data behind a wall they're not supposed to be behind.
  • Respect robots.txt and a site's Terms of Service where practical. Not always legally binding, but it's a real signal of good faith, and it's cheap to honor.
  • Don't circumvent technical access controls. CAPTCHAs, login walls, and rate limits exist for a reason. A tool that reads data you can already see is a fundamentally different animal from one built to defeat those measures.
  • Don't resell someone else's proprietary database wholesale. Extracting a handful of data points for your own research or workflow is different from standing up a commercial product that repackages and resells another company's structured dataset at scale. The latter is where litigation like this tends to start.

ScrapeMaster is built around that first posture. It runs inside your own Chrome browser session — there's no server infrastructure sending automated requests on your behalf, no IP rotation, no bypassing of anti-bot systems. Click the extension, let the AI auto-detect the columns on the page (no CSS selectors, no code), and it handles pagination and infinite scroll by capturing what's actually been scrolled or loaded in your session — not by hammering a server with synthetic requests. Export to CSV, XLSX, or JSON when you're done, or hook it up over MCP if you're feeding the data into an AI agent workflow. It doesn't do OCR, it doesn't process anything in the cloud (the scraping happens through your own browser), and it doesn't bypass paywalls or logins you don't already have legitimate access to.

None of that makes any specific use case bulletproof — that still depends on what you're collecting, from where, and what you do with it afterward. But it's a meaningfully different risk profile from the kind of infrastructure this entire wave of litigation has been aimed at.

Frequently asked questions

No. The case was dismissed over what's been described as an "authority issue" — a procedural question about whether Google had the standing or right to bring some of its claims as filed. The court did not rule on whether SerpApi's scraping methods were lawful or unlawful under the DMCA. That underlying question remains unresolved.

Can Google refile the lawsuit?

We don't know. Current reporting on the dismissal doesn't address whether Google plans to appeal, refile, or take any other next steps, so we're not going to speculate on that here. If new developments are reported, we'll cover them.

Does this dismissal affect the Reddit v. Perplexity, SerpApi, Oxylabs, and AWMProxy case?

Not directly. That's a separate lawsuit with a different plaintiff, different defendants, and its own claims and procedural history. An authority issue in Google's specific complaint against SerpApi doesn't automatically transfer to a different plaintiff's case, even though both cases are part of the same broader wave of 2026 scraping litigation.

This particular case against it was dismissed, but that's not the same as a clean bill of health across the board. Reporting indicates the broader wave of 2026 scraping litigation is continuing to touch other companies as well, including Snap and Meta. Vendors operating server-side scraping infrastructure at commercial scale remain a focus of ongoing legal attention industry-wide.

What's the difference between a dismissal and a win on the merits?

A dismissal on procedural or technical grounds — like an authority issue — means the case ended before a judge evaluated the substance of the dispute. A ruling on the merits means the court actually weighed the facts and legal theories and decided who was right. This dismissal was the former, not the latter, so it doesn't set the kind of precedent a merits ruling would.

Should I change how I use ScrapeMaster because of this news?

Not because of this specific ruling. The guidance hasn't changed: scrape publicly visible data, avoid circumventing technical access controls like CAPTCHAs or login walls, respect robots.txt and Terms of Service where practical, and don't repackage and resell someone else's proprietary database wholesale. This dismissal doesn't loosen or tighten that guidance — it's simply one procedural development in an ongoing legal story.

Where can I read more about the underlying case?

Our original explainer covers the DMCA anti-circumvention theory and how it compares to prior cases like hiQ v. LinkedIn. Our May 19 hearing preview covers what was actually argued in the motion to dismiss. For the general legal landscape around scraping, see our full guide to web scraping legality.

Bottom line

Google's lawsuit against SerpApi was dismissed on July 21, 2026, according to Bloomberg Law's reporting, because Google reportedly failed to demonstrate it had the proper authority to bring some of its claims. That's a real, newsworthy outcome — but it's a procedural win for SerpApi, not a court declaring that scraping Google's search results is legal. The substantive DMCA question this case raised is still open, and the broader 2026 wave of scraping litigation touching companies like Snap and Meta hasn't slowed down because of it.

For anyone using a browser-based tool for everyday data collection, none of that changes the fundamentals: scrape what's publicly visible, respect access controls, and don't turn someone else's database into your product. ScrapeMaster is built for exactly that posture — it runs in your own browser session, auto-detects data with AI so you never touch a CSS selector, handles pagination and infinite scroll as you browse, and exports to CSV, XLSX, or JSON, all without a server in the middle. We'll keep watching this case and the rest of the docket, and we'll update our coverage if Google's next move changes the picture.

This is general information, not legal advice.