The New York Times v. Brave Puts AI Search Indexing Under Scrutiny
The New York Times has sued Brave Software over allegations that its search index used Times journalism and was sold as AI-grounding infrastructure. The unresolved case highlights why publishers need to understand how their content can surface through AI search systems.
The New York Times Co. has filed a copyright complaint against Brave Software that places a growing part of search infrastructure under a legal and publishing-industry spotlight: the independent web indexes used to ground AI answers.
Filed on November 2, 2026, the complaint alleges that Brave scraped Times journalism, including paywalled material, for its search index and then monetized that index through access sold to AI companies via the Brave Search API. The case is ongoing, and the court has not determined whether Brave is liable or established the scope of any alleged conduct. Still, the dispute offers a concrete example of a wider issue for publishers: content may be discovered and reused through an AI-ready search index even when it is not appearing in a conventional Google results page.
The case can be followed through the Times v. Brave docket entry.
What the Times alleges about Brave’s index
According to the complaint, Brave built a large-scale index from web content, including Times material, and made that index available to AI companies. The filing describes an index of more than 30 billion pages. Subsequent reporting has focused on the allegation that this index is not solely used to power Brave Search, but is also commercialized as data infrastructure for AI-generated responses.
This matters because an index is a foundational layer. A search interface may show links, while an AI product can use indexed material as context for answering a question, summarizing a topic or selecting sources to cite. The user may never directly conduct a search on Brave.com for the content to influence an answer elsewhere.
Brave publicly markets its Search API for AI uses and describes its LLM Context API as a way to ground AI answers in its index. Its own materials also describe an index at a scale of tens of billions of pages. Those public product claims do not resolve the lawsuit’s copyright allegations, but they help explain why the dispute reaches beyond a conventional search-scraping disagreement.
Why this is a search visibility issue, not just a copyright case
For years, publishers have treated crawling and indexing largely as prerequisites for visibility in search results. AI search changes the practical stakes. A page can potentially become source material for an answer generated in another interface, where the publisher receives a citation, a link, limited attribution or no measurable referral at all.
The Times’ allegations concern ownership and permission. For SEO and GEO teams, the operational question is slightly different: which indexes and AI-facing retrieval systems can access the site, and what visibility or control follows from that access?
Brave’s API positioning illustrates the distinction:
| Layer | Potential role | Publisher question |
|---|---|---|
| Brave Search index | Discovers, crawls and stores web pages for retrieval. | Is the site accessible to Brave’s relevant crawlers? |
| Search API | Lets third parties access Brave Search results or index-derived information. | Could a third-party product use Brave as part of its search layer? |
| LLM context services | Can provide retrieved web context to help ground an AI response. | How might source selection, linking and attribution appear in the final answer? |
The relationship between an indexed page and an individual AI answer is not guaranteed. Index inclusion does not mean a page will be retrieved, cited or clicked. Likewise, a mention in an AI answer does not prove a particular index supplied it. Retrieval choices, model behavior, query wording and the product using the underlying data can all affect the outcome.
What publishers can audit now
The litigation does not create a new technical standard for publisher controls. It does, however, make existing indexing choices more consequential. Publishers should begin with an inventory rather than assuming every crawler has the same purpose or every form of access has the same business value.
Review crawler directives and their trade-offs
Check the site’s robots.txt file and any relevant page-level directives. Identify whether Brave’s crawlers are allowed, blocked or subject to rules that have changed over time. Robots.txt is an important signal for compliant crawlers, but it is not a universal technical access-control mechanism, and it does not settle the legal questions raised in the case.
Before blocking a crawler, document the likely visibility cost. A publisher that prevents indexing may reduce the chance of appearing in Brave Search or services that rely on its index. Whether that trade-off is worthwhile depends on the publisher’s content strategy, licensing position and tolerance for AI-mediated discovery.
Separate index presence from AI referral value
If a site is discoverable in a search index, that is only the start of measurement. Teams should track branded queries, important informational topics and pages that commonly attract citations or summaries. Watch for references in relevant AI search products, but distinguish observed citations from traffic, conversions and revenue.
Server logs can also help identify crawler activity where user-agent information is available. Pair that technical evidence with referral reporting and manual checks of how key content is represented. Avoid drawing broad conclusions from isolated prompts, because AI answers can vary between sessions and over time.
Protect access-controlled content deliberately
The complaint’s references to paywalled material are especially relevant for subscription publishers. Teams should review whether paywalled pages, preview text, structured data and alternate versions expose more content than intended. This is not a claim that a particular configuration caused the conduct alleged in the lawsuit. It is a reminder that access controls, crawl directives and content-delivery choices should be assessed together.
What remains unresolved
The central allegations in The New York Times’ complaint have not been adjudicated. Brave has denied or pushed back against claims that it improperly uses publisher content, and the eventual legal outcome could turn on facts and legal arguments not established by the publicly available case summary.
It is also too early to quantify any impact on organic traffic. The existence of a large AI-facing index does not show how often a given publisher is used in AI answers, whether those uses produce citations or whether they displace search clicks. Those are separate measurement questions.
What is clear is that independent indexes are becoming more strategically relevant as AI products seek current web information. Publishers that only monitor traditional search rankings may miss a layer of discovery that increasingly sits behind answers rather than in front of users as a results page.
If your team needs a clearer view of where content is prepared for AI-era discovery, create a GEO Search Leads account. It provides a practical starting point for assessing website GEO readiness and identifying optimization opportunities around content accessibility, entities and signals that can affect how a site is understood by search and AI systems. Use that assessment alongside your crawler, indexing and content-governance reviews.
Frequently Asked Questions
Did a court find that Brave infringed The New York Times’ copyright?
No. The New York Times filed a complaint alleging copyright infringement and related issues, but the case is ongoing. A court has not yet determined liability or the full scope of the allegations.
Does being in Brave’s index mean a page will appear in an AI answer?
No. Indexing makes retrieval possible, but it does not guarantee that a page will be selected as context, cited in an answer or generate a referral visit. The outcome depends on the query, the AI product and its retrieval and answer-generation systems.
Can robots.txt control whether AI systems use publisher content?
Robots.txt can communicate crawl preferences to crawlers that honor it, but it is not a universal access-control or legal solution. Publishers should review crawler directives alongside paywall settings, content delivery and their broader indexing strategy.
What is Brave’s LLM Context API?
Brave positions its LLM Context API as a service that provides web context from Brave’s index to help ground AI-generated answers. The specific use of that context, including citations and presentation, can depend on the product integrating the service.
Conclusion
The Times v. Brave case is unresolved, but it exposes an important shift in web discovery: search indexes can now function as infrastructure for AI answers as well as search results. Publishers should treat crawler governance, index monitoring and AI-reference measurement as connected parts of their visibility strategy, while keeping legal claims and confirmed technical facts clearly separate.