Step 01
Paste your URL
We crawl your public site, follow sitemap hints, and pick the pages AI systems should know about—no manual sitemap upload.
Paste your URL and get a clean llms.txt that your site can publish today, built to the spec ChatGPT, Claude, and Perplexity look for.
Sign in free · Strategy docs + llms.txt in minutes
How it works
Publish once. Re-run when you ship new pages or reposition.
Step 01
We crawl your public site, follow sitemap hints, and pick the pages AI systems should know about—no manual sitemap upload.
Step 02
Rankealo builds llms.txt (and llms-full.txt) with titles, descriptions, and sections aligned to how ChatGPT, Claude, and Perplexity discover sites.
Documents
Step 03
Host at yoursite.com/llms.txt, edit in your dashboard, and connect GEO monitoring so fixes land in your daily queue.
Why llms.txt
Search is splitting: classic Google results on one side, and ChatGPT, Claude, Perplexity, and Gemini pulling answers on the other. llms.txt is the lightweight map that tells AI systems which pages matter, how to describe them, and what your site is actually about—without making models crawl your entire sitemap blind.
< 1 min
llms.txt ready
5+
Strategy docs included
100B+
AI queries per month
GEO
Audit + fix cards
You came for llms.txt. You stay for a daily SEO + GEO operating system—queue, agents, and measurable fixes.
Strategy docs, competitors, and brand voice sit next to technical files—editable, versioned, and tied to your domain—not a one-time export.
Today's queue
GSC data, GEO audits, LLM visibility, and content decay roll into one prioritized list every morning—so you work on what moves rankings.
coding-agent · PR opened
feat: add /llms.txt + sitemap link
Approve actions from the dashboard, trigger fixes via MCP in ChatGPT or Claude, or let the coding agent open a PR—same queue, multiple surfaces.
Free onboarding gives you the artifact and strategy docs. Paid plans unlock the full queue, GEO fix cards, GSC sync, and agent execute flows.
llms.txt is a proposed standard: a Markdown file published at the root of a website — yoursite.com/llms.txt — that gives large language models a short, curated map of the site’s most important content. It was proposed by Jeremy Howard of Answer.AI on 3 September 2024.
A sitemap is exhaustive: every URL you will admit to having. llms.txt is the opposite — a deliberately short, human-curated shortlist with a sentence of context beside each link, so a model reading a few thousand tokens lands on the pages that actually represent you rather than a pagination archive.
Worth stating plainly: llms.txt is a proposal, not a ratified web standard. Neither the W3C nor the IETF has adopted it.
They are often mentioned together and they do opposite jobs. robots.txt restricts what a crawler may fetch. llms.txt recommends what a model should read. One is a fence, the other is a map — and publishing one says nothing about the other.
| Dimension | llms.txt | robots.txt |
|---|---|---|
| Purpose | Curation. Points models at the pages that represent you best. | Crawl control. Tells crawlers which paths they may fetch. |
| Format | Markdown: an H1, an optional summary blockquote, then H2 sections of annotated links. | A line-based directive syntax: User-agent, Allow, Disallow, Sitemap. |
| Audience | Large language models and AI agents reading your site as context. | Search and AI crawlers deciding what to request. |
| Default posture | Opt-in. Nothing happens unless you write and publish the file. | Assumed present. Most crawlers look for it on every site. |
| Enforcement | Advisory only. No provider has committed to reading it. | Still advisory, but widely and consistently respected by named crawlers. |
Need the other half? Build your robots.txt file and set your crawl rules before you hand anyone a reading list.
Most pages selling you an llms.txt file will not answer this honestly, so here it is. The evidence is mixed, and the case for publishing one does not rest on it being a ranking signal.
Our position: publish it as low-cost insurance, and treat writing it as a content-curation exercise. The half hour you spend deciding which twenty pages represent your business is worth more than the file itself — and if providers do standardise on it, you are already there. Just do not build an AI-search strategy on top of it.
By hand it is about thirty minutes of work, most of it deciding what to leave out.
Homepage, product or service pages, pricing, docs, and your best guides. Ten to thirty links is plenty. Leave out tag archives, author pages, and legal boilerplate — curation is the whole point.
An H1 with your site or product name, an optional blockquote summarising what you do, then H2 sections (Docs, Product, Guides) containing Markdown links with a one-line description each.
Serve it at yourdomain.com/llms.txt as plain text with a 200 response, and make sure robots.txt does not block it. If you want an expanded version, publish the full content at yourdomain.com/llms-full.txt.
A stale llms.txt is worse than none — it hands models dead links and old positioning. Revisit it whenever you ship a new product page or restructure your docs.
Paste your domain at the top of this page and Rankealo analyses your site, picks the source-of-truth pages, and hands you an editable llms.txt alongside the rest of your free strategy run.
llms.txt is a proposed standard: a Markdown file published at the root of a website (yoursite.com/llms.txt) that gives large language models a short, curated map of the site’s most important content. It was proposed by Jeremy Howard of Answer.AI in September 2024. It is a proposal, not a ratified web standard — neither the W3C nor the IETF has adopted it.
At the root of your domain, so it resolves at yoursite.com/llms.txt. It should return HTTP 200 as plain text, and it must not be blocked in robots.txt. Each subdomain that serves its own content needs its own file. If you also publish an expanded version, the common convention is yoursite.com/llms-full.txt.
There is no public commitment from any major AI provider that they read llms.txt in their production answer surfaces. Google’s own guidance states you do not need special machine-readable files to appear in Search or its AI features, and Google’s John Mueller said in mid-2025 that no AI system was using llms.txt at the time. Some agent and developer-tool workflows do fetch it. Treat it as cheap insurance and a useful curation exercise, not as a ranking lever.
llms.txt is the short index: headings, one-line descriptions, and links to your key pages. llms-full.txt is the expanded companion that inlines the actual content of those pages into a single file, so a model can read everything in one request. The original proposal describes generated context files (llms-ctx.txt and llms-ctx-full.txt); the /llms-full.txt filename most sites use today is a community convention that grew out of it.
Going deeper: see which bots actually reach your site in our guide to AI crawlers, or start with the fundamentals of generative engine optimization.
If you searched for llms.txt generator, these tools solve adjacent formatting, technical SEO, and content-optimization tasks without leaving the workflow.
Create a robots.txt file for your website in seconds.
Audit a page for AI search and GEO readiness.
Score your site for AI search and GEO basics.
See which AI bots your robots.txt allows.
Preview how your site looks when shared on social media.
Generate JSON-LD schema markup for common page types.
One closed loop across content and AI answers. Per domain — subscribe monthly or save 20% annually.
Close the loop on one site: find the gap, publish the article, re-measure the lift.
$99/mo · billed $948/year
7-day money-back guarantee Terms apply
Everything to run content autopilot + weekly AI visibility on one domain:
A daily pulse on how AI answers describe you — across more prompts, engines and cities.
$249/mo · billed $2,388/year
7-day money-back guarantee Terms apply
Everything in Starter, plus a daily read on your AI visibility:
Multiple sites or done-with-you rollout? We'll shape a plan around your portfolio.
Volume pricing on 2+ domains
Talk to us →Reply within one business day
For teams running many domains:
Running more than one site? Save 10% on sites 2–4 and 20% on 5+ — discounts apply automatically at checkout. 10+ sites? Talk to us.