llms.txt for church websites: what it is and whether you need one

llms.txt is a proposed file for AI tools, not a Google ranking factor. Here is what it does, what Google says, and a short template if your church wants one anyway.

By SermonLingo TeamUpdated 7 min read

What is llms.txt, and does a church website need one?

llms.txt is a proposed convention: a short Markdown file at the root of a website, such as yourchurch.org/llms.txt, that summarizes the site and links to key pages for AI tools. Google says Search ignores llms.txt, so it is not a ranking factor. A church does not need one to be found, though a short, accurate file is harmless if someone keeps it current.

This guide separates the proposal from the marketing around it. It reports what Google's documentation says as of October 2026, helps you decide whether a file is worth an hour of your time, and gives you a template to adapt if the answer is yes.

Where did llms.txt come from, and who reads it?

The idea is laid out at llmstxt.org, a proposal first written in 2024. Its reasoning is simple. Web pages are built for people, with menus, scripts and layout, so an AI tool that wants a quick summary of a site has to dig through clutter. One Markdown file gives that tool a curated starting point.

The format is modest. The only required part is a single heading with the site's name. After that come an optional summary and short lists of links, grouped under headings, each with a one-line note. It is a convention anyone can follow, not a standard issued by a standards body, and nothing obliges a crawler or an assistant to read it.

Who actually reads it is the honest unknown. The proposal's own site says thousands of sites publish the file, used most heavily for software documentation. Chrome's Lighthouse tool has an llms.txt audit inside an experimental agentic-browsing category, but Chrome's page calls the file an emerging convention and treats a missing file as not applicable, because providing one is optional. We could not find a commitment from any search engine or assistant to read or favor a church's file.

What does Google say about llms.txt and AI Overviews?

Google has addressed llms.txt directly. Its guide to optimizing for generative AI features lists llms.txt among the things you can ignore for Google Search. You do not need new machine-readable files, AI text files, special markup or Markdown to appear in AI Overviews or AI Mode, because Google Search does not use them. Google adds that keeping such a file for other services is fine and will neither harm nor help your visibility in Search.

The clarification appears in Google's documentation changelog on June 15, 2026. The same guide treats AEO and GEO, the labels people use for optimizing for answer engines and generative engines, as ordinary SEO from Google's side. The foundations did not change: pages Google can crawl and index, helpful original content, and accurate business information.

Eligibility for AI Overviews is covered step by step in our guide to AI Overviews for church websites. If a vendor tells you an llms.txt file will lift your Google visibility, that claim contradicts Google's own documentation.

Should your church publish one anyway?

For most churches the honest answer is not yet, and not before the basics are right. The file costs little to write, but it is one more thing to keep accurate, and an outdated summary can do more harm than none. This table helps you decide.

Decide by your situation, not by the hype
SituationOur suggestionWhy
One site, one location, a Visit page that is currentOptionalThe Visit page already does the work for visitors and for Google. Fix anything stale first.
Several campuses or many language pagesWorth a short fileA short index of campus and language pages gives any tool a clear starting point.
Nobody owns the website week to weekSkip itWrong service times in a machine-readable summary spread quietly.
A hosted builder that restricts files at the site rootSkip itCheck your platform first. Google Search does not depend on the file.
Business Profile not yet claimed or verifiedDo that firstGoogle says Business Profiles can help your services be visible in AI responses and other results.

If you do publish, treat the file like a bulletin insert. Give it an owner, and review it whenever service times, staff or addresses change. A file nobody maintains is worse than no file.

What does a short llms.txt for a church look like?

Keep it brief. Name the church, say in a sentence or two who it serves and in which languages, then link to the pages that hold the facts. Do not copy service times into the file. Link to your Visit page so there is only one place to update. This sample uses a made-up church and domain.

# Example Community Church
> A neighborhood church in Springfield with Sunday services in English and Spanish. Visit details, languages and contact information are on the pages below.

## Plan a visit
- [Visit](https://www.example.org/visit): service times, address, parking and what to expect
- [Languages and translation](https://www.example.org/languages): how to follow the service in your language on your phone
- [Children's ministry](https://www.example.org/kids): ages, check-in and safety

## Teaching
- [Sermons](https://www.example.org/sermons): recent messages with video and notes

## Contact
- [Contact the church office](https://www.example.org/contact): phone, email and office hours
  • Save it as plain text at the site root, so www.example.org/llms.txt opens in a browser. If that address shows your home page or an error, the file is not working.
  • Link only to pages that exist, and open every link before publishing.
  • Leave out private pages and personal contact details for staff. Include nothing you would not print in the bulletin.
  • Test it like a stranger. The proposal suggests asking an AI assistant questions while giving it only the file as a starting point. If the answers are wrong, fix the pages behind the file.

If your church runs live translation, the Languages page deserves care. Say which languages are available and how guests join. With SermonLingo, guests scan a QR code or open a link in their phone's browser, with no app or account, so the page can be short. You can see the guest view yourself on the SermonLingo demo service before you write it.

What helps more than llms.txt?

  1. Put the basics in real text. Service times, address, languages and children's check-in belong in the body of a page, not only in a flyer image or PDF.
  2. Claim and verify your Business Profile, and keep it consistent with your website. Entity SEO for churches shows how to audit the details.
  3. Write something only your church can write. Google's generative AI guide asks for original, first-hand content over summaries of what is already online. How your food pantry runs on Tuesday nights is more useful than a list of verses about hope.
  4. Check that Google is allowed in. A robots.txt rule or noindex tag left over from a redesign can hide pages, and no llms.txt file can undo it.
  5. Do the plain accessibility work. Google's web.dev guide to agent-friendly websites recommends semantic HTML, real links and buttons, and labelled form fields. Screen reader users benefit from the same changes.
  6. Watch your results in Search Console, including its generative AI performance report once your site has enough impressions.

One distinction is worth keeping straight. llms.txt describes a site; it does not grant or block access. Crawling is controlled with robots.txt, and Google offers a separate Google-Extended token for limiting use of your content for Gemini training and grounding. Google says that token does not affect inclusion in Google Search. For the wider picture, see AI search optimization for ministries.

Questions

Is llms.txt a Google ranking factor?

No. Google's guide to generative AI features says Google Search does not use llms.txt, so the file neither helps nor harms your visibility or rankings in Search. You can still publish one for other tools, but it should never replace accurate, crawlable pages on your church website.

Will an llms.txt file make AI assistants recommend my church?

No one can promise that an llms.txt file will make an AI assistant recommend your church. Each assistant decides how it finds and uses sources, and vendors rarely publish the details. The dependable foundation is accurate public information: a clear Visit page, a verified Google Business Profile, and the same details everywhere your church is listed.

Where does the llms.txt file go, and what does it contain?

The llms.txt file goes at the root of your site, for example www.example.org/llms.txt, as plain Markdown text. It needs one heading with your church's name. Most files add a one-sentence summary and short lists of links to useful pages such as Visit, Languages, Sermons and Contact.

Can an llms.txt file hurt a church website?

Google says an llms.txt file will not harm a site's visibility in Search. The practical risk is stale information: if the file names a pastor who has left or a service time that changed, any tool reading it may repeat the mistake. Link to pages instead of copying facts, and review the file whenever those pages change.

All articles