llms.txt is a proposed Markdown file at a site’s root that gives large language models a short, curated guide to the site’s most important pages. For B2B companies it can point AI assistants to product overviews, pricing logic, security documentation, integration lists and case studies. It is quick to publish, but support across AI platforms is limited, so treat it as one small part of a wider plan.
Why might a B2B site bother with it?
B2B buyers increasingly ask AI assistants to compare vendors, explain integrations or summarise security practices. B2B websites are often large, with product pages, documentation, blogs and gated content mixed together. A curated file tells any assistant that reads it where the authoritative answers are.
The format was proposed by Jeremy Howard in 2024. Developer platforms and documentation tools adopted it first, and many software companies now publish one. Google has said it does not use llms.txt in Search. Other AI providers have not published firm commitments for their consumer products at the time of writing.
What belongs in a B2B llms.txt?
Think about the questions a buying committee asks and link the page that answers each one.
- Product overview: what the product does, for whom, in plain terms.
- Pricing page or pricing model explanation, even if exact prices are on request.
- Security and compliance: SOC 2, ISO 27001, GDPR or KVKK statements, data residency.
- Integrations list and API documentation.
- Implementation guide: timelines, roles, what the customer must provide.
- Case studies grouped by industry.
- Company facts: founding, headquarters, leadership, contact.
Each link gets a one-line description written as a fact, not a slogan.
How should the file be structured?
The proposal suggests an H1 with the company name, a short blockquote summary and H2 sections with link lists. A B2B example might have sections titled “Product”, “Security”, “Integrations”, “Customers” and “Company”, with three to eight links each. Keep the whole file readable by a person in two minutes.
Optional full-text file
An llms-full.txt file can hold the full text of core pages, such as the product overview and security page, in one document. This helps tools that prefer one fetch. Keep it updated, or it becomes a source of outdated claims.
How do you publish it?
- Place the file at https://yourdomain.com/llms.txt and serve it as text/plain or text/markdown.
- Make sure robots.txt does not block it.
- On WordPress, upload to the web root or use a plugin; on HubSpot or Webflow, check whether root files are supported or use a redirect from the root path.
- Avoid redirects to another domain, which some tools will not follow.
- Add it to your content review calendar alongside pricing and security pages.