geo

llms.txt Won't Get You Cited by AI. Here's What Actually Will.

llms.txt won't get you cited: 515M+ bot events show AI crawlers ignore it. Six tactics with real evidence instead.

AD

Alex Dabson

Founder, DabaRank

7 min read

We keep getting the same question from clients: "should we add an llms.txt file?" The honest answer, as of July 2026, is that it almost certainly won't move your AI citation numbers — and we'd rather tell you that up front than let you spend a sprint on it.

TL;DR

llms.txt is a proposed markdown file listing a site's key pages for AI systems to read. An analysis of over 515 million bot events found AI crawlers essentially never request it, and no major AI provider — OpenAI, Google, or Anthropic — has committed to using it for ranking or citation decisions. It has a narrow, legitimate use for coding-agent documentation navigation, but it is not a GEO strategy.

What llms.txt actually is

llms.txt is a proposed convention — modeled loosely on robots.txt — where a site publishes a plain markdown file at /llms.txt listing its most important pages, with short descriptions, intended to give AI systems a curated map of the site. It sounded plausible for an obvious reason: robots.txt genuinely shapes what crawlers do, so a similarly simple text file promising to shape what language models do felt like a natural next step. Several CMS plugins and "GEO checklists" latched onto it fast, and it became one of the most-recommended "quick wins" in early GEO content.

Why the evidence says it doesn't work

The core question — do AI crawlers actually read it — has a documented answer, and it's no. An analysis of more than 515 million bot events found that AI crawlers essentially never request the llms.txt file at all (AEOEngine). That's not "rarely used as a ranking signal" — that's "the file is not being fetched in the first place" at meaningful scale.

That data point lines up with statements from the platforms themselves. No major AI provider — not OpenAI, not Google, not Anthropic — has publicly committed to reading or using llms.txt for ranking or citation decisions. Google's Gary Illyes has explicitly said Google will not use it (Wix AI Search Lab). When the crawler behavior data and the platform statements point the same direction, that's about as clear a "this doesn't work" signal as you get in an industry this new.

The one place llms.txt genuinely helps

It answers a real, narrower question well: how does a coding agent navigate my documentation? Companies like Stripe, Vercel, and Anthropic publish llms.txt files specifically to give coding assistants and developer tools a fast, structured index into API docs — a context where the "reader" is a specific class of agent operating inside a development environment, not a general-purpose consumer chatbot deciding what to cite in an answer. If you run a developer-facing product with extensive docs, an llms.txt file is a low-cost, legitimate addition for that use case. Just don't expect it to influence whether ChatGPT recommends your brand to a consumer comparing options.

What actually moves AI citations

Here's what has evidence behind it, in priority order.

1. Statistics, citations, and quotations in your content

Content is more likely to get cited by generative engines when it includes concrete statistics, cites its own sources, and includes quotations. A large-scale study from Princeton and collaborators, analyzing roughly 10,000 queries (the "GEO" paper presented at KDD), found that adding statistics increased citation visibility by 40%, citing sources increased it by another 40%, and including quotations added 28% — with combined techniques driving overall gains of 30–41% (Search Engine Land).

+40%

citation visibility from adding statistics to content

Source: Princeton/KDD GEO study

This is the single highest-leverage, best-evidenced tactic in GEO right now, and it's also the cheapest to execute: rewrite your existing content to include real numbers, name your sources, and quote credible voices instead of making unsupported claims.

2. Third-party presence, not just owning your own narrative

Your own website is not where most AI citations come from. Roughly 91% of AI citations pull from third-party sources rather than brand-owned domains, and about one in three citations comes from comparative listicle-style content ("best X for Y") rather than a single authoritative page (Growth Unhinged; Onely). That means getting covered in third-party comparisons, review roundups, and industry listicles matters more for GEO than polishing your own site copy — a genuine reversal from classic SEO's emphasis on owned-domain authority.

3. Presence on Wikipedia and Reddit specifically

