Module new 6 min
Open Knowledge Format
Google Cloud's June 2026 spec: knowledge as a directory of cross-linked markdown files with YAML frontmatter, readable by any agent without scraping.
Why it mattersThe first agent-readable content spec backed by a major platform; it formalizes the "markdown for machines" pattern llms.txt only gestured at.
Definition & Foundation
New in June 2026: for agents, not (yet) search
The Open Knowledge Format (OKF) is Google Cloud's attempt to formalize what llms.txt only gestured at: knowledge as a directory of cross-linked markdown files, one concept per file, each with YAML frontmatter. A product, a policy, an API, a metric: each gets its own file, and files link to each other with ordinary markdown links, so an agent can assemble context by following them wiki-style, with zero custom tooling. Published as v0.1 in June 2026 under Apache-2.0, it carries one required frontmatter field (type), five recommended ones (title, description, resource, tags, timestamp), and two reserved filenames: index.md for a folder's contents and log.md for its change history.
The critical framing: OKF was built for the "context assembly problem" faced by coding, research, and enterprise agents, not as an AI-search retrieval signal. No answer engine treats OKF as a ranking or retrieval input today. So the honest GEO position mirrors llms.txt: adopt OKF if you have agents that read your content directly (internal tools, partner integrations, coding assistants consuming your docs), and treat any future search upside as a free option, which is why, like llms.txt, it earns no impact score yet.
The Spec, and How It Compares
What OKF declares, and where it sits next to llms.txt and schema
One concept per file
Each markdown file describes exactly one thing: a product, policy, API, or metric. This is the same "self-contained unit" instinct as passage optimization, applied to a whole knowledge base: an agent grabs the file it needs without parsing an entire site.
YAML frontmatter
One required field, type, plus five recommended ones (title, description, resource, tags, timestamp) and any producer keys you invent. Deliberately minimal, and forgiving by design: a conformant consumer must never reject a bundle over an unknown type, an unknown key, or a broken link. Low ceremony is the point; it is what lets a spec survive contact with real adoption.
Wiki-style cross-links
Files reference each other with plain markdown links, so an agent follows them to build context on demand: no bespoke API, no scraping. This is the actual innovation: it solves how an agent assembles what it needs, not how a search engine ranks you.
Reserved files
Two filenames are special. index.md lists what lives in a folder, so an agent reads the map before drilling into details (progressive disclosure); log.md records changes newest-first. Everything else is a concept. It is the "clean table of contents plus a changelog" instinct, written for a machine reader instead of a human one.
Loaded, not crawled
A bundle is not something an engine spiders. There is no official discovery mechanism: you tell a named agent where the directory is (a link from llms.txt, a /.well-known/okf pointer, or an agent config path). That single fact is why "publish it and wait for AI traffic" misreads the format entirely.
OKF vs llms.txt vs schema
Schema annotates facts inside your public HTML for search engines (proven, used today). llms.txt is an informal content map (unproven). OKF is a structured knowledge directory for agents (new, vendor-backed, agent-focused). They layer; they don't replace each other.
Myths vs Reality
Common misreadings, corrected
Putting It to Work
Adopt for agents you can name
OKF pays off when a real agent reads your content directly. The test before investing is simple: can you name the agent? If yes, publish a small, clean directory; if no, watch the standard mature. When you are ready to build one, our step-by-step walks the whole mechanism end to end: How to Create an OKF Bundle for AI Agents.
The agent-readable-knowledge playbook
Identify a concrete agent consumer
Do you have coding assistants reading your API docs, partner integrations pulling your specs, or internal agents querying your policies? A named consumer justifies OKF. "An AI search engine might use it someday" does not; that's the free option, not the reason.
Model your knowledge as one-concept files
Break the knowledge that agent needs into a directory of markdown files (one product, policy, API, or metric each) with the required type frontmatter and the reserved fields where they apply. Reuse your existing canonical facts and docs as the source.
Cross-link for context assembly
Connect related files with plain markdown links so an agent can traverse from a product to its pricing to its policies. The value is in the graph of links, not any single file; mirror the relationships your agent needs to answer real questions.
Keep it in the repo, versioned and fresh
Because OKF is just markdown files, it diffs cleanly in git and rides your normal review and deploy flow. Wire timestamps to real updates so agents can trust freshness, the same discipline as content freshness, applied to your knowledge directory.
Treat search upside as a free option
If an engine later adopts OKF as a retrieval signal, you're early, but don't budget for that. Invest to serve the agent you named today; log OKF in your standards-watch so you notice the day its status changes.
Works Together With
The nodes this one leans on
Tools for this from Technical GEO
- Screaming Frog freemium Desktop crawler: render checks, schema extraction and content audits at scale.
- Dark Visitors freemium Live registry of AI crawler user-agents plus robots.txt generation.
- Google Rich Results Test free Validates structured data exactly the way Google parses it.
- Bing Webmaster Tools free Index health for the Bing corpus that ChatGPT Search and Copilot retrieve from.
Go deeper from Technical GEO
Voices to follow
- Michael King · iPullRank The deepest technical explanations of how AI retrieval and ranking actually work.
- Crystal Carter · Wix Structured data and AI-search education with concrete implementation examples.
- Aleyda Solis · Orainti Practical frameworks, checklists and free learning roadmaps for search & AI search.
Canonical reads
Always current
These links resolve live: what you get is generated or filtered the moment you click.
Fresh from the field feed refreshed July 8, 2026
- Jul 7 SEO Study: 5 Lessons From Running AI Agents Across Every Search via @sejournal, @lorenbaker Search Engine Journal
- Jul 7 Google Search Console Adds Reports For Social Posts via @sejournal, @MattGSouthern Search Engine Journal
- Jul 7 Google Search Console gains reporting on social and video platforms Search Engine Land
- Jul 7 Google On Using Markdown For AI SEO via @sejournal, @martinibuster Search Engine Journal