Nobody put copyright in your job description. Still, if you run content in 2026, you've inherited two questions about it. One comes from the engines: they read and cite what you publish, so what rights do you actually have over that? The other comes from inside your team, which now ships AI-assisted content, and somebody has to know who owns it and what it might infringe.
This year both questions have real answers, or at least a clear line between what's settled and what isn't, and a sense of what to do while the courts finish. I'll say one thing plainly first: this is a practitioner's map of the AI search copyright terrain, none of it is legal advice, and the calls specific to your business belong with counsel.
Three questions the courts keep separate
Courts and regulators are treating three activities as legally distinct, and once you see them separately, most of the noise goes away. There's training, when a model ingests your content to learn from it. When an engine fetches and quotes your pages to build an answer, that's retrieval, and output covers whatever the model generates and who owns it.
Different cases go after different layers, and different defenses apply, so a headline about one layer usually tells you nothing about the other two. When marketers argue about "AI stealing content," they're mostly blending all three.
A heavily upvoted r/webdev thread asked the question underneath all of it: where did AI companies get legal permission to train on copyrighted data? As of September 2026, the straight answer is that most of them never asked. They made a fair-use bet, and the courts are still grading it.
Where did AI companies get legal permission to train on copyrighted data?
This is a question I have thought about a lot lately. If it wasn’t for the repositories hosted in Github and other platforms, none of the models would exist now. Specifically, I don’t remember agreeing on anything that said something about...
Where the big cases actually stand
Three matters define the map in September 2026, and all three moved this summer.
The newest move came on September 2, when the US government filed a brief backing OpenAI's position that training on copyrighted material is generally fair use, warning that restricting it could hold back creative and scientific progress. That brief landed in New York Times v. OpenAI, still the main event on the training question and still being actively litigated, with no final merits ruling. Creator communities took it badly, and one widely shared thread called it the end of the argument. I read it differently. A brief adds weight to one side of a scale that's still moving, and the verdict hasn't come.
The Anthropic books settlement gets miscited constantly. It went final in July, when a judge approved the $1.5 billion class settlement with authors over pirated books used in training. What it resolved was past claims about pirated source material, and it set no precedent on whether training itself is lawful. It did put a visible market price on getting provenance wrong, which is why every serious lab now cares where its data came from.
In late July a Manhattan judge rejected most of Perplexity's bid to dismiss Reddit's suit over data scraping, and of the three, Reddit v. Perplexity sits closest to AI search. The claims that scrapers circumvented protective measures can now go forward. The ruling is procedural and nothing is final, but it keeps alive the question content owners care about most: whether a site's technical controls carry legal force when a crawler ignores them.
Line the three up and you get settlements and briefs where you'd want clean precedents. So for the next few years, deals and risk tolerance will set the working rules far more than decided law will.
AI search traffic grew 835% this year. Is your content ready?
RankControl generates 26 content formats optimized for ChatGPT, Claude, and Perplexity. Published on your domain, matched to your brand.
Your content inside the engines
What does all that unsettled law mean for what you publish? Your controls are technical and your compensation is visibility, and I'd make a deliberate decision about each. If Google's AI answers are your main worry, our piece on whether Google AI search is copyright theft walks through the new Search Console opt-out and what it costs you.
The technical controls are the crawler directives. GPTBot and ClaudeBot are in there, along with PerplexityBot and Google-Extended and the rest of the allow-block roster. Two things about them matter for strategy. They're voluntary signals, and their legal force is precisely what the scraping cases are testing. And blocking won't take you out of AI answers, because engines keep learning about you from third-party content. One community analysis found roughly a third of sites blocking GPTBot still got cited by ChatGPT through exactly those leaks.
Licensing is the other path, and for large publishers it's real money. For everyone else it's mostly out of reach. Nobody is writing checks to a B2B SaaS blog, and even the deals that do exist come with no standard rate card and confidential terms.
The frame I'd use is the one the Figma blocking episode made concrete. For most content teams, the real choice sits between visibility in the answer layer and a principled absence from it, while protection with payment attached stays a menu reserved for the largest publishers. Whichever way you go, decide it crawler by crawler and write it down, since a default you never chose is the only wrong answer.
The copyright status of what you ship
Ownership of your own output sits on firmer ground than most teams assume. The US Copyright Office has held steady here: copyright requires human authorship. Text a machine generated on its own isn't protectable. AI-assisted work is protectable to the extent a human exercised genuine creative control, by directing it, editing it substantially, or selecting and arranging the material, and when you register, you disclose the AI-generated portions and claim only the human-authored ones.
Think about what that first rule does to your business. If your pipeline generated an article and nobody meaningfully touched it, the article may be property nobody owns, and a competitor who lifted it wholesale would face a thin claim at most. So full automation with zero human authorship has a cost beyond quality, because it produces pages you may not be able to defend.
The fix is in the workflow. Get a person to edit each piece in ways that change its structure and add judgment. Weave in your own data and customer evidence, and keep a record of who did what. The same steps give you a stronger copyright position and better content.
Infringement can also run the other way, with your AI-assisted article reproducing someone else's protected text. The headline cases target the AI companies, though, and no wave of claims against their business customers has materialized. Your narrow real exposure is verbatim text sneaking into output, and guarding against it is boring, cheap insurance: an originality check in the publishing pipeline catches it.
Built by the team that got cited in 48 hours.
Content generation, backlink building, AI visibility tracking, and Google rankings. One platform, zero guesswork.
Vendor diligence: the questions your tools should answer
The last exposure point hides in your stack. What content teams buy are tools built on top of other companies' models, and the copyright posture of those tools varies more than their marketing suggests.
The big model providers moved early here. OpenAI's Copyright Shield and Microsoft's Copilot copyright commitment both promise to defend enterprise customers against infringement claims arising from output, and similar indemnities have spread through the serious end of the market since then.
That history hands you a clean diligence script for any AI content tool. I'd open with indemnity: will the vendor cover you against copyright claims on generated output, and does your tier actually qualify? Then ask what their underlying models were trained on, or at least which providers they build on. Last, find out whether they screen for originality before output reaches you or leave that job to you.
Good answers tell you the vendor took the provenance lesson from the Anthropic settlement seriously. A vendor with no answers is quietly handing the risk down the chain to you, priced as if it weren't there.
The five-point checklist
Everything above comes down to five workflow decisions a content lead can put in place this month.
- Set your crawler policy on purpose. Audit which AI crawlers you allow and block today, decide per engine with the visibility tradeoff in view, and record why.
- Build documented human authorship into the pipeline, with named editors, substantive revision passes and original data in every important piece. Keep a record of all of it, because that record is your copyright position.
- Run an originality check before anything publishes. One automated pass per article closes the realistic infringement exposure.
- Keep provenance records of which model, which sources and which human edits went into each piece. The Anthropic settlement's lesson generalizes here, since provenance is what gets expensive to reconstruct later.
- Recheck the legal map quarterly, never daily. Cases move in months, and a quarterly note from counsel beats a panic per headline.
The strategic read
Step back from the case names and one idea organizes the 2026 picture. A sharp commentator on X put it well: the fight looks like copyright, and underneath it's about who participates in the value AI builds from human work. Publishers with negotiating power are turning that participation into licenses and settlements. Everyone else participates through the answer layer itself, as citations and mentions and the trust they carry.
That's why the copyright question and the visibility question land on the same desk. If your team sets its crawler policy deliberately and ships content it can defend, and then actually watches what the engines do with it, you're playing the whole board.
The law will take years to settle. Your visibility is being decided now, and that's the part you can measure, which is the instrument we build: per-engine citation tracking that shows what ChatGPT, Perplexity, Claude, Gemini and Google's AI surfaces are doing with your content week over week, so your policy calls run on your own data instead of on litigation headlines.
See your first AI citation report in under 5 minutes.
No setup calls. No onboarding meetings. Connect your domain and see where AI mentions your brand right now.
