Google Addresses llms-author.txt and Online Identification

Google's John Mueller said Google does not use `llms-author.txt` in response to a Reddit question about online identity and author disambiguation, according to Search Engine Journal on July 6, 2026. The practical takeaway for SEO, retrieval, and knowledge-graph teams is that self-declared AI metadata remains weak unless a crawler or platform explicitly supports it. The same report says Mueller also dismissed Cloudflare-style Content-Signal robots directives as unsupported by Google. Practitioners should treat these files as experimental documentation for agents, not as a reliable way to make a person or brand easier to identify in search and AI answers.
The useful lesson is that identity metadata only matters when the consuming system actually reads and trusts it. For search and retrieval teams, llms-author.txt is a reminder that self-declared files can help document intent for some agents, but they are not a substitute for crawlable pages, consistent entity references, structured data, reputable mentions, and platform support.
What happened
Search Engine Journal reported that Google's John Mueller responded to a Reddit user who was testing an llms-author.txt file and Content-Signal directives to improve online identification for a name that overlaps with more prominent entities. The report says Mueller stated that Google does not use llms.txt or llms-author.txt, and that he did not know of other crawlers or LLMs confirming use of those files beyond SEO tools.
Technical context
The distinction matters because several ideas are being conflated: the broader /llms.txt proposal, a non-standard llms-author.txt variant, Cloudflare's Content Signals policy, and Cloudflare's Markdown for Agents feature. Cloudflare documents Content Signals as machine-readable robots.txt directives for search, AI input, and AI training preferences, while Markdown for Agents converts eligible HTML pages to Markdown when clients request text/markdown. That does not mean Google Search treats those signals as ranking or identity inputs.
For practitioners
Use these files only as supplemental documentation when they match a real crawler or agent workflow. For discoverability and entity disambiguation, the safer work is still durable web evidence: author pages, organization profiles, schema, canonical links, bylines, citations, and third-party references that search systems can corroborate.
What to watch
The meaningful signals are explicit support announcements from major crawlers, measurable server-log fetches from known AI agents, and documentation that explains how a platform consumes the file. Without those signals, llms-author.txt should be treated as an experiment rather than an SEO control.
Key Points
- 1Google does not use llms-author.txt, so identity teams should not treat it as a Search disambiguation lever.
- 2Cloudflare Content Signals and Markdown for Agents are separate mechanisms, not proof that Google reads author files.
- 3Durable entity evidence still depends on crawlable profiles, schema, canonical links, bylines, citations, and third-party references.
Scoring Rationale
This is a minor but relevant AI-search and SEO signal story, useful for practitioners deciding whether to invest in experimental metadata files. It has limited broader impact because it is a clarification around unsupported tooling rather than a platform launch or confirmed ranking change.
Sources
Public references used for this report.
Practice with real Ad Tech data
90 SQL & Python problems · 15 industry datasets
250 free problems · No credit card
See all Ad Tech problems