Not all third-party presence is equal — two platforms dominate disproportionately. Wikipedia (13.2%) and Reddit (12%) together account for more than a quarter of US ChatGPT citations, and Reddit alone accounts for roughly 24% of Perplexity citations (5W Research via PR Newswire). Yet only about 11% of domains get cited by both ChatGPT and Perplexity (Profound) — meaning a presence strategy has to be platform-aware, not one-size-fits-all. Practically: a maintained, neutral-toned Wikipedia presence and genuine, non-astroturfed engagement in relevant Reddit communities are disproportionately valuable compared to almost any other third-party channel.

4. Freshness

Generative engines skew toward recently updated information more heavily than classic organic search does. ChatGPT-cited URLs are, on average, about 393 days newer than the URLs Google ranks organically for the same queries (Ahrefs). Practically, that means a content refresh cadence — updating publish dates, statistics, and examples on a real schedule, not just cosmetically — is a GEO lever in its own right, separate from writing new content.

5. Bing indexation and not blocking AI crawlers

ChatGPT's search functionality is built on Bing's index, which makes Bing indexation a prerequisite for ChatGPT search citations, not an optional extra (Ahrefs). Pair that with a basic technical check most sites still get wrong: confirm your robots.txt isn't blocking GPTBot, OAI-SearchBot, or PerplexityBot. It's a five-minute audit that can silently zero out your citation eligibility if it's wrong.

6. Structuring for extraction, even in unstructured answers

Even though generative answers are synthesized rather than extracted verbatim, models still favor content that's cleanly organized into direct, self-contained answers to specific questions — the same "answer-first" structure that wins featured snippets in AEO. It's not the dominant lever the way statistics and third-party presence are, but it compounds with them.

Why the myth persisted anyway

It's worth naming why llms.txt spread as fast as it did, because the same pattern will repeat with the next proposed "quick fix." robots.txt is a real, working precedent — it genuinely controls crawler behavior, and it's simple enough to explain in one sentence, which makes it an easy thing for a blog post or a plugin to promise as a GEO shortcut. The appeal of llms.txt was never really about evidence; it was about the shape of the idea. "One small file solves a hard, expensive problem" is an appealing pitch in any category, and GEO — being new, poorly measured, and full of anxious marketers — was fertile ground for it.

The honest version of GEO in July 2026 doesn't have a single-file shortcut. It looks more like ongoing content and reputation work: publishing content with real statistics and sources, earning mentions in third-party comparisons, maintaining a presence on the platforms models actually cite from, keeping content fresh, and clearing basic technical blockers. None of that fits on a one-page checklist you set once and forget — which is exactly why it's less viral than "just add this file," and exactly why it's the version that's actually backed by data.

Priority checklist

| Tactic | Evidence strength | Effort | |---|---|---| | Add statistics, citations, quotations to content | Strong (Princeton/KDD study, +30-41%) | Low | | Build third-party / listicle presence | Strong (91% of citations are third-party) | Medium | | Wikipedia + Reddit presence | Strong (>25% of US ChatGPT citations) | Medium-High | | Refresh content on a real cadence | Strong (393-day freshness gap) | Low-Medium | | Confirm Bing indexation + unblock AI crawlers | Strong (prerequisite for ChatGPT search) | Low (one-time audit) | | Answer-first content structure | Moderate (compounds with AEO) | Low | | Publish llms.txt | Weak (near-zero crawler usage; no provider commitment) | Low, but low payoff |

llms.txt isn't harmful to add if you're a dev-tools company serving coding agents — just don't mistake it for a GEO strategy. The tactics above are the ones we've built DabaRank's tracking around, because they're the ones with actual evidence behind them, not just plausible-sounding theory. See exactly which of these levers is moving your citations across every major AI platform we track — DabaRank starts at $99/mo with a 14-day free trial.

AD

Written by

Alex Dabson

Founder, DabaRank

Alex has spent his career across marketing agencies, local-services businesses, and multi-location, multi-brand companies, with a background building SaaS products — the exact teams now working to measure AI visibility across many brands at once. He founded DabaRank to track how brands rank and get cited across ChatGPT, Claude, Gemini, Perplexity, and other AI platforms.