For Google you don't need an llms.txt, or any special structured data: Google Search does not use such files, and an llms.txt neither helps nor harms your visibility [1]. None of ChatGPT, Claude or Perplexity officially confirms that they read the llms.txt of other sites. Structured data remains useful, but as hygiene, not as a lever.
The question often comes up after a LinkedIn post or a new button in an SEO plugin. If you hire an SEO agency, you can expect an honest answer, with sources.
What Google, the AI labs and the inventor say
| Who | What they say about llms.txt | When |
|---|---|---|
| Google Search | No new machine-readable files, AI text files or Markdown needed; Google does not use them, not even for AI Overviews or AI Mode [1], [2] | Guide from May 2026, llms.txt note of 15 June 2026 [3] |
| John Mueller, Google | As far as he knew, no AI service said it used llms.txt; he compared it to the keywords meta tag [4] | April 2025 |
| Chrome (Lighthouse) | An "emerging convention"; the audit only fails on a server error, and without a file it does not apply [5] | May 2026 |
| OpenAI, Anthropic, Perplexity | Document their crawlers and robots.txt [6], [7], [8], but nowhere say they use the llms.txt of other sites | Consulted September 2026 |
| Jeremy Howard, the inventor | Mainly used for software documentation, where coding agents follow it [9], [10] | August 2026 |
The AI labs do publish an llms.txt themselves, for their developer documentation [9], [8]. That is not the same as saying their search functions use the one on your site. And the Chrome audit says nothing about search visibility: it belongs to the Lighthouse category "agentic browsing", which Chrome itself calls experimental [11].
Ahrefs looked at how it works in practice: 28% of the domains in its data published an llms.txt, and 97% of those received not a single request for it in May 2026 [12]. Ahrefs also found no major provider that had formally adopted it [12]. So articles claiming that GPTBot or ClaudeBot "regularly read" your llms.txt are not backed by the makers.
What llms.txt is
On 3 September 2024, Jeremy Howard proposed giving websites a Markdown file /llms.txt, with a short summary of the site and links to the pages a language model should read [9]. The file has an H1 with the name (the only required part), a blockquote with a summary and sections with lists of links; a model may skip a section called "Optional" [9]. Version 2 from August 2026 adds, among other things, links in HTML or in an HTTP header to the Markdown version of a page [10].
This is what a small file looks like, for a made-up company:
# Schrijnwerkerij Peeters
> Schrijnwerkerij Peeters installs wooden windows and doors in the Leuven region,
> for homeowners and contractors.
## Services
- [Wooden windows](https://www.example.be/windows/): wood types, prices per m², installation
- [Front doors](https://www.example.be/doors/): models, insulation values, lead time
## Optional
- [Projects](https://www.example.be/projects/)
When llms.txt does make sense
- Software documentation. If you have an API or a software package, an llms.txt and Markdown versions of your pages make things easier for coding assistants. That is also the use the inventor sees [9].
- Large sites with a lot of deep content, where a summary quickly takes an agent to the right page.
- An SME site of twenty pages: low priority. If you have it generated automatically, as Yoast does for free in WordPress [13], it costs little. An outdated file with dead links helps nobody.
Google says so literally: you can ignore tactics such as cutting your content into "chunks" or creating unnecessary AI text files [1].
Structured data: hygiene, not a lever
Structured data tells Google in a fixed format what a page is about; Google recommends JSON-LD [14]. It is not required for Google's AI features, and there is no special markup for AI [1]. Correct markup doesn't guarantee a rich result either [15].
Structured data does make you eligible for rich results [1], and it makes basic facts about your business unambiguous: name, legal name, address, VAT number and profiles elsewhere [16]. Google calls the VAT number an important trust signal, because users can look it up in a public register [16]. The condition: your markup faithfully reflects what is visible on the page [15].
FAQ schema no longer works. From August 2023 Google only showed FAQ rich results for authoritative government and health sites [17], and since 7 May 2026 it no longer shows them at all [3]. That markup does no harm, but it has no visible effect [17]. An FAQ in plain text is still useful, for visitors and for AI answers.
Which structured data an SME needs
| Type | What for | Priority |
|---|---|---|
Organization or LocalBusiness | Name, legal name, address, phone, VAT number, logo, profiles (sameAs) | High, on your homepage or contact page |
BreadcrumbList | Where a page sits in your site | Medium |
Article | Blog posts and knowledge pages, with author and date | Medium, if you publish |
Product | Products with price and availability | High for web shops |
FAQPage | Frequently asked questions | Low: no rich result in Google any more |
An Organization block for our made-up company, with a fictitious VAT number:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Schrijnwerkerij Peeters",
"legalName": "Schrijnwerkerij Peeters bv",
"url": "https://www.example.be/",
"vatID": "BE0000000000",
"address": {
"@type": "PostalAddress",
"streetAddress": "Voorbeeldstraat 1",
"postalCode": "3000",
"addressLocality": "Leuven",
"addressCountry": "BE"
},
"sameAs": ["https://www.linkedin.com/company/example"]
}
</script>
If you work locally, with a shop or workshop, LocalBusiness is the better type, together with a well-completed Business Profile. Benjamin explains how that fits together in local SEO.
You can also add it via Google Tag Manager, because Google reads JSON-LD that is added to the page with JavaScript [18]. But then the risk grows that your markup diverges from the page [18], so preferably put it directly in the HTML. Cédric explains how GTM works in Google Tag Manager explained.
Test your markup with Google's Rich Results Test and the Schema Markup Validator from schema.org.
What achieves more than either
- Allow the right crawlers, such as OAI-SearchBot and PerplexityBot, including in your firewall or CDN.
- Text in the HTML: prices, services and contact details as plain text.
- One question per page, with the answer at the top and figures with a source.
- Mentions elsewhere, in places where your customers read.
The step-by-step plan is in how to get found in ChatGPT. How AI search engines then choose between candidates is covered in how ChatGPT, Gemini and Perplexity choose their sources.
Want to know whether your site has the basics in order, from structured data to your visibility in ChatGPT, Gemini, Perplexity and Google AI Overviews? The free scan looks at it, and you get the findings and a conversation.
Frequently asked questions
What is llms.txt?
A proposal by Jeremy Howard from September 2024: a Markdown file at /llms.txt that gives language models a short summary of a site and links to its most important pages. Version 2 appeared in August 2026. It is a proposal, not a standard.
Does Google use llms.txt?
No. Google writes that Google Search does not use machine-readable files, AI text files or Markdown, not even for its AI features, and that an llms.txt neither helps nor harms your visibility or rankings.
Do ChatGPT, Claude and Perplexity read my llms.txt?
There is no official confirmation of that. OpenAI, Anthropic and Perplexity document their crawlers and robots.txt, and publish an llms.txt for their own documentation, but nowhere say that their search functions use the llms.txt of other sites.
Do I need to add structured data for AI Overviews?
It is not required, and there is no special markup for AI. Structured data remains useful for rich results and to make basic facts about your business unambiguous, as long as it matches what is visible on the page.
Does FAQ schema still work for expandable questions in Google?
No. Since 7 May 2026 Google no longer shows FAQ rich results and has removed their documentation. FAQPage markup does no harm, but it no longer produces a visible result in Google Search.
Sources
- Optimizing your website for generative AI features on Google Search — Google Search Central, 10 Jul 2026, accessed 27 Sep 2026
- AI features and your website — Google Search Central, 10 Dec 2025, accessed 27 Sep 2026
- Latest Google Search documentation updates — Google Search Central, accessed 27 Sep 2026
- Google Says LLMs.Txt Comparable To Keywords Meta Tag — Search Engine Journal (Roger Montti), 17 Apr 2025, accessed 27 Sep 2026
- llms.txt (Lighthouse, agentic browsing audits) — Chrome for Developers, 5 May 2026, accessed 27 Sep 2026
- Overview of OpenAI Crawlers — OpenAI, accessed 27 Sep 2026
- Does Anthropic crawl data from the web, and how can site owners block the crawler? — Anthropic (Claude Help Center), 7 Apr 2026, accessed 27 Sep 2026
- Perplexity Crawlers — Perplexity, accessed 27 Sep 2026
- The /llms.txt file — llmstxt.org (Jeremy Howard), 10 Aug 2026, accessed 27 Sep 2026
- llms.txt: changes (v2, August 2026) — llmstxt.org, accessed 27 Sep 2026
- Agentic browsing audits: scoring — Chrome for Developers, 5 May 2026, accessed 27 Sep 2026
- What Is llms.txt, and Should You Care About It? — Ahrefs (Ryan Law), 15 Jun 2026, accessed 27 Sep 2026
- llms.txt in Yoast SEO — Yoast, accessed 27 Sep 2026
- Introduction to structured data markup in Google Search — Google Search Central, 10 Dec 2025, accessed 27 Sep 2026
- General structured data guidelines — Google Search Central, 10 Jul 2026, accessed 27 Sep 2026
- Organization structured data — Google Search Central, 8 Sep 2026, accessed 27 Sep 2026
- Changes to HowTo and FAQ rich results — Google Search Central Blog, 8 Aug 2023, accessed 27 Sep 2026
- Generate structured data with JavaScript — Google Search Central, 10 Dec 2025, accessed 27 Sep 2026