What should I put in the summary field?

Use one plain-English sentence that explains what the company or website does without slogans or vague positioning language.

Which pages belong in the core page list?

Include the pages an AI agent should trust most: usually product, pricing, docs, security, support, and contact.

Can I start from a live URL instead of from scratch?

Yes. The scan flow can prefill the builder from a homepage, then you can edit the summary, links, and guidance before downloading.

Where do I publish the generated file?

Put it at /llms.txt on the root of your domain so the final URL is stable and public.

AI-readiness builder

Generate a production-ready `llms.txt` file.

Use the builder to create a concise machine-readable summary of your site’s purpose and key links, or scan a live URL to prefill the first draft for a stronger AI-readiness layer.

AI-readiness scan

Scan a homepage and prefill your builder.

We inspect the homepage title, meta description, and important same-domain links through our server-side scan endpoint, so the scan is not blocked by normal browser cross-origin limits.

Site basics

Website name Website URL One-sentence summary

Core pages

These are the pages AI tools usually need first.

Homepage Product Pricing Docs API Security Support About Blog Contact

Custom pages

Additional important pages

One page per line: path | label | why it matters

Guidance for AI tools

Optional context

One instruction per line.

AI-readiness references

Use the builder with pages that clarify scope.

The builder works best when the site summary, canonical pages, and publishing path are already clear. These references help tighten those decisions before you generate a final file.

What is llms.txt?

Use this if you need a clean internal explanation before publishing.

llms.txt vs llms-full.txt

Use this if the root file starts getting too broad.

Publishing mistakes

Use this as a final QA sweep before you ship.

Generate a production-ready llms.txt file.