WikiHow's AI Copyright Lawsuit Argues Something Sharper Than Theft

The ai copyright lawsuit arguing something sharper than copying#

A fox does not need to steal the whole henhouse to empty it. It only needs to keep visiting until the hens stop laying for anyone else. That is the uncomfortable shape of the newest ai copyright lawsuit to land against OpenAI, and it is worth reading closely because its argument is genuinely different from the ones that came before it.

WikiHow filed suit against OpenAI in the U.S. District Court for the Southern District of New York on 21 August 2026, according to Playwire's coverage of the filing, alleging OpenAI scraped more than 11,000 of its how-to articles to train ChatGPT, covering upward of 1,200 registered copyrights. OpenAI's standard defence across this whole wave of suits, including the pending Authors Guild class action, is that training on publicly available text is protected fair use. A Reddit thread from SEO practitioner u/chrismcelroyseo, posted the same week, corroborates the article and copyright counts and adds that the complaint also alleges OpenAI kept crawling after robots.txt explicitly blocked it, and stripped copyright management information from the scraped pages.

Most prior AI copyright suits, including the widely covered Getty Images suit against Stability AI, argued straightforward copying: a model reproduced protected text or imagery closely enough to infringe. WikiHow's complaint leads with a different theory entirely. It argues economic substitution, that ChatGPT now "produce[s] competing how-to content on the same subjects, at a fraction of the time, effort, and cost", directly displacing the traffic and advertising revenue WikiHow's own pages once earned. Copying is about the past. Substitution is about the future the plaintiff says it no longer has.

Why substitution changes the whole case#

Courts have spent two years wrestling with whether training a model on copyrighted text is fair use. Substitution sidesteps that fight almost entirely. The question stops being "did the model copy the words" and becomes "did the model's answer replace the reason anyone needed the original page at all".

This is not WikiHow's theory alone. A 2025 research paper, The Economics of AI Training Data: A Research Agenda, tracked training-data licensing deals and found five distinct pricing structures already in use, nearly all of which exclude the original creators of the underlying content from any ongoing compensation once the initial deal is struck. Substitution is the economic mechanism that theory describes in practice: the value moves from the page that answered the question first to the system that answers it last.

This incident is not the first, either. Reddit's own SEO community, tracking the filing the week it landed, described it as OpenAI's twenty-fourth active copyright suit, joining a wave of publisher and author litigation the industry has watched build for two years, including The New York Times' own suit against OpenAI and Microsoft and the consolidated multidistrict copyright litigation, MDL No. 3143 now running in the Southern District of New York, all without a single settled precedent on the substitution question specifically. Every one of these cases is, at heart, a different generative ai copyright lawsuit testing a slightly different theory against the same underlying training practice.

What the numbers in the filing actually say#

WikiHow's complaint reportedly alleges OpenAI's crawlers kept visiting after robots.txt disallowed them, which if proven would matter well beyond this one case. A US appeals court recently held, in a separate dispute covered in folkfox's own reporting on agentic browsing, that a user-directed agent legally counts as the user acting, not the platform. That ruling was about consent to access on a user's behalf. It says nothing about a crawler that keeps returning after a site has explicitly declared it unwelcome, which is closer to what WikiHow alleges here.

The ai crawler access control question every publisher now faces#

robots.txt was never built to be an enforceable legal barrier. RFC 9309, the formal specification the file follows, describes it as advisory: a crawler is meant to fetch and honour it, but nothing in the standard stops one that simply chooses not to. Google's own developer documentation is equally direct that robots.txt is a request, not an access-control mechanism, which is precisely the gap WikiHow's complaint is trying to close with a lawsuit instead of a text file.

That gap is why the fox in this story does not just leave a scent at the gate and hope. WikiHow's complaint treats a crawler that ignores robots.txt as trespass rather than an oversight, which reframes ai crawler access control from a technical setting into a legal exhibit. Every publisher weighing whether to block, allow, or licence AI crawlers is now watching this case for the answer to a question their engineering team cannot settle alone: does robots.txt actually mean anything once it is written down, or does it only work on crawlers polite enough to prowl no further once asked.

What content teams should do this quarter#

Waiting for a court to settle the substitution question is not a content strategy, it is a bet on someone else's litigation timeline. A more useful response starts by measuring, not guessing, how much of a site's own traffic is already quietly slipping into a warren no analytics dashboard shows by default.

does ai violate copyrights is the wrong first question for most content teams to spend their energy on, because it will be litigated for years regardless of what any one publisher decides this quarter. The more useful question is whether a given piece of content still earns a visit once an AI system can answer the same query directly, and that is measurable today, in your own analytics, without waiting for a verdict. A April 2026 citation-absorption study, tracked in this newsroom's own weekly evidence review, found the same substitution pattern WikiHow alleges showing up in raw citation data months before any lawsuit made the argument in court.

This is precisely the audit folkfox runs for SEO and GEO clients already: crawler-log review, query-overlap measurement, and a citation-tracking layer that treats AI visibility as a metric worth reporting on its own, not a footnote under organic traffic. Content strategy now has to account for a reader who may never click through at all, and that shift did not start with this lawsuit. It only became impossible to ignore because of it. Whatever a court eventually decides about this specific ai copyright lawsuit, the underlying traffic pattern it describes is already measurable, today, in every content team's own logs.

Frequently asked questions#