LLMS Central - The Robots.txt for AI
AI Models

I gave ChatGPT, Claude, and NotebookLM the same 100-page PDF — here's who actually understood it

XDA Developers1 min read
Share:
I gave ChatGPT, Claude, and NotebookLM the same 100-page PDF — here's who actually understood it

Original Article Summary

Time to see who actually read the PDF

Read full article at XDA Developers

Our Analysis

ChatGPT's evaluation of a 100‑page PDF alongside Anthropic's Claude and Google's NotebookLM revealed that only ChatGPT consistently extracted accurate information across the entire document, highlighting its superior long‑context comprehension. For website owners, this means AI‑driven agents can now parse extensive, text‑heavy resources such as whitepapers, manuals, or policy documents with high fidelity. Search engines and third‑party AI services may begin indexing full PDFs rather than just metadata, increasing the risk of proprietary content being repurposed or cited without attribution. Moreover, the heightened ability of bots to understand nuanced sections could affect how content is ranked, as AI‑generated summaries may surface in SERPs, potentially diverting traffic from the original site. **Actionable tips:** 1. **Update your llms.txt** to explicitly declare which PDF endpoints are allowed for AI crawling (e.g., `User‑Agent: ChatGPTBot\nAllow: /public-reports/`) and which are disallowed (e.g., `Disallow: /internal-docs/`). 2. **Deploy bot‑traffic analytics** that flag long‑duration sessions and high‑page‑depth requests typical of large‑document processing; set alerts for any AI‑identified user‑agents. 3. **Add watermarks or hidden identifiers** inside PDFs to trace unauthorized AI extraction, then monitor for those markers in downstream content using automated plagiarism scanners.

Related Topics

ChatGPTClaude

Track AI Bots on Your Website

See which AI crawlers like ChatGPT, Claude, and Gemini are visiting your site. Get real-time analytics and actionable insights.

Start Tracking Free →