--- type: Article name: "\"Add an llms.txt file and you're SEO-optimised for AI.\" There's no ranking signal involved. What it's for is narrower and more specific." id: "https://selfe.ai/insights/myth-vs-fact/add-an-llms-txt-file-and-youre-seo-optimised-for-ai" url: "https://selfe.ai/insights/myth-vs-fact/add-an-llms-txt-file-and-youre-seo-optimised-for-ai" publisher: "did:web:selfe.ai" description: "An llms.txt file isn't a ranking mechanism, and treating it like a new kind of SEO misreads what it's for. What it can genuinely help with is narrower and more useful: telling an AI agent what a business can do, not making its content rank better anywhere." datePublished: "2026-09-15T15:35:35.873Z" author: The Selfe team --- # "Add an llms.txt file and you're SEO-optimised for AI." There's no ranking signal involved. What it's for is narrower and more specific. > An llms.txt file isn't a ranking mechanism, and treating it like a new kind of SEO misreads what it's for. What it can genuinely help with is narrower and more useful: telling an AI agent what a business can do, not making its content rank better anywhere. ## In short - An llms.txt file isn't SEO. There's no ranking mechanism it feeds, so "optimising" it doesn't mean what SEO used to mean. - What it can genuinely help with is narrower: pointing an agent toward what a business can do, not describing it persuasively. - It's still a static file at a domain root, hoping to be found the way robots.txt or a sitemap always has been. - Selfe makes a business's facts continuously and directly reachable, rather than relying on a file being found and read correctly. A file at the root of a domain borrowed a sitemap's old habits. It was never going to borrow a sitemap's old job too. ## What it isn't A bed and breakfast owner adds an llms.txt file to the site, the way she once added a sitemap, and describes it to a colleague as "SEO for AI." Nobody corrects her, because the file lives in the same spot a sitemap does and gets talked about in the same breath. It isn't doing the same job at all. Nothing about an llms.txt file makes a business rank higher in an AI-generated answer the way better SEO used to improve search rankings. There's no algorithm being fed a signal here. A file at the root of a domain, describing a site in plain language, doesn't compete for attention the way a search result does. Calling it "SEO for AI" borrows a framework that doesn't apply. ## The job it does instead Where it genuinely helps is narrower: pointing an agent toward what a business can do, not describing what the business says about itself. A well-written one tells an agent this is a bed and breakfast, here's where the booking information lives, here's what an agent can check or do here, more like a signpost toward capability than a description written to be read and enjoyed. ## Its own real limit Even used well, it's still a file sitting at a domain's root, following a convention, hoping to be found and read the same way robots.txt or a sitemap always has been. That's a real improvement over nothing. It's still the same shape as a chat widget or extended page markup: a text file layered onto the existing website-and-crawler model. A business's own facts, made directly and continuously reachable, is a different thing entirely. ## Where this shows up for a business A business's real facts stay continuously and directly reachable through Selfe, rather than relying on a static file at a domain root to be found, read and correctly interpreted by whatever's looking. ## Should we bother adding one at all? It's a reasonable, low-effort thing to have. Just don't expect it to do the job structured, connected facts do. ## What should it say? What an agent can do here, availability, booking, terms, in plain language, rather than a persuasive description of the business. ## Act on this - [Check whether an agent can buy from you](https://selfe.ai/agentic-commerce/buyability-check) — the free readiness scan. - [Discover venues](https://selfe.ai/api/registry/discover) — `POST`, semantic browse across the registry. - [Match a bookable answer](https://selfe.ai/api/registry/match) — `POST` with dates and party size. - [Verify Selfe's identity](https://selfe.ai/.well-known/did.json) — `did:web:selfe.ai`. - [Agent card](https://selfe.ai/.well-known/agent-card.json) — how to connect over A2A or MCP.