Every so often a new file convention makes its way through the web and lands on our desks with a small flurry of questions. This year that file is llms.txt. It sits at the root of a domain, right next to robots.txt and sitemap.xml, and it is meant to give large language models a clean, human-written summary of what your site is about and where the important pages live.
Since April, Shopify has quietly shipped one for every storefront on its platform. Documentation sites for open-source tools have adopted it in large numbers. A handful of the ministry websites we help maintain have started asking whether they should follow suit.
The honest answer is more layered than either yes or not yet, and we think church and ministry leaders deserve the full picture before spending a Saturday on it.
What llms.txt actually is
At its simplest, llms.txt is a markdown file listing the parts of your site that best represent your work. There is a short description at the top, and a small tree of links underneath. Think of it as a hand-curated map, written for a reader who does not want to crawl your whole site.
The format is not enforced by any browser, search engine, or law. It is a proposed convention that some AI tools and developer environments have started respecting, and that a growing number of publishers have started publishing. As of the middle of 2026, roughly one in eighteen of the top ten thousand sites has a valid one. That number is climbing, but slowly, and mostly because of platform defaults rather than individual decisions.
What it does not currently do
Here is the part we think church leaders should hear plainly. As of this summer, having an llms.txt file does not measurably improve your odds of being cited by ChatGPT, Claude, Gemini, or Perplexity when someone searches for a church, a Christian counselor, or a ministry near them. The crawlers those tools depend on largely ignore the file today and read your HTML directly.
That may change. It also may not. Standards on the web have a long history of arriving, gathering some fans, and quietly fading when the ecosystem does not follow. We would not build our AI-search strategy around this one file, and we would not lose sleep if your site does not have it yet.
Where it is genuinely useful today
The place llms.txt is doing real work right now is inside developer tools. AI-assisted code editors like Cursor and Continue, documentation servers built on the MCP protocol, and internal knowledge bots often look for the file when pointed at a site. If your ministry publishes technical documentation, an API, a research library, or a knowledge base that other developers or agents might consume, an llms.txt file will make their experience faster and more accurate.
For a typical church website, that use case is rare. For a Christian nonprofit publishing open research, a seminary hosting a document library, or a faith-based software project, it is worth doing.
What a good ministry llms.txt looks like
If you do decide to publish one, keep it short. A working church file might name the ministry, describe its purpose in a sentence, and list a handful of the pages that most represent your work. Usually that means the plan-your-visit page, an about page, a beliefs or values page, a giving page, and a sermon archive. Ten to twenty links, each with a plain-English description. That is often the whole file.
Longer is not better. The point is to be a quick, honest map. Anything you would not want a first-time visitor to read as your one-paragraph introduction to the church does not belong on it.
We also encourage ministries to write the descriptions in the same voice they use everywhere else. Not marketing copy, not a mission statement pulled from a bylaws document, just plain sentences that describe what each page is for. If a language model does eventually quote your file, that voice is what will show up in the answer.
What to focus on instead
For most churches and ministries we work with, the ordinary work of a well-built website still moves the needle far more than a new file at the root. Clear headings on important pages. Descriptions that read like sentences and not slogans. Structured data on services, staff, and events. A sitemap that stays current. Content written to answer the real questions that real people are typing into search bars and AI chats.
All of that is what actually gets your church quoted when a family in your city asks their favorite assistant which congregations offer Sunday evening services or which ministry runs the recovery group they are looking for. llms.txt might one day sit alongside those signals. It does not replace any of them.
Our current recommendation
We are shipping llms.txt files on new projects when it takes twenty minutes and costs nothing. We are not going back to older sites to add one unless the client asks. We are watching adoption numbers and citation studies, and we are ready to update this position the moment the data actually shifts.
If your church website is being built or rebuilt this year, ask your developer to include a small, honest llms.txt. If your site is already live and running well, this is not the item to move to the top of the list. There are almost certainly two or three older pages, one form that does not work on a phone, and a sermon archive that needs a search box, all ahead of it.
Ministry websites are meant to serve real people first, and the machines that summarize them second. When both are cared for, the site tends to do its quiet, faithful work for years without asking for much attention.
If you would like a hand thinking through what belongs on your church or ministry site in 2026, from the everyday pages to the small technical files most sites forget, reach out through our contact page and tell us where things stand.