Google Says You Don’t Need llms.txt. Should You Still Create One?

Google has been clear that it does not use llms.txt for Search or its AI features. That naturally raises a fair question: if the biggest player on the internet ignores the file, why bother?

It’s a good question, and the honest answer is: it depends on what you’re trying to do. llms.txt was never primarily about Google. Conflating “Google doesn’t use it” with “it’s useless” is a category error. Let’s untangle it.

Why “Google doesn’t use it” isn’t the whole story

Google’s statement tells you one specific thing: a /llms.txt file will not influence Google Search rankings or how Google’s AI surfaces your content. That’s true and worth internalizing — if you came for an SEO boost, this is not it. (We cover that fully in Is llms.txt a Google Ranking Factor?.)

But Google Search is not the only consumer of web content anymore. The file is read — or can be read — by:

LLMs that users paste context into directly
AI agents and assistants pointed at a specific domain
Internal retrieval-augmented-generation (RAG) pipelines built over your own docs
MCP servers and automation tools that prefer structured Markdown over scraped HTML
Developers and technical writers who just want a clean index of your site

Google opting out doesn’t change the value llms.txt offers those other consumers.

Who genuinely benefits

You should consider creating an llms.txt if any of these describe you:

You have documentation. A /llms.txt linking to your quickstart, concepts, and API reference is a fast, accurate map for anyone — human or machine — learning your product.
You ship an API or developer tool. Agents and developers can orient themselves far faster from a curated link list than from your marketing pages.
You run a SaaS or content-heavy site and want AI tools that do read the file to summarize you accurately rather than guessing from cluttered HTML.
You’re building agent or automation workflows that need a predictable, parseable description of a site.
You maintain an internal knowledge base and want a curated source of truth for your own RAG system.

In these cases the file pays for itself in comprehension quality, not rankings.

Who can comfortably skip it

Be equally honest about when it’s not worth it:

Small brochure or local-business sites whose only goal is Google rankings. Spend your time on conventional SEO and content instead.
Sites with almost no content to index. A llms.txt that points to three pages adds little.
Anyone hoping it will guarantee AI citations or traffic. It won’t, and chasing that will only frustrate you.

There’s no shame in deciding llms.txt isn’t for you. A clear “no” beats a half-maintained file.

A simple decision framework

Ask yourself three questions:

Do I have content worth explaining to a machine (docs, API, product, substantial guides)? If no, skip it.
Do I expect LLMs, agents, or internal tooling to consume my content — now or soon? If no, it’s low priority.
Can I keep it accurate as my site changes? If you can’t maintain it, a stale file is worse than none.

Two or more “yes” answers, and creating an llms.txt is a reasonable, low-cost move.

If you do create one, do it properly

The fastest way to undermine the file is to ship a malformed or stale one. A few principles:

Start with a single H1 title and a one-line summary blockquote.
Group links under clear H2 sections (Docs, API, Guides, etc.).
Give every link a short description.
Keep it concise; move long-form content into a companion llms-full.txt.
Validate before publishing. Paste the file or point us at your URL with the free llms.txt validator.

You don’t have to write it by hand — our generator can produce a clean draft from your site that you then review and trim.

The bottom line

“Google doesn’t use it” is true, but it answers a question most people aren’t really asking. The useful question is: do the tools and workflows I care about benefit from a clean, machine-readable map of my site? For docs, APIs, SaaS products, and agent workflows, the answer is often yes — and that’s reason enough, with no ranking claims required.

Decide deliberately. If the answer is yes, generate a draft and validate it before you ship.

Google Says You Don't Need llms.txt. Should You Still Create One?