Google filed an Amended Complaint against SerpApi on 10 August 2026, roughly a month after a US court dismissed its original lawsuit against the SERP scraping tool. Search Engine Roundtable reported the refiling on 12 August 2026, and the new pleading changes the argument: instead of the grounds the court threw out, Google now frames the case around protecting licensed content inside its own search results.
The specific example, per MediaPost's account of the filing, is Reddit. Google alleges that Reddit, which licenses its content to Google, specifically directed Google "not to enable third parties to extract and independently commercialize the licensed content", and that Google's "licensing partners" have "expressly requested that Google prevent unauthorized access to licensed content". The argument is that Google is contractually obliged to police scraping of partner content that appears in its results.
What is new here, and what is not
Relevant Audience already covered the dismissal of Google's DMCA lawsuit against SerpApi. That part is old news and should not be re-reported as if it happened this week. The court dismissed the original complaint roughly a month before this filing.
The new element is narrow and specific. Google did not appeal the dismissal into a different court or drop the case. It amended the complaint on 10 August 2026 and built the amended version on a licensed-content theory, with Reddit named as the example of a licensing partner whose instructions Google says it has to honour. That shift in legal theory, not the existence of the lawsuit, is the story.
The sourcing caveat, stated plainly
Barry Schwartz noted that the full complaint had not appeared on CourtListener at the time of writing. Everything anyone knows about the content of the amended pleading therefore rests on MediaPost's reporting of the filing, which Search Engine Roundtable cited and quoted. Search Engine Journal covered the same amendment on 11 August 2026.
That matters for how the quotes should be read. The phrases about extracting and commercializing licensed content, and about licensing partners expressly requesting that Google prevent unauthorized access, come to us through MediaPost's account rather than from a document anyone reading this has seen. Nobody outside the parties has confirmed the full scope of the amended claims, the causes of action pleaded, or the relief Google is asking for. Treat the quotes as reported, not as verified primary text.
Why a licensed-content theory is a different hook
The original case leaned on a DMCA argument that the court rejected. A licensed-content theory does not depend on that reasoning at all. It routes the argument through Google's contracts with the publishers and platforms whose material appears inside search results, which changes who Google is arguing on behalf of.
Under that framing, Google is not only asserting its own rights over its results pages. It is asserting an obligation to third parties who licensed content to it. If a court accepted that framing, the enforceable surface would be defined by Google's licensing agreements rather than by copyright law applied to a results page, and licensing agreements are private, numerous and not visible to the companies being sued. That is a broader hook, and a less predictable one for anyone building a product on scraped results.
None of that has been tested. No ruling has been issued on the amended complaint, no hearing date has been reported, and no licensing partner other than Reddit has been named in the reporting. Whether the theory survives a motion to dismiss is exactly the thing nobody knows yet.
The filing at a glance
The table below carries only what was reported by Search Engine Roundtable on 12 August 2026 and what it attributed to MediaPost.
| Element | Detail | How it is sourced |
|---|---|---|
| Original lawsuit | Google's suit against SerpApi was dismissed roughly a month before the amendment | Reported by Search Engine Roundtable |
| Amended Complaint | Filed 10 August 2026 | Reported by Search Engine Roundtable |
| New theory | Protection of licensed content appearing inside Google's search results | Per MediaPost's account of the filing |
| Named partner | Reddit, said to have directed Google not to enable third parties to extract and independently commercialize the licensed content | Per MediaPost's account of the filing |
| Primary document | Not on CourtListener at the time of writing | Noted by Barry Schwartz |
Why SEO teams should care about a scraping lawsuit
Almost every number in a standard SEO report that is not from Search Console comes, at some point in the chain, from scraped SERP data. Rank trackers scrape. SERP feature monitors scrape. Competitor visibility tools scrape. The newer AI visibility trackers, the ones telling you whether a brand gets cited in AI Overviews or in an assistant answer, are built on the same kind of collection, and many of them buy that data from an upstream provider rather than collecting it themselves.
That is the exposure. Nothing about this case touches an advertiser's or publisher's own Google account, rankings or traffic. What it touches is the supply chain sitting behind the reporting tools those teams pay for. If enforcement against scrapers becomes easier for Google, the effects would show up as pricing changes, reduced coverage of certain SERP features, slower refresh rates, or a provider quietly narrowing what it collects. Those are commercial and operational effects on vendors, not algorithmic effects on sites.
It is worth being precise about the AI angle, because this is where speculation usually starts. The reported filing is about scraping of licensed content in Google's results. It says nothing about AI Overviews ranking, nothing about how content gets cited in AI answers, and nothing about what publishers should do to be included. Anyone extending this story into advice about visibility in AI answers is going beyond what was reported. The connection is a data-supply one: if AI visibility tools depend on scraped SERP data, their inputs are in scope; the citation behaviour of the assistants is not.
What is not known
- No ruling has been made on the amended complaint.
- No hearing date has been reported.
- No licensing partner other than Reddit has been named.
- The full text of the amended complaint was not publicly available on CourtListener at the time of the report.
- No statement has been reported from SerpApi in response to the amendment.
- Nothing has been reported about effects on any specific rank tracking or SEO tool.
Amended complaints get answered, and defendants routinely move to dismiss them. A filing is a claim, not a finding. The next real information point is the court's response to the amended pleading, whenever that arrives.
What this means for Thai marketers
What follows is Relevant Audience analysis. The reporting made no statement about Thailand or about any Thai business.
Thai agencies and in-house teams run rank tracking and, increasingly, AI visibility tracking through tools that ultimately buy scraped SERP data from someone. The exposure sits with those vendors and their pricing, coverage and refresh rates. It does not sit inside anyone's Google Ads account, Search Console property or website. If a client asks whether this lawsuit affects their rankings, the honest answer is no, and the useful answer is that it may affect what their reporting stack costs and how complete it is.
The sensible hedge is dull and cheap. Go through the metrics in your monthly report and mark each one by where the data comes from. Impressions, clicks, average position and query data come from Search Console, which is first-party and unaffected. Cost, conversions and impression share come from Google Ads, also first-party. Tracked keyword rankings, SERP feature presence, competitor visibility scores and share of voice in AI answers come from third-party collection, and those are the lines that would move if a vendor's data supply gets more expensive or thinner.
That mapping tends to surface two questions worth answering. The first is how much of the report depends on a single vendor. The second is whether any client-facing metric has no first-party equivalent at all, which would be a reporting risk regardless of how this case ends. Building the report so that first-party data carries the headline numbers, with third-party data used for competitive context, is better practice for anyone doing serious SEO work even if no court ever rules on this.
FAQ: questions clients are asking about the SerpApi filing
Does this affect my website's rankings?
No. This is a commercial dispute between Google and a scraping tool provider, and nothing in the reporting describes any change to ranking, indexing or crawling of ordinary websites.
Will my rank tracking tool stop working?
Nothing has been reported that says so. No ruling has been made on the amended complaint, no injunction has been reported, and no specific SEO tool has been named as affected. Any effect would arrive through vendor decisions rather than through anything visible in your account.
Did Google win the case?
No. The original complaint was dismissed roughly a month before this filing, and the amendment is Google's attempt to plead a different theory. A court has not ruled on the amended version, and a filing is not a decision.
Can I read the actual complaint?
Not at the time of the report. Barry Schwartz noted the full complaint had not appeared on CourtListener, so the details in circulation come from MediaPost's account of the filing rather than from the document itself.
Does this have anything to do with AI search visibility?
Only indirectly, through data supply. The reported allegations concern scraping of licensed content in Google's results, and if AI visibility trackers rely on scraped SERP data then their inputs are in scope, but nothing in the reporting addresses how AI answers select or cite sources.
Where to take this next
The practical takeaway is a reporting audit rather than a legal one: know which numbers you hand to clients or management depend on someone else scraping Google, and know which come straight from your own properties. If you want a second pair of eyes on where your reporting data actually originates, and which metrics would survive a supply squeeze, we are happy to walk through it with you.
