PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchGrowNexus reported that 18 of 25 SaaS platforms in its audit published an llms.txt file, but that 72% figure is a snapshot of one sample—not proof of industry-wide adoption. The proposal itself is a practical convention for helping AI agents find useful documentation. For engineering teams, the key questions are what to put in the file, how to expose it, and how to judge adoption claims against the audit method.
What GrowNexus reported in its 25-platform audit
In an article dated September 19, 2026, GrowNexus described a sample of major SaaS platforms spanning developer tooling, content management systems, infrastructure, and productivity software. Its indexed article text reports these results:
| Measure | GrowNexus-reported result |
|---|---|
Platforms publishing an llms.txt file |
18 of 25 (72%) |
| Adopters following the article’s described structure | 12 of 18 (66.7%) |
Adopters emitting an HTTP rel="describedby" header |
2 of 18 (11.1%) |
Adopters implementing an HTML <link rel="describedby"> |
0 of 18 (0%) |
| Reported file sizes | 2,088–210,736 bytes; median 16,299 bytes |
These are figures attributed to GrowNexus’s article and named dataset; the underlying dataset and scripts were not independently inspected for this account. The available article text does not establish the platform list, crawl date, redirect handling, exact URL scope, or structural scoring rules. Treat the counts as GrowNexus-reported findings, not a verified census or a representative measure of all SaaS companies.
GrowNexus also says files larger than 50 KB can consume more than 15,000 tokens before an agent’s first tool call. That should not be treated as a universal conversion or an independently measured outcome: token use varies with content and tokenization, and the article’s indexed text does not provide enough method detail to assess that estimate.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →What llms.txt is—and what it is not
The proposal, titled “The /llms.txt file, v2,” describes a Markdown file at a website root or subpath that gives language-model agents concise context and links to useful material. Its author, Jeremy Howard, published it on September 3, 2024 and modified it on August 10, 2026. Howard describes the idea this way: “We propose adding a /llms.txt markdown file to websites to provide LLM-friendly content.”
The file is a proposed navigation aid, not an established enforcement standard. It does not replace robots.txt, which communicates crawler access instructions, or sitemap.xml, which can inventory URLs. The intended value is curation: point an agent toward the information most useful for understanding a product, API, or site without requiring it to start with an exhaustive crawl.
Rank #2
What the v2 format asks teams to publish
The required element is an H1 naming the project or site. The proposal describes a short blockquote summary, explanatory text, and H2 sections containing lists of Markdown links as optional structure. Optional sections let agents skip secondary material when context is limited; they should not become an excuse to bury essential API information.
A useful index for an API team might link to authentication, quick-start instructions, API reference pages, versioning or deprecation policies, error handling, and limits. Keep it concise and selective, and make sure the linked pages are current and readable as Markdown or otherwise friendly to agents. The file should guide readers to detailed documentation rather than duplicate it wholesale.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
- Income And Expense Log Book: This Income and Expense Record Book（8.5" x 10.5"） is a necessary item for any small business owner or entrepreneur. It is an essential part of any business - helping you understand your overall earnings to determine if you are profitable.
- Daily Tracking and Weekly Overview: let our log tell you if you are profitable today! There are two pages per week to help you you track your income and expenses. At the end of each day or week, you can note whether you made a profit or a loss for the day.
- Clear P&L Statement For Your Business: This income and expense book makes it easy to see your expenses and how they fluctuate from time to time. This makes it easy for you to decide where you can cut back on expenses and assess your total annual net profit.
- Main Features: Expense Review + Income Review + Weekly Pages + Summary of The Year + Twin-Wire Binding + Waterproof Cover + Rounded corner design + Thicker paper
- Effective Organization: This budget book has a twin-wire binding and you can easily lay it flat at 180°. This effective design can help you work better and bring you great convenience in the process of using.
How v2 makes the file and Markdown pages discoverable
The proposal recommends standard link relations so a browser, crawler, or agent can discover both Markdown alternatives and the relevant index. Either relation may be conveyed in an HTML <link> element or an HTTP Link: response header.
| Relation | Purpose | Example form |
|---|---|---|
alternate with type="text/markdown" |
Identifies a Markdown version of a page. | <link rel="alternate" type="text/markdown" href="…"> |
describedby |
Identifies the llms.txt file that covers a page. |
<link rel="describedby" href="…/llms.txt"> |
For Markdown twins, the proposal allows a URL formed by appending .md to the existing page URL or replacing its extension with .md. An llms.txt file can also live below the root: a file at a subpath describes URLs beneath that path, and when several files apply, agents should use the most specific one. That makes it possible to maintain separate indexes for a product site and a large documentation area.
Rank #4
Why adoption percentages depend on the crawl
Another audit illustrates how URL scope affects reported adoption. GeoSalience says it crawled 100 domains on May 19, 2026 and found an apex-domain llms.txt on 37 of them; within its 20 top SaaS domains, it found one on 14 (70%). Its probe checked only https://<brand>.com/llms.txt. A file hosted only on a documentation subdomain or deeper path counted as absent, and GeoSalience notes that this approach missed files on Anthropic and Mintlify documentation surfaces.
That is useful context, not a direct validation or refutation of GrowNexus’s 72% result. The samples, dates, and URL rules are not shown to be equivalent. To compare adoption studies meaningfully, check whether they align on:
Recommended Free Tools
- Sample and date: which companies or domains were selected, and when they were checked.
- URL coverage: apex domains only, or also documentation subdomains and deeper paths.
- Request handling: how redirects, response status, and content type affect whether a file counts.
- What “adoption” means: merely publishing a file, meeting a structural checklist, or exposing discovery relations.
- Discovery checks: whether the audit inspects HTML, HTTP headers, or both.
The supplied GrowNexus article text does not expose enough detail to score all those criteria, and its reported percentages should not be generalized beyond its described sample.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How an engineering team can approach implementation
For a team deciding whether to support the convention, focus first on useful documentation and reliable discovery rather than treating a file’s mere presence as the goal.
- Choose a scope. Decide whether the index covers the main site, API documentation, or a particular product area. Put it at the corresponding root or subpath.
- Curate the index. Add the site or project name as an H1, then a short summary and optional sections of links. Prioritize pages agents need to answer real user questions.
- Publish Markdown-friendly destinations. Where available, provide Markdown page versions and identify them with
rel="alternate" type="text/markdown". - Expose the covering index. Add
rel="describedby"for the applicablellms.txtthrough an HTML link element, an HTTPLink:header, or both. - Check the paths agents will encounter. Verify the file and linked pages resolve at the intended root or subpath, and keep the index aligned with documentation changes.
This is an implementation path consistent with the proposal, not a claim that every site or crawler already supports or honors these relations. The practical test is whether the index reliably points an agent to accurate, relevant API material.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
