Agent Readiness Score
Hub page

llms.txt guides, comparisons, and generation

Use this page as both a generator and a working decision aid. It shows where llms.txt helps, where it does not, and what still belongs to canonical pages, docs, pricing, and robots.txt.

Run a fresh scanAgent readiness hub
Best for
Canonical public references
Not a replacement for
Site architecture
Best companion pages
Docs, pricing, trust pages

Use the file well

What llms.txt is good at

Use it to reduce ambiguity around your best public references, not to paper over weak page architecture.

Pointing assistants toward canonical docs, pricing, policy, and setup pages.
Reducing ambiguity when the same subject appears across many public pages.
Making your preferred public references easier to find in one place.
Supporting a broader site architecture that is already clean and crawlable.

Boundaries

What llms.txt does not fix by itself

If any of these are your real problem, the next fix belongs in the site itself rather than in the file.

It does not repair weak internal linking.
It does not replace canonical tags, sitemap.xml, or robots.txt.
It does not turn thin or contradictory content into trustworthy content.
It should not become an excuse to avoid fixing docs, pricing, or trust surfaces.

Use it operationally

What to check before you generate the file

Reference set
Decide which public pages deserve to be preferred first.
docs
pricing
legal pages
setup or getting-started pages
Canonical hygiene
Make sure those pages already look like the canonical answers.
stable URLs
clear titles
no duplicate campaign variants
Link support
The file should reinforce pages that are already linked into the site.
homepage paths
docs navigation
footer or hub links

Next pages

Continue through the llms.txt cluster

llms.txt example for SaaS

See a practical SaaS-oriented llms.txt shape and what each block is doing.

llms.txt example for docs sites

See how docs-focused references differ from a SaaS-oriented file.

llms.txt vs robots.txt

See where each file helps and where it does not.

Agent readiness checklist for SaaS

A practical checklist for pricing, docs, trust, and action paths.

Generator

Generate a cleaner llms.txt directly

If you already know the brand name, base URL, and site type, generate it here directly. If you came from an audit result page, the inputs can be prefilled.

Practical starter draft

Generate a starter llms.txt for your website

Build a clean llms.txt draft from your brand, site type, and important public pages. The output is deterministic, easy to edit, and ready to copy into your repo.

Project details
Fill in the core public details you want agents to see first.

One URL or path per line. Relative paths like /docs are fine.

Generated llms.txt
Review the draft before you copy it into your site root.
Your generated llms.txt will appear here after you fill in the form and click generate.
What to do next
The first draft should be reviewed by the team that owns docs, pricing, and policy pages.
  • Keep the summary factual and short. This file should guide agents, not replace full documentation.
  • List canonical public pages first. Remove campaign URLs, previews, or private dashboards.
  • Review the boundaries section before publishing so it matches your real support and policy posture.

Next step

Generate the file after you know what it should point to

Use the generator when your canonical docs, pricing, trust, and setup pages are clear enough to deserve promotion. The file should reinforce that structure, not invent it.

Generate llms.txt nowllms.txt vs robots.txt