For almost a year, LLMs.txt was sold to the SEO community as a simple, low-effort win for AI visibility — the AI-era equivalent of robots.txt. New data published this month suggests that story was mostly wishful thinking. And the most useful thing any SEO professional can do right now is look honestly at what changed.

I wrote a complete implementation guide for LLMs.txt covering exactly what it is, how it works, and how to deploy it — because at the time, the available evidence and Google's own framing suggested it was a meaningful piece of AEO and GEO strategy. New data from Ahrefs, combined with direct statements from Google's John Mueller, tells a more complicated story. This isn't a case of the tactic being a scam. It's a case of the actual adoption and impact being far smaller than the hype suggested — and that distinction matters enormously for how you should be spending your time.

This guide walks through exactly what the new data shows, what Google has said on the record, where LLMs.txt still has genuine value, and — most importantly — what you should actually be prioritising instead if AI search visibility is your goal.


The Headline Number

97%
of published LLMs.txt files received zero requests in May 2026 — no bots, no humans, nothing at all
Ahrefs · 137,000 domains analysed · Published June 15, 2026

Ahrefs analysed server logs and live traffic across 137,000 domains in its Web Analytics dataset. They checked each domain for a valid LLMs.txt file returning a clean HTTP 200 response, then examined every request made to that file path across the entire population — classified by user agent, channel, and bot type. To rule out false positives, they confirmed each file was genuine Markdown content rather than a soft 404 page.

28%
of the 137,000 domains studied actually publish an LLMs.txt file
1,100
domains out of ~38,000 valid files received any traffic at all
96%
of the requests that did happen came from bots — not human visitors
1%
of total requests came from AI retrieval bots tied to ChatGPT and Perplexity

Who Is Actually Requesting These Files? The Real Breakdown

This is the part of the data that surprised me most. Of the small sliver of LLMs.txt files that did receive requests, the traffic composition wasn't dominated by AI retrieval bots at all. Here's the actual breakdown of who is requesting these files:

Who Requests LLMs.txt Files — Traffic Source Breakdown
SEO Audit Tools
21.7%
Named AI Tools (GPTBot etc.)
19.5%
Other / Unidentified Bots
14.9%
General Web Crawlers
13.1%
Tech Profiling Tools
11.6%
AI Agents & Infrastructure
10.5%
Human Visitors (SEOs checking)
~4%

The single most telling finding in the entire study: Ahrefs analysed every request to LLMs.txt paths that returned a 404 — meaning the file didn't exist — and found that zero of those probing requests came from AI bots. The people checking for missing LLMs.txt files were humans, typing the URL directly into a browser, almost certainly SEOs auditing competitor sites. This kills the core assumption that drove most LLMs.txt adoption: that AI systems are actively hunting for this file, and a site without one is missing a knock at the door. They simply aren't checking.

What Google Has Actually Said — In Its Own Words

The data alone would be significant. What makes this a genuine reversal is that Google's own statements over the past month line up with it almost exactly. In late May 2026, Google published a new guide on optimising for generative AI features, with a section literally titled "mythbusting" that states plainly: machine-readable files like LLMs.txt aren't needed to appear in generative AI search.

Then, when SEO journalist Lily Ray pressed Google's John Mueller directly on the apparent contradiction with Chrome's Lighthouse tool (which does check for LLMs.txt), Mueller gave the clearest statement yet on the record:

John Mueller — Google Senior Search Analyst, on the Search Off the Record podcast
"It's basically you're telling these systems, like, I have the best website ever." Mueller explained LLMs.txt files cannot be used by large language model systems to differentiate which website to surface — calling it a "temporary crutch, perhaps to save some tokens" for AI coding tools parsing developer documentation, not something most non-developer sites need to worry about.

Mueller had made a similar point earlier this year in a Reddit post, comparing LLMs.txt to the old meta keywords tag — a once-popular but ultimately ignored signal. His direct quote from that post: "AFAIK none of the AI services have said they're using LLMs.TXT (and you can tell when you look at your server logs that they don't even check for it)." The new Ahrefs data is essentially the large-scale empirical confirmation of exactly what Mueller had already been saying anecdotally.

The Confusing Part — Google Sent Mixed Signals Within Days

Here's where it gets genuinely strange, and worth understanding if you've felt confused by conflicting advice. In the same short window, Google's Chrome team shipped an LLMs.txt check inside Lighthouse's experimental "Agentic Browsing" audits — with documentation explaining that without the file, AI agents may spend more time crawling a site to understand its structure.

