Foundation
Publish a root llms.txt
Place it at yourdomain.com/llms.txt so assistants have a stable, public guide to your best pages. Use the full checklist post to work through the details.
Build your AI-readiness file
Scan a live URL
Improve AI readiness
Publish at /llms.txt
Chrome Lighthouse describes /llms.txt as a machine-readable site summary for AI agents.
llms.txtllms.txt is a practical way to improve AI readiness by helping systems route to, understand, and cite your canonical pages more clearly.
Scan a live homepage to prefill the builder below.
Tracked in the live directory snapshot referenced on this site.
Start from a URL or from scratch, then tune the summary and canonical pages inline.
The generated file is designed to be published directly at /llms.txt.
AI-readiness builder
llms.txt file.The output updates as you edit. Start from a URL or from scratch, then download a root-ready file you can publish directly.
AI-readiness scan
We inspect the homepage title, meta description, and important same-domain links. The scan runs through our server-side endpoint so it can inspect live sites without normal browser CORS limits.
AI-readiness checklist
Think of this as the minimum viable structure for being understandable, citeable, and trustworthy.
Foundation
llms.txtPlace it at yourdomain.com/llms.txt so assistants have a stable, public guide to your best pages. Use the full checklist post to work through the details.
Core pages
Make sure product, pricing, docs, and contact pages are current, specific, and better than any secondary summary.
Clarity
Use consistent names for products, plans, and services across your homepage, docs, and metadata.
Maintenance
Update your llms.txt when pages move, product names change, or new canonical resources go live.
AI-readiness library
llms.txt.These pages are written to answer the questions people and AI systems ask repeatedly: what the file is, how it differs from llms-full.txt, how to verify it is live, and where publishing goes wrong.
A durable explainer on what the file does and what it does not do.
When to keep the root file concise and when a full variant helps.
A fast QA checklist for root placement, status codes, and public reachability.
The failure modes that keep a file from being trusted or found.
About this site
llms.txt.llmstxt.ca editorial publishes practical guides, examples, diagnostics, and reference pages focused on root-file implementation and AI-readable site structure.
This site publishes its own /llms.txt and uses the same builder, score, and publishing workflow it recommends.
Built on a .ca domain, but intended as a global implementation resource for teams anywhere.
Compare live files from real product and docs sites.
Run a site check and copy a URL that points other reviewers to the same target.
Use the reference library for stable definitions, comparisons, and QA checks.
FAQ
llms.txt questions.Short, durable answers about what the file is, where it should live, and what still has to be true about the site underneath it.
llms.txt?llms.txt is a machine-readable summary file published at the root of a website. It gives AI agents a direct path to canonical pages like product, pricing, docs, security, and contact.
llms.txt live?Publish llms.txt at /llms.txt on the root domain so it is publicly reachable at a stable URL like https://yourdomain.com/llms.txt.
llms.txt file include?A strong file has a plain-English summary, a short list of important canonical pages, and a few guidance lines about what agents should prefer or avoid inferring.
llms.txt replace strong website content?No. llms.txt helps with routing, not with weak content. The homepage, docs, pricing, trust pages, and contact routes still need to be current, specific, and easy to understand.