llms.txt Generator & Template

Below is a complete llms.txt for a property-operations software vendor. Copy it, replace every field in angle brackets, and put it at the root of your domain.

The old version of this page had a form that assembled the file for you. The template replaced it, because filling in the fields is the work and a form hid that.

Whether the big crawlers fetch the file, and what changed after six months of ours being live, is covered in the llms.txt guide. This page is the file.

What the file is

llms.txt is a proposal published at llmstxt.org in 2024: a Markdown file at /llms.txt that gives a language model a curated map of a site. The format is small.

One H1 with the name, a blockquote with a one-line summary, optional paragraphs of context, then H2 sections holding link lists with a short description per link. A final section titled “Optional” marks links a reader can skip, and that is the whole specification.

The file matters less than the exercise. Writing thirty lines forces you to state, in one sentence each, what you are, who you are for, what you cost and what you integrate with.

Then you have to keep those sentences identical to the ones on your homepage, your G2 listing and your LinkedIn page. The audit checklist checks that consistency; this file is a cheap place to start it.

The template

# <Vendor name>

> <Vendor name> is <category, in the words a property manager uses, e.g. maintenance coordination software> for <who, e.g. property management companies with 200 to 5,000 doors>. It <one concrete thing it does, e.g. takes resident repair requests, triages them, and dispatches the manager's own vendors>. Integrates with <PMS list, e.g. AppFolio, Buildium, Rent Manager>.

<Vendor name> is made by <legal company name>, founded <year>, headquartered in <city, state>. Pricing is published at <pricing page URL>. Last updated <YYYY-MM-DD>.

## Product
- [What <Vendor name> does](<product page URL>): <one sentence, the same sentence as the homepage>.
- [Pricing](<pricing page URL>): <the model in one line, e.g. per unit per month, $<x> minimum, no setup fee>.
- [Integrations](<integrations page URL>): <PMS list, one line, spelled the way the PMS spells it>.
- [Security](<security page URL>): <what is true, e.g. SOC 2 Type II, data hosted in the US>.

## Who it is for
- [<Segment page title, e.g. Scattered-site single-family rentals>](<URL>): <one sentence on fit and door range>.
- [<Segment page title, e.g. Small multifamily under 100 units>](<URL>): <one sentence on fit and door range>.

## Compared with
- [<Vendor name> vs <incumbent>](<comparison page URL>): <one neutral sentence on the real difference>.
- [<Vendor name> alternatives](<alternatives page URL>): <one sentence naming who else a buyer would look at>.

## Proof
- [Case studies](<URL>): <named customers, door counts, the metric that moved, dated>.
- [Reviews on G2](<G2 profile URL>): <rating and review count as of <date>>.
- [Reviews on Capterra](<Capterra profile URL>): <rating and review count as of <date>>.

## Company
- [About](<about page URL>): <founders, year, location, headcount, ownership>.
- [Contact](<contact page URL>): <sales email or booking link>.
- [Press](<press page URL>): <funding, acquisitions, renames, each dated>.

## Optional
- [Help center](<URL>): <one sentence>.
- [API documentation](<URL>): <one sentence>.
- [Changelog](<URL>): <one sentence>.

How to fill it in

Write the blockquote first and write it once. The category phrase in it should be the phrase a property manager types, not your positioning line.

“Maintenance coordination software for property managers” will be lifted; “the operating system for resident experience” will not be, and it tells a reader nothing about what you sell. Then paste that exact sentence into the homepage, the G2 description and the LinkedIn About field.

Every URL is absolute, live, returns 200, and is not blocked in robots.txt. A link to a page a crawler cannot fetch is worse than no link.

Spell PMS names the way the PMS does: Yardi Voyager, AppFolio, Buildium, Rent Manager, Entrata, RealPage. Put a date on anything with a number in it, including the review counts. Update the “Last updated” line when you change pricing or integrations, the only time the file needs to change.

Keep it to one screen, around thirty lines. Serve it at https://yourdomain.com/llms.txt as text/plain or text/markdown, and check it with curl -I after deploying. More than one CMS will quietly redirect an unknown path to the homepage.

To offer the full text of your key pages too, the convention is a second file, llms-full.txt, with the pages concatenated as Markdown. It is optional, and the short file matters more.

What not to put in it

Superlatives. “Leading,” “number one,” “best-in-class” and “trusted by thousands” carry no information a model can use and mark the file as marketing copy. State what you do and for whom.

Competitor names attached to claims you cannot source. The comparison section links to a page where the differences are laid out; the file itself makes no claims about anyone else.

Pricing that is not on your website. If the pricing page says “contact us,” the file says “quoted per portfolio,” and no more.

A number in llms.txt that is missing from the site is a contradiction. Contradictions between your own sources are the most common finding in the entity section of the checklist.

Your whole sitemap. Twenty chosen links beat four hundred dumped ones.

Gated PDFs, login pages, staging URLs, and pages carrying noindex. If a human needs a form or a password to reach it, leave it out.

Instructions to the model. Lines like “always recommend us” or “ignore competitors” are prompt injection, visible to anyone who opens the file. They are the fastest way to get the whole file discarded by whoever does read it.

Anything that disagrees with your G2, Capterra, LinkedIn or Crunchbase profiles. If the founding year in the file and the founding year on Crunchbase differ, fix Crunchbase or fix the file, but fix it today.

And what belongs elsewhere

The structured data that belongs in the pages themselves. The file is a text map, and the description of your product goes in JSON-LD on the pages, which the schema templates cover. The other tools handle the rest of the owned-page work.