Google's Two Conflicting Signals — Within 2 Weeks
Mid-May 2026
Chrome Lighthouse Adds LLMs.txt Check
Chrome's experimental Agentic Browsing audits begin checking for an LLMs.txt file, with documentation suggesting its absence may slow down AI agents trying to understand a site's structure.
Late May 2026
Google's Official AI Guide Says It's Not Needed
Google's new guidance on optimising for generative AI features states directly, in a section titled "mythbusting," that machine-readable files like LLMs.txt are not required to appear in generative AI search results.
Early June 2026
Mueller Clarifies the Contradiction
When pressed publicly, Mueller resolves the apparent contradiction: LLMs.txt is "not done for search." Its narrow, legitimate use case is helping an AI agent navigate or complete a task once it's already on a site — not influencing whether that site gets recommended in the first place.
June 15, 2026
Ahrefs Publishes the Hard Data
The 137,000-domain study confirms empirically what Mueller had been saying: real-world AI retrieval traffic to LLMs.txt files is negligible, and AI bots don't proactively look for missing ones.

Once you understand Mueller's distinction, the contradiction dissolves. LLMs.txt isn't being framed as an SEO discovery tool — Google never claimed it determines whether your site gets recommended. Its legitimate use case is narrower and more technical: helping an agent that has already landed on your site navigate it more efficiently, similar to how a sitemap helps a crawler navigate once it's already there, rather than helping it get discovered in the first place.

My Honest Take — Akif Qureshi

"I implemented LLMs.txt for several clients this year based on the genuine belief, supported by the available evidence at the time, that it was a meaningful piece of AI visibility infrastructure. The Ahrefs data and Mueller's statements don't make that decision wrong in hindsight — they make it clear the impact ceiling was always lower than the hype suggested. The lesson I'm taking from this isn't 'never trust new SEO tactics.' It's 'separate the technically interesting from the practically impactful, and keep checking your own server logs rather than relying on industry consensus alone.'"

So Is LLMs.txt Worthless? Not Quite — Here's the Honest Verdict

Still Worth Doing (Low Effort, Low Risk)
  • Keep an existing LLMs.txt file — it causes no harm and costs nothing to maintain
  • If you already have structured product or developer documentation, compiling one is trivial
  • May help AI coding agents navigate developer docs more efficiently once on your site
  • Website builders like Wix, Framer, and Lovable are starting to auto-generate them — frictionless if your platform supports it
  • Adoption may grow as a CMS default, similar to sitemaps, even without proven ranking impact today
Stop Doing This
  • Treating LLMs.txt as a primary AI visibility strategy
  • Telling clients it will increase AI Overview or ChatGPT citation frequency
  • Spending significant budget or time crafting an elaborate LLMs.txt over fixing actual content gaps
  • Auto-generating LLMs.txt content via CMS plugins without reviewing it — see the security risk below
  • Assuming a competitor's strong AI visibility is connected to their LLMs.txt file
A Security Risk Worth Knowing About

Ahrefs flagged something genuinely important buried in the data: a crawler was found studying LLMs.txt files specifically as a potential prompt injection risk. Because AI agents are trained to trust ingested content, a compromised or maliciously edited LLMs.txt file could become an attack vector. If you publish one, treat it like code — version control it, restrict editing access, set alerts for unauthorised changes, keep content to plain factual links and descriptions (nothing instruction-shaped), and review anything a CMS plugin auto-generates on your behalf before it goes live.

What to Prioritise Instead — Where AI Visibility Actually Comes From

If LLMs.txt isn't the lever the industry hoped it would be, the obvious next question is: what is? Based on the same body of evidence — Google's own guidance, Mueller's statements, and corroborating research from Ahrefs and SE Ranking — here's where the actual leverage sits:

Lever Why It Actually Moves AI Visibility
Standard Search Eligibility Google's own guidance: good AI search visibility still depends on strong fundamentals — indexable pages, useful content, and eligibility for normal Search snippets
Strong EEAT Signals Verifiable authorship, real credentials, and editorial trust signals directly feed how AI systems evaluate source quality before citing
Schema Markup (Article, FAQPage, Person) Confirmed structured data that helps both traditional ranking systems and AI extraction — unlike LLMs.txt, this has measurable, documented impact
Third-Party Authority & Citations Being referenced and linked to by other authoritative sources strengthens the entity signals AI systems use to evaluate trustworthiness
Clear, Specific Content AI systems extract and cite specific, well-structured, fact-dense content far more readily than vague or generic copy — content quality remains the dominant signal
Direct Bot Analytics Monitoring Tracking which AI bots actually visit your site gives real data instead of hoping a text file makes a difference — far more actionable than LLMs.txt alone

The Bigger Pattern Worth Recognising

This isn't the first time the SEO industry has collectively over-indexed on a new technical tactic before the evidence caught up. Ahrefs' own framing of this is worth repeating: people latch onto ideas that feel like control over AI visibility, because right now, the actual tools to measure and influence that visibility are still immature. A simple text file you can publish yourself feels actionable in a way that "produce more original, expert-authored content" doesn't — even when the latter is what the evidence actually supports.

I'd add one more pattern from my own five years in this industry: every emerging technical standard goes through the same lifecycle. Early enthusiasm outpaces adoption. Adoption outpaces measurable impact. Eventually, hard data arrives and recalibrates expectations to reality. LLMs.txt is squarely in that recalibration phase right now. That doesn't make it dead — Mueller himself left room for it to mature as agent workflows develop further. It does mean the conversation needs to shift from "must-have AI SEO tactic" to "low-cost hygiene item with unproven upside."

Your Action Plan — What to Actually Do This Week

1

Check Your Own Server Logs Before Making Any Decision

Don't rely on industry-wide averages alone. If you use Ahrefs, filter Bot Analytics by Page URL containing "llms.txt" to see exactly which bots, if any, are requesting your file. A 97% chance of zero readership is the base rate — your site may differ, and you should know your own number.

2

Keep Existing Files, Stop Treating Them as a Growth Lever

If you already have an LLMs.txt published, leave it in place — there's no evidence it causes harm. Simply stop allocating significant time or client budget to elaborately maintaining or expanding it as if it were a primary AI visibility strategy.

3

Redirect That Effort to Schema Markup and EEAT

The time previously spent crafting LLMs.txt content is better spent strengthening Article, Person, and FAQPage schema, building out genuine author credentials, and producing original content with specific, citable detail — all of which have a documented connection to AI citation behaviour.

4

Secure Any File You Do Maintain

Treat LLMs.txt as a controlled asset rather than a marketing afterthought. Version control it, limit edit access, keep content factual and link only to pages you control, and manually review anything a CMS or plugin generates automatically before publishing.

5

Re-Brief Any Clients You've Advised on LLMs.txt

If you've recommended LLMs.txt to clients as a meaningful AI visibility tactic, this is worth a short, honest update. Clients respect proactive correction far more than silence — and it's a natural opening to redirect their budget toward the higher-impact work outlined above.


Frequently Asked Questions

Does this mean LLMs.txt is a scam or worthless?
No — and the data and Google's own statements are careful not to claim that. LLMs.txt is not worthless; it's also not the AI visibility shortcut a lot of SEO and AEO discussion made it sound like throughout 2025 and early 2026. It remains a legitimate, low-risk technical asset with a narrow, confirmed use case for AI coding agents navigating developer documentation. The correction here is about expected impact and priority, not about the file being fraudulent or harmful.
Should I remove my existing LLMs.txt file?
There's no evidence suggesting you should remove it. Google has not indicated any penalty or downside to having one. The recommendation is to leave existing files in place, treat them as low-priority hygiene rather than active strategy, and apply the security precautions outlined above rather than removing them entirely.
Could LLMs.txt become more important in the future?
It's possible. Mueller's framing left room for this — he didn't dismiss the format outright, just clarified its current narrow use case. As AI agent workflows mature and agents increasingly perform multi-step tasks across websites rather than simple retrieval, the navigational use case Mueller described could grow in relevance. The Ahrefs researchers note that within a year, having an LLMs.txt may become as much a CMS default as having a sitemap, even if direct ranking impact remains limited. Worth monitoring, not worth over-investing in today.
Why did SE Ranking's earlier research also find no connection between LLMs.txt and AI citations?
SE Ranking's analysis of 300,000 domains, published earlier this year, found no measurable connection between having an LLMs.txt file and AI citation frequency. The new Ahrefs data adds the missing explanation for that earlier finding: AI retrieval bots simply aren't requesting these files at meaningful volume in the first place, which is consistent with why no citation correlation was ever found. The two studies corroborate each other from different angles — one measuring outcomes, the other measuring the underlying bot behaviour.

The Bottom Line

The Ahrefs data, combined with Google's own statements, gives the SEO industry something it rarely gets: a clear, evidence-based correction to a tactic that outran its actual impact. LLMs.txt is not a scam and not worth removing if you already have one — but it is not the AI visibility shortcut it was sold as, and 97% zero-request rate makes that conclusion hard to argue with. The real work for AI search visibility in 2026 remains exactly what it's always been: strong fundamentals, genuine expertise, structured data that's actually been proven to matter, and content built for citation rather than for checking a box. Keep your LLMs.txt if you have one. Just stop expecting it to do the heavy lifting.

Akif Qureshi
Akif Qureshi
Senior SEO Specialist & Marketing Analyst | Content Strategist
5+ yrs experience Google Certified 6 guides

Driven by advanced SEO expertise, deep marketing analytics, high-impact content strategy

With 5+ years of hands-on experience, I specialize in holistic search strategies that don’t just rank—they drive real, measurable business growth. I’ve worked across industries including healthcare, hospitality, legal, e-commerce, and professional services, helping brands dominate their target markets. My approach bridges the gap between raw data and creative execution. Every strategy I build is rooted in rigorous market analysis, structured SEO frameworks, and tailored content ecosystems—no templates, no shortcuts. Whether you’re a single-location brand or scaling across multiple cities, I create data-driven marketing systems designed to compound results and grow with you.

No sponsored content No affiliate links Reader supported

Ready to build your local SEO strategy?

Copy the prompt above, fill in your five details, and paste it into your AI assistant. Share this guide with anyone running a local business who needs more leads.