How llms.txt improves AI visibility and helps models find your best pages
llms.txt is a plain-text file at your site root that lists the URLs you want AI systems to prioritize. It does not replace robots.txt or rankings — it helps models discover your strongest answer pages faster.
Last updated: 23 August 2026
Publish a clear map of priority pages, keep it in sync with your sitemap, then verify GEO readiness on a live URL.
# Your Business> Short description of what you offer## Pages- https://yoursite.com/services- https://yoursite.com/pricing- https://yoursite.com/locations/dubaiWhy do models need llms.txt if you already have a sitemap?
Sitemaps list indexable URLs for search engines. llms.txt is a human- and model-readable shortlist of the pages you care about for answers — especially when the homepage is a weak citation source.
What sitemaps do
Help Google and Bing discover and recrawl URLs. They are not optimized as a curated “cite these first” brief.
What llms.txt adds
A concise index of priority pages with optional notes — easier for retrieval tools to skim than a full XML sitemap.
What to put in llms.txt
Keep it short, accurate, and served as text/plain at https://your-domain/llms.txt.
Serve it at the domain root
The file must be reachable at /llms.txt — not buried in /docs or /blog.
Lead with who you are
A short header and one-line description of the business or product.
List only high-intent URLs
Services, pricing, locations, comparisons — not every blog post.
Use absolute HTTPS links
Full URLs reduce ambiguity for crawlers and agents.
Keep it in sync after publish
When you ship a new GEO page, add it to llms.txt the same day.
Do not contradict robots.txt
Never list URLs that Disallow retrieval bots — you will confuse both systems.
Inseo checks for llms.txt and drafts a file aligned to your priority pages.
Common llms.txt mistakes
Avoid these when teams rush a file live without a citation plan.
| Pattern | Looks fine | Still weak for AI |
|---|---|---|
| Location | File exists somewhere | Not at /llms.txt on the apex domain |
| Content | Long dump of every URL | No priority signal — models ignore noise |
| Format | HTML page titled llms | Must be plain text, not a styled page |
| Freshness | Created once | Missing new landing pages after publish |
| Access | File public | robots.txt still blocks GPTBot |
How do you ship llms.txt well?
Treat it like a living map of citation targets, not a one-off SEO checkbox.
What is a good minimal example?
A title, one-line description, and 5–15 absolute links to pages that already answer real questions.
Does llms.txt replace robots.txt?
No. robots.txt controls access; llms.txt suggests priority pages. You need both for GEO.
What if my CMS cannot upload root files?
Host the file elsewhere and 301 /llms.txt to it, or use a platform that supports root static files.
How does Inseo help?
Analysis flags a missing llms.txt and generation can draft contents pointing at the URLs that matter.
How Inseo helps
Draft llms.txt from your real site structure
Analyze a live domain to see whether llms.txt is missing or thin, then generate a GEO blueprint that includes a practical draft.
- Ready checks detect missing or unreachable llms.txt
- Blueprints reinforce answer pages worth listing
- Free preview before you spend a generation
Questions about llms.txt
Is llms.txt an official Google standard?
It is an emerging community convention for AI discovery. Support varies by tool, but a clear root file still helps human and agent navigation.
Will llms.txt alone get me cited?
No. It improves discovery of your best pages. Citation still needs crawl access and quotable content.
Should I list the homepage only?
Usually no. List the service and location pages that actually answer user questions.
Can I block training but still allow retrieval?
Often yes via robots.txt and Content Signals — configure carefully and keep llms.txt aligned with what bots may fetch.
Related guides
Step-by-step how-tos and deeper articles for the gaps this page diagnoses.