AI search news · ·

Is scraping Google's search results a DMCA violation? A judge said not by itself — so Google's amended complaint pivots to licensed content

Where the case stands, docket read 2026-09-30: briefing on SerpApi's motion to dismiss Google's amended complaint is complete. SerpApi moved on 2026-08-24 (entry 49), asking for dismissal with prejudice; Google opposed on 2026-09-15 (entry 58); SerpApi replied on 2026-09-29 (entry 59). The hearing is set for 2026-10-13, reset from 2026-09-29 on 2026-09-04. On 2026-09-15 the court denied SerpApi's motion to compel production of the three licensing agreements the amended complaint relies on (entry 57); the order is now a free PDF on CourtListener and gives two reasons: SerpApi had already responded to the amended complaint by moving to dismiss, and SerpApi cited no authority that the incorporation-by-reference doctrine "can be used as a discovery mechanism." No merits ruling exists on the amended complaint. The background: on 2026-07-20 Judge Yvonne Gonzalez Rogers ruled that Google's DMCA anti-circumvention claims fail as a matter of law "to the extent that they are premised on instances where SearchGuard controls access to Google Search results that do not contain any copyrighted content" and dismissed that portion without leave to amend. Google refiled on 2026-08-10 around the licensed copyrighted content inside results, quoting its Reddit agreement as directing it "not to enable third parties to extract and independently commercialize the licensed content." The pivot matters to anyone whose AI-visibility data arrives via scraped Google results.

Where the case stands (docket read 2026-09-30)

We re-read the CourtListener docket on 2026-09-30. Every entry after the amended complaint (entry 45, 2026-08-10) is below. Entries 46, 48, 49, 55, 56 and 57 are free PDFs on CourtListener and we read them; entries 47, 51, 52, 54, 58 and 59 exist there only as docket text, and we quote that text rather than the documents. The two briefs on the motion to dismiss after SerpApi's opening brief (Google's opposition, entry 58; SerpApi's reply, entry 59) are among the ones we have not read.

DateEntryWhat it is
2026-08-1746SerpApi moves to require service of the three license agreements incorporated into the amended complaint (hearing was set for 2026-09-22)
2026-08-1847SerpApi's administrative motion to enlarge the time to respond to the amended complaint
2026-08-2148Google opposes entry 47
2026-08-2449SerpApi moves to dismiss the amended complaint, asking that it be dismissed with prejudice
2026-08-2450Text order: entry 47 found moot "in light of SerpApi's filing of a motion to dismiss"
2026-08-3151Google opposes the motion to require service of the agreements (entry 46)
2026-08-3152Google's administrative motion to enlarge the briefing time on the motion to dismiss
2026-09-0153Text order tentatively granting entry 52, directing SerpApi's counsel to certify they had read the district's Professional Conduct Guidelines: "Federal courts are incredibly busy. The Court should not need to spend time dealing with such a small routine matter."
2026-09-0354SerpApi's response to entry 52 and the 2026-09-01 order, with four declarations and two email exhibits
2026-09-0455Order granting Google's motion to enlarge time "as modified"; the same day the deadlines on entry 49 were reset: opposition due 2026-09-15, reply due 2026-09-29, hearing moved from 2026-09-29 to 2026-10-13 at 2:00 PM in Oakland
2026-09-0856SerpApi's reply on the motion to require service of the agreements
2026-09-1557"ORDER DENYING MOTION TO COMPEL THE PRODUCTION OF LICENSING AGREEMENTS" by Chief Judge Yvonne Gonzalez Rogers; "Hearing previously set for 9/22/2026, is vacated"; free PDF, quoted below
2026-09-1558Google's opposition to the motion to dismiss ("OPPOSITION/RESPONSE (re 49 MOTION to Dismiss the Amended Complaint) filed by Google LLC"), on PACER only
2026-09-2959SerpApi's reply on the motion to dismiss ("REPLY (re 49 MOTION to Dismiss the Amended Complaint) filed by SerpApi, LLC"), on PACER only; briefing complete

SerpApi's motion to dismiss opens: "This case is a shadow of its former self. Google began by seeking to block access to all its public search results. The Court rightly rejected Google's attempt to convert the DMCA into a general-purpose anti-scraping statute, dismissing with prejudice any claim for search results not involving copyrighted works." Its argument is that the amended complaint names four sources of authority for SearchGuard (an agreement with an unnamed licensing partner, one with an unnamed content partner, the Reddit agreement, and Google's own privacy policy) and quotes the operative terms of none of them: "Google chose not to place before the Court the three license agreements it proffers as the cure for its prior pleading deficiencies. Nor does it quote the operative terms." SerpApi's brief quotes the July order back at Google: without the text, "the Court cannot reasonably infer that such license agreements grant Google authorization to deploy technological measures to control access to the copyrighted content at issue."

