Chrome’s new Lighthouse Agentic Looking audit treats your .txt file as a markdown doc. In case your llms.txt does not use markdown hyperlink syntax, you fail the audit, even when each hyperlink in the file is correct and works. I ran the audit on nohacks.co. Two of six audits handed. Three got here again not relevant. One failed: the llms.txt audit, with the verbatim error “File does not seem to comprise any hyperlinks.” The repair was 5 characters per hyperlink. The file is nonetheless served as plain textual content. Solely the audit outcome modified.
Lighthouse 13.3.0 shipped the Agentic Looking class alongside Efficiency, Accessibility, search engine optimisation, and Greatest Practices. Six audits in the default set: accessibility tree well-formedness (agent-accessibility-tree), cumulative structure shift (cumulative-layout-shift), llms.txt discoverability (llms-txt), and three WebMCP checks (webmcp-registered-tools, webmcp-form-coverage, webmcp-schema-validity). The class returns a fractional move ratio as an alternative of a 0-to-100 rating, as a result of the requirements for the agentic internet are nonetheless in movement.
1 Of 6 Audits Failed On Nohacks.co
I ran the audit by way of the Lighthouse CLI: npx lighthouse@newest https://nohacks.co --only-categories=agentic-browsing. Six audits returned. Three got here again not-applicable, all WebMCP: webmcp-registered-tools, webmcp-form-coverage, and webmcp-schema-validity. Lighthouse provides no motive for a not-applicable outcome, it simply marks the audit and strikes on. nohacks.co does expose WebMCP, however solely by means of the experimental crucial navigator.modelContext API (two glossary instruments, two for an agentic-browser listing), with no declarative kind annotations. The scan ran in a default headless Chrome 150 with no WebMCP flag, so the not-applicable verdict might imply the web site exposes nothing these audits acknowledge, or that the scan atmosphere had no WebMCP API energetic at the time. Lighthouse does not say which. Two audits handed cleanly: agent-accessibility-tree reported “All audits handed,” confirming the semantic HTML and ARIA construction is well-formed sufficient for brokers to navigate, and cumulative-layout-shift got here again at zero.
One audit failed: llms-txt. The verbatim error message from Lighthouse was:
File does not seem to comprise any hyperlinks.
The class rating was 0.67. That was the first shock. The file at nohacks.co/llms.txt has many hyperlinks. Navigation paths to articles, episodes, visitors, the glossary. RSS feed URLs. Audio file URL patterns. The file is over 5 kilobytes of structured content material. So why was Lighthouse reporting zero hyperlinks?
Lighthouse Parses .txt As Markdown And Rejects Plain-Textual content Hyperlinks
The file extension is .txt, however Lighthouse parses the contents as markdown, and calls for markdown hyperlink syntax for any textual content to depend as a hyperlink. The file is named llms.txt. The HTTP server returns it with a textual content/plain MIME kind. Open it in a browser, and also you see plain textual content. However the llms.txt specification at llmstxt.org defines the format as a markdown doc. The spec is express: “Every part comprises a markdown bullet listing of hyperlinks. Every listing merchandise has a hyperlink adopted by optionally available notes about the hyperlink, separated from the hyperlink by a colon.” Lighthouse’s parser enforces that strictly. Each hyperlink should be encoded as markdown hyperlink syntax, [text](url), with sq. brackets round the hyperlink textual content and parentheses round the URL.
My file had been utilizing a extra pure plain-text format:
- Homepage: / - Publication masthead, cornerstone sequence, newest articles and episodes
- Articles: /weblog - All articles on AXO, the agentic internet, and AI brokers
- Episode: /episode/[slug] - Full present notes, transcript, audio participant
Similar locations. Similar descriptions. Similar information. Lighthouse’s parser does not register these traces as hyperlinks. Throughout the total file, it registered precisely zero. Audit fails.
A file with a .txt extension, served with a textual content/plain MIME kind, that fails an audit until it is formatted as markdown. That is a mismatch the audit layer is going to have to be extra sincere about. The extension says one factor. The MIME kind says one factor. The parser is the supply of fact, and the parser calls for markdown.
The Repair Is 5 Characters Per Hyperlink
Wrap every hyperlink goal in markdown bracket-paren syntax, [text](url), and change the - separator before every description with : . 5 characters per hyperlink. Mechanical conversion, repeated throughout the file.
- [Homepage](/): Publication masthead, cornerstone sequence, newest articles and episodes
- [Articles](/weblog): All articles on AXO, the agentic internet, and AI brokers
- [Episode](/episode/[slug]): Full present notes, transcript, audio participant
I made the edit. Re-ran the audit. Rating went from 0.67 to 1.0. The audit title flipped from “llms.txt does not observe suggestions” to “llms.txt follows suggestions.” No element gadgets in the after-report. Clear move.
The file is nonetheless served as textual content/plain. The file extension is nonetheless .txt. The file content material is nonetheless the identical content material. Solely the hyperlink encoding modified.
Lighthouse Measures Parseable Hyperlink Syntax, Not File High quality
The audit checks whether or not your file is mechanically parseable. It does not test whether or not the file describes your web site usefully. Each reads are true at the identical time.
The primary learn: The audit is measuring one thing actual. Markdown hyperlink syntax is mechanically parseable. Plain-text descriptive traces are not. If an AI agent (or the Lighthouse parser standing in for an agent) wants to extract hyperlinks from the file programmatically, the markdown format is required. The audit is right that the file before my repair might not be parsed for hyperlinks by the normal tooling. The conversion to markdown hyperlink syntax fixes an actual interoperability hole.
The second learn: format compliance is not the identical as file high quality. A thoughtfully-written, correct, complete llms.txt that makes use of plain-text descriptions fails this audit. A skinny, auto-generated llms.txt with markdown hyperlink syntax passes. The audit can not inform the distinction between the two. The WordPress plugin AIOSEO, utilized by over 3 million web sites per its WordPress.org listing, generates llms.txt recordsdata with markdown hyperlink syntax by default, a default-on conduct Glenn Gabe surfaced, and the plugin’s personal documentation confirms. These auto-generated recordsdata use markdown hyperlink syntax as a result of that is what the generator emits. Most of them most likely move this audit. Most hand-curated, owner-aware llms.txt files probably fail it.
That hole is price fascinated about before treating the audit’s move/fail as a measurement of how agent-ready your web site actually is. The audit is checking whether or not your file is parseable. It is not checking whether or not your file is helpful.
Ought to You Care About Lighthouse Agentic Looking’s Llms.txt Verify?
Sure, however narrowly. Lighthouse can inform you whether or not your llms.txt is parseable as markdown. It can not inform you whether or not the file describes your web site actually. That test is yours. Open Chrome DevTools, click on the Lighthouse tab, verify the Agentic Looking class is checked, and run Analyze on your URL. The audit takes beneath a minute. If it fails on the no-links error, the repair is 5 characters per hyperlink and 5 minutes of enhancing. If it passes, the more durable query is the one Lighthouse can not ask. Was the file auto-generated by a plugin you probably did not configure, or did you write it your self, and both manner, does it describe what your web site truly is?
The Machine-First Architecture Construction pillar sits beneath all of this: knowledge fashions before web page layouts, rendering independence, content material that does not rely on client-side JavaScript or human-display defaults to be machine-readable. The llms.txt audit is a slender test at that layer. The larger structural query, whether or not your machine-readable floor describes your web site precisely, is yours to run.
Extra Sources:
This submit was initially printed on No Hacks.
Featured Picture: Darko 1981/Shutterstock
Disclaimer: This article is sourced from external platforms. OverBeta has not independently verified the information. Readers are advised to verify details before relying on them.
