An llms.txt file is a short Markdown document you place at the root of your site that lists your most important pages with a sentence about each, meant to give AI models a clean map of your best content. You don't need a generator tool to build one; you can write a good one by hand in an afternoon. Below is the step-by-step, but the honest framing first: llms.txt is a proposed standard that no major AI engine has confirmed it reads, so treat this as a low-effort, tidy-house move, not a ranking lever. Get your real fundamentals right first.
With that expectation set, here's how to build a clean one, because if you're going to add the file, adding it correctly costs almost nothing.
What is an llms.txt file, really?
It's a plain-text, Markdown-formatted file, named llms.txt, that lives at your domain root and points AI models to your key pages. The idea, proposed in 2024, is analogous to robots.txt or sitemap.xml: a single predictable location where a firm can hand a model a curated list of its best, most citable content instead of making it crawl the whole site. It's a map you write for machines.
The critical caveat is that adoption is unconfirmed. No major AI engine has publicly committed to reading llms.txt, so it may do nothing today. That doesn't make it harmful, since a well-made one is just a clean summary of your site, but it does mean you should build it after the things that demonstrably matter, not instead of them. We lay out that honest cost-benefit in full in whether llms.txt matters for law firms. This walkthrough is for firms that have the fundamentals handled and want the file done right.
Step 1: List the pages worth including
Start by choosing your genuinely important pages, the ones you'd want an AI to cite. For a law firm that's usually your homepage, each practice-area page, your attorney bios, your main location or contact page, and your strongest guides or FAQ content. Leave out thin pages, tag archives, and anything you wouldn't want representing you. The file is a highlight reel, not a full sitemap, so curation is the whole value.
Keep the list focused. A dozen strong, distinct pages beats fifty that include every thin post, because the point is to show a model your best, clearest content. If a page wouldn't make a good citation on its own, it doesn't belong in the file.
Step 2: Write the structure in Markdown
The format is simple Markdown. Begin with a top-level heading that names your firm, add a short blockquote summarizing what you do, then group your links under section headings with a one-line description each. A basic skeleton looks like this:
# Smith Family Law
> A family law firm in Austin, Texas, handling divorce, custody, and support.
## Practice Areas
- [Divorce](https://example.com/divorce/): How divorce works in Texas and how we handle it.
- [Child Custody](https://example.com/custody/): Custody arrangements, process, and what to expect.
## About
- [Attorney Jane Smith](https://example.com/attorney/): Bar admissions, background, and experience.
## Guides
- [Property Division FAQ](https://example.com/property-faq/): Answers to common questions on dividing assets.
Use full absolute URLs, keep each description to one honest sentence, and group related pages under clear headings. That's the entire structure. There's no hidden syntax, which is exactly why a generator tool adds little; the format is meant to be hand-writable.
Step 3: Write good descriptions
Each line's description is where the file earns its keep, so write it the way you'd want an engine to understand the page: specific, plain, and accurate. "How property is divided in a Texas divorce, with the community-property rules explained" tells a model far more than "Learn about our divorce services." Describe what the page actually answers, not what you wish it ranked for.
Keep the descriptions honest and matched to the page's real content, because a mismatch between your one-liner and the page helps no one and could read as manipulation. Think of each line as a clean, truthful summary a person could act on. If the descriptions are good, the file is good; if they're marketing fluff, the file is pointless.
Step 4: Place it and check it
Save the file as llms.txt and put it at your domain root, so it loads at yourdomain.com/llms.txt, the same convention as robots.txt. It needs to be reachable at that exact path as plain text, not tucked in a subfolder. Once it's live, open the URL in a browser to confirm it loads cleanly and the links work.
Some sites also add a longer llms-full.txt containing expanded content, but for most law firms the basic llms.txt is plenty, and there's little sense maintaining more until any engine confirms it uses the standard. Verify the file loads, spot-check that every link resolves, and you're done. It's the kind of thing worth confirming the same way you'd confirm your schema is valid before trusting it, which we cover in how to test your law firm schema before it goes live.
Do the things that actually matter first
Before you spend any energy here, make sure an AI engine can read your site at all, because that foundation decides everything and llms.txt sits far downstream of it. If your pages depend on JavaScript to render their content, a model may see nothing regardless of how tidy your llms.txt is, which is why server-rendered, machine-readable pages come first, covered in why law firm sites should be readable without JavaScript.
So the order of operations is: get the fundamentals right, real answer-first content, valid schema across the seven types every law firm site needs, a crawlable and JavaScript-free-readable site, then add llms.txt as a clean finishing touch. Done in that order, the file costs an afternoon and does no harm, and if the standard gains traction you're already set. To see whether the fundamentals underneath it are in place, run the free audit, and the deeper machine-readability work is the core of our AEO service.