SerpApi's separate motion asked the court to order Google to serve those three agreements so their text could be read against the motion to dismiss. The court denied it on 2026-09-15 without holding the hearing, in a three-page order. The two reasons, in the order's words: "First, the fact that SerpApi has already responded to the AC by filing a motion to dismiss, see Dkt. No. 49, invalidates its contention that it cannot adequately respond to the AC without the licensing agreements at issue. Second, SerpApi has not cited a single case in which a court has ordered the production of documents mentioned in a complaint on the ground that they are incorporated by reference into the complaint. Nor has SerpApi cited any authority that the incorporation-by-reference doctrine can be used as a discovery mechanism." The order adds that the doctrine "can be used to allow the Court to evaluate known documents referenced in a complaint," but that "no legal authority exists for the proposition that normal procedural, including discovery, processes should be circumvented." It also restates the July holding the amended complaint has to overcome: allegations that Google licenses the content "were insufficient, without more, to raise the inference that copyright owners authorized it to deploy technological measures to control access to their copyrighted content," and notes that discovery is stayed until the motion to dismiss is resolved. So the motion to dismiss goes to the 2026-10-13 hearing with Google's description of the agreements on the record and the agreements themselves not.

Corrections made on September 30. The 2026-09-22 version of this page said the entry 57 order was on PACER only and that we had not read it; the PDF is free on CourtListener and is quoted above. It said the docket text for entry 58 did not name the filer; the docket text reads "filed by Google LLC." Entries 47, 48 and 50 to 54 were left out of the table; they are in it now.

What happened, from the docket

Google sued SerpApi — the API vendor that sells structured, scraped Google results at scale — in the Northern District of California on 2025-12-19, pleading two claims under the DMCA's anti-circumvention provisions (17 U.S.C. § 1201(a)(1)(A) and § 1201(a)(2)): that SerpApi circumvents SearchGuard, Google's anti-bot access control, and traffics in the means to do so. On 2026-07-20, the court granted SerpApi's motion to dismiss — partly with leave to amend, and partly without: where the scraped results pages contain no copyrighted content, the DMCA claims "fail as a matter of law" and "amendment would be futile." Google's amended complaint, filed on the court's 2026-08-10 deadline, re-pleads both § 1201 claims — now built on the copyrighted material Google licenses into its results.

Free · 60 seconds · no account

Our audits do not scrape Google; they ask each engine directly. See what the engines say about a business today: we ask 2 AI engines 3 real buyer questions and show you exactly who they name.

Begin your check

Free · 60 sec

No account · No card · 3 buyer questions, 2 engines

By running a check you agree to our Terms and Privacy Policy.

The licensed-content theory, in Google's own words

The amended complaint's clearest new material is contractual. Google describes its licensing agreement with Reddit as one that "directs Google not to enable third parties to extract and independently commercialize the licensed content," and alleges its licensing partners have "expressly requested that Google prevent unauthorized access to licensed content." It also leans on Reddit's separate, ongoing suit against SerpApi (Reddit Inc. v. SerpApi LLC, No. 25-cv-8736, S.D.N.Y.), quoting Reddit's own filing that it "has always authorized its partners, including Google, to protect [the licensed] content from misuse." Knowledge-panel photographs, music lyrics, and licensed user-generated content are the copyrighted components Google now says SearchGuard protects.

Why this docket matters for AI-visibility measurement

Most tools that report on Google AI Overviews and AI Mode visibility do not get that data from Google — the official Search Console surface for generative-AI performance has no API, no query data, and no click data. The industry's working substitute is scraped SERPs, and SerpApi is one of the largest suppliers of exactly that. This case is drawing the legal boundary around the supply chain.

No merits ruling exists on the amended complaint. Briefing on the motion to dismiss closed with SerpApi's reply on 2026-09-29 (entry 59); the hearing is set for 2026-10-13 at 2:00 PM in Oakland. The next edit to this page follows the order on that motion, read from the docket, not from either side's press coverage.

See your number

See which businesses AI names when your client's buyers ask.

Running this for clients? The $249 agency 5-pack audits five businesses, white-labeled.

Check a client's AI visibility

Begin your check

Free · 60 sec

No account · No card · 3 buyer questions, 2 engines

By running a check you agree to our Terms and Privacy Policy.

Who runs this