Open Knowledge Format (OKF) vs llms.txt: Two Ways to Make Your Site Agent-Ready in 2026
Open Knowledge Format (OKF) vs llms.txt: Google's structured markdown-plus-YAML knowledge bundles versus the community llms.txt index for AI agents. Compare structure, maturity, setup, vendor independence, real-world crawler pickup and when each wins in 2026.
These are complementary layers, not rivals, and the honest 2026 answer is usually 'ship both.' Reach for llms.txt first if you run a public website: it is a single text file at your root, a non-engineer can publish it in minutes, it has 20+ months of community tooling behind it, and it is the established way to expose a curated index to agents. Reach for OKF when a flat index is not enough — when you are packaging curated internal or enterprise knowledge that agents must navigate by type and metadata before reading, when producers and consumers need to interoperate without translation, or when you want a portable bundle agents read as-is with no scraping and no API in between. The honesty caveat applies to both: neither is reliably fetched in the wild yet. Limy's analysis of 500M+ LLM bot events in May 2026 found the major crawlers overwhelmingly skip /llms.txt and read HTML directly, and OKF is only days old. So treat both as forward infrastructure bets, not traffic guarantees. The framing Context Studios uses with clients is a dual-format discoverability strategy: llms.txt as the public front door for any site, OKF for the deeper, typed knowledge bundles your agents will actually reason over — shipped now, so you are already there the day a major answer engine flips the switch.
Detailed Comparison
A side-by-side analysis of key factors to help you make the right choice.
| Factor | Open Knowledge Format (OKF)Recommended | Llms.Txt | Winner |
|---|---|---|---|
| Structure & metadata granularity | A whole directory of markdown files, each with typed YAML front matter (type, title, description, tags, links) — granular, machine-typed context | A single flat file: a curated list of links with one-line descriptions, with an optional llms-full.txt that embeds the content | |
| Adoption & maturity | Published by Google Cloud on 12 June 2026 — days old at launch, with tooling and conventions still settling | Live since September 2024 with 20+ months of community adoption, generators and real-world examples | |
| Setup friction | Author a directory of typed markdown files plus an index.md so agents see the bundle's structure first | A single text file at your domain root — a non-engineer can ship it in minutes with nothing to install | |
| Scope & depth | Built for curated knowledge bundles and enterprise agent context — a portable knowledge base, not just a pointer list | A site discovery surface — an index of your key pages, not a structured body of knowledge | |
| Vendor independence | A genuinely portable spec, but it originated from and is stewarded by Google Cloud (the open piece of its Knowledge Catalog launch) | A community proposal from Jeremy Howard at Answer.AI, with no single vendor steering the standard | |
| Agent navigability | Typed front matter and linked neighbours let an agent map a whole bundle before opening any single file — no scraping, no API | An agent gets a flat list of links, then still has to fetch and parse each target page to learn anything | |
| Real-world crawler pickup | Too new to measure — published in June 2026, with no field data on uptake yet | Empirically thin today: Limy's 500M+ bot-event study found GPTBot, ClaudeBot, PerplexityBot and others overwhelmingly skip it | |
| Human readability | Plain markdown in any editor, renderable on GitHub, indexable by any search tool — readable to people and machines alike | Plain markdown too — a short, human-readable index anyone can open and edit in seconds | |
| Total Score | 3/ 8 | 3/ 8 | 2 ties |
Key Statistics
Real data from verified industry sources to support your decision.
Google Cloud Blog
Limy
Limy
Suganthan Mohanadasan
Suganthan Mohanadasan
Fern
All statistics come from verified third-party sources. Source, year, and direct link are shown on each metric.
When to Choose Each Option
Clear guidance based on your specific situation and needs.
Choose Open Knowledge Format (OKF) when...
- You are packaging curated internal or enterprise knowledge for agents, not just indexing a public site
- You need typed, per-document metadata an agent can navigate before it reads anything
- You want a portable bundle agents consume as-is, with no scraping and no API in the way
- Producers and consumers across teams must interoperate on the same context without translation
Choose Llms.Txt when...
- You want a zero-friction, single-file surface live at your domain root today
- Your priority is public-website AI discoverability, not an internal knowledge base
- You want the established community standard with 20+ months of tooling and examples
- A non-engineer needs to ship it in minutes, with no structure to design and nothing to install
Our Recommendation
These are complementary layers, not rivals, and the honest 2026 answer is usually 'ship both.' Reach for llms.txt first if you run a public website: it is a single text file at your root, a non-engineer can publish it in minutes, it has 20+ months of community tooling behind it, and it is the established way to expose a curated index to agents. Reach for OKF when a flat index is not enough — when you are packaging curated internal or enterprise knowledge that agents must navigate by type and metadata before reading, when producers and consumers need to interoperate without translation, or when you want a portable bundle agents read as-is with no scraping and no API in between. The honesty caveat applies to both: neither is reliably fetched in the wild yet. Limy's analysis of 500M+ LLM bot events in May 2026 found the major crawlers overwhelmingly skip /llms.txt and read HTML directly, and OKF is only days old. So treat both as forward infrastructure bets, not traffic guarantees. The framing Context Studios uses with clients is a dual-format discoverability strategy: llms.txt as the public front door for any site, OKF for the deeper, typed knowledge bundles your agents will actually reason over — shipped now, so you are already there the day a major answer engine flips the switch.
Frequently Asked Questions
Common questions about this comparison answered.
Related Comparisons
Explore more comparisons to inform your decision.
Need help deciding?
Book a free 30-minute consultation and we'll help you determine the best approach for your specific project.