Maybe in some specific tools or future systems, but it is not a universal AI-discovery requirement. As of August 2026, Google explicitly says it does not use llms.txt for Search, and major AI platforms such as OpenAI document crawler access through robots.txt rather than requiring an llms.txt file.

That makes llms.txt worth understanding.

It does not make it a magic switch.

The web-development world occasionally discovers a new file and immediately treats it like a ranking factor.

llms.txt has received some of that treatment.

What is llms.txt?

llms.txt is an emerging convention intended to provide language models with a concise, machine-readable summary of useful content on a website.

The basic idea is sensible.

A site could provide a text or Markdown-style file that points an AI system toward:

important documentation;

key pages;

structured explanations;

other useful resources.

Conceptually, it is a way of saying:

If an AI system wants a clean map of this site's important information, start here.

That can be useful.

But "useful idea" and "documented ranking requirement" are very different things.

Google says it ignores llms.txt

Google's current official generative-AI Search guidance is unusually clear.

It says website owners do not need to create new machine-readable AI files, special AI text files or special markup to appear in Google Search, including AI Overviews and AI Mode.

Google specifically names llms.txt.

Its guidance says creating one will neither help nor hurt visibility or rankings in Google Search because Google Search ignores it.

That is about as direct as platform guidance gets.

So if somebody tells you:

You need llms.txt to rank in Google AI Overviews,

the current official Google documentation says otherwise.

OpenAI's current publisher guidance focuses on a different mechanism.

If you want content discoverable and citable in ChatGPT Search, OpenAI says to make sure OAI-SearchBot is not blocked.

That is a crawler-access issue.

OpenAI documents robots.txt controls for that crawler.

It does not currently tell ordinary publishers that llms.txt is required for ChatGPT Search discovery.

That distinction matters.

Follow documented platform behaviour before speculative optimisation tactics.

Could llms.txt still be useful?

Yes.

This is where I would avoid swinging too far in the other direction.

A convention can be useful before it becomes universal.

Some tools, agents, crawlers or developer workflows may choose to read an llms.txt file.

A well-maintained file may make a documentation-heavy site easier for certain systems to navigate.

There is nothing inherently wrong with creating one.

The question is priority.

Worth knowing

llms.txt is exactly the sort of emerging idea that can become an expensive distraction for a small business. If the site still has weak service pages, poor internal linking, crawl problems or generic content, I would fix those first. A speculative extra file should not outrank proven fundamentals.

Priority matters for a small business

Imagine a small business website has:

weak service pages;

no proper About page;

broken internal links;

no sitemap;

poor local information;

and an llms.txt file.

I would not consider the AI-visibility problem solved.

The business has optimised a speculative machine-readable file while neglecting the actual public source material.

That is backwards.

Fix the website first.

A bad llms.txt file can become another stale asset

Every additional machine-readable file creates maintenance.

If it lists old URLs, missing pages or outdated services, it becomes inaccurate.

If the site structure changes and nobody updates it, the file drifts away from reality.

That is not catastrophic.

It is simply another reason not to add it thoughtlessly.

If you create one, maintain it.

llms.txt is not a replacement for robots.txt

These files solve different problems.

robots.txt communicates crawler-access preferences to bots that respect it.

llms.txt is an emerging content-discovery convention.

Do not confuse:

may crawl

with:

here are the pages I think are useful.

The access decision remains fundamental.

I explain that properly in should I allow AI crawlers on my website?.

It is not a replacement for a sitemap either

An XML sitemap is an established discovery mechanism for search engines.

It lists canonical URLs you want crawlers to know about.

Again, different job.

A small-business website should not skip established search infrastructure because a newer AI-specific convention sounds more exciting.

What should Built by Gavin do?

I am open to llms.txt.

But I would treat it as an optional experimental layer.

The site should first have:

clean crawlability;

strong canonical pages;

useful Guides;

clear internal links;

XML sitemap;

appropriate crawler access;

good structured data;

strong business identity.

Once those are in place, adding a lightweight llms.txt is reasonable if we want to support systems that may use it.

That is a sensible experiment.

Not the foundation.

Gavin's take

I would not sell llms.txt as a premium AI-visibility product. If there is a sensible low-cost reason to test it, fine. But the client should understand that it is experimental and not confuse its presence with guaranteed discovery, indexing or citation.

Should you pay someone hundreds of euro to add it?

Not on the basis of the file alone.

Creating a basic llms.txt is not a large technical project.

If somebody is charging for a broader AI-discovery audit that includes crawler controls, content structure, source quality and monitoring, that may be legitimate work.

If the entire service is:

We create llms.txt and get you into AI,

I would want evidence.

How would I test whether it helps?

Treat it like an experiment.

Create it cleanly.

Track referral traffic.

Watch AI/search visibility where measurement is available.

Keep the file aligned with the actual site.

Then evaluate.

Do not claim success because the file exists.

The bottom line

llms.txt is an emerging convention.

It may become useful across more systems.

But as of August 2026:

Google says it ignores the file for Search;

OpenAI's documented ChatGPT Search guidance focuses on OAI-SearchBot access;

and no universal AI-discovery standard requires every small-business site to have one.

So I would not ignore it.

I also would not build an AI SEO strategy around it.

Want your site prepared for AI discovery without chasing every new file format?

See how I approach modern website foundations or tell me what you want the site to become known for.

The priority is still the quality and accessibility of the actual website.

---