llms.txt generator

Builds an llms.txt file and the robots.txt crawler directives that go with it. It emits both because the most common error we find is a site publishing llms.txt while robots.txt blocks the crawlers that would read it.

What the organisation does, in a sentence a model could quote.
Key pagesThe pages you would want a model to read first. Paths or full URLs both work.
AI crawlers to allowAnything unticked is blocked in the robots.txt below. For most businesses, allowing all of these is the right call — blocking them removes you from the answers your buyers read.

/llms.txt

# Your organisation

> One sentence describing what this organisation does.

## Key pages

- [Add at least one page above](https://example.com/): what it covers

/robots.txt directives

# Crawler policy.
# Allowing an AI crawler means your content can appear in the answers it
# generates. Blocking one removes you from those answers entirely.

User-agent: *
Allow: /

User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: PerplexityBot
User-agent: ClaudeBot
User-agent: Google-Extended
User-agent: Applebot-Extended
User-agent: CCBot
Allow: /

Sitemap: https://example.com/sitemap.xml

Before you publish this

llms.txt is a proposal, not a standard. No major engine has committed to honouring it and there is no reliable public evidence that models fetch it. It costs little to publish and it is not a visibility strategy — the robots.txt half of this output matters considerably more, because that one is actually enforced.

The crawler decision is strategic rather than technical. Blocking AI crawlers removes you from the answers your buyers read. For most businesses that is the worse trade; publishers are the genuine exception, because there the content is the product rather than a route to it.

Related reading