Google's OKF Standard: The New AI Agent Protocol No One's Talking About

On June 12, Google committed a new open standard to GitHub, and the announcement was so quiet that the loudest coverage was a Reddit thread titled "Most people missed it." No keynote, no Search Central post, no press cycle. Yet a month later the repo holds 6,831 stars, a linter, a signing tool, a WordPress plugin, and a Claude Code skill, which is a strange amount of ecosystem for a spec almost nobody wrote about. It's called OKF, the Open Knowledge Format, and it's Google's answer to a question every SaaS team is about to face: when an AI agent shows up to learn what your product does, what exactly should it read?

What the OKF Standard Actually Is

The spec itself is almost aggressively boring, and that's deliberate. An OKF bundle is a directory of markdown files, one file per concept: a feature, an API endpoint, a metric, a runbook. Each file opens with YAML frontmatter, and exactly one field is required, type, which tells an agent what kind of thing it's reading. Five more are recommended: title, description, a canonical resource URI, tags, and an ISO timestamp. Two filenames are reserved, index.md for progressive disclosure and log.md for update history. Bundles ship as git repos or plain folders, the whole thing is Apache 2.0 on GitHub, and there's no SDK, no runtime, no registration. Search Engine Journal's coverage landed on the best one-line summary: it's an agreement on shape.

Google's own framing gives away the ambition:

In case you missed it: We recently introduced the Open Knowledge Format (OKF), an open specification that formalizes the LLM-wiki pattern into a portable, interoperable format. How OKF works → https://t.co/RIhyQkffH8 https://t.co/4gioLyki3S

Google Cloud Tech@GoogleCloudTechJul 10, 2026

That phrase, formalizing the "LLM-wiki pattern," is the tell. Google is standardizing something practitioners were already doing in private, and betting that a shared shape beats a thousand bespoke ones.

One correction before we go further, because most of the early takes get this wrong. OKF did not come from the Search team. The announcement went out on the Google Cloud blog on June 13, written by two BigQuery tech leads, and the sample bundles in the repo are things like GA4 and Stack Overflow datasets. This is a data-team spec for sharing curated knowledge with agents. Nothing in it mentions rankings, crawling, or citations. Keep that in mind when someone sells you an "OKF for SEO" package.

You're getting AI traffic. But are you capturing the leads?

RankControl tracks every visitor from ChatGPT, Perplexity, and Claude. Full source attribution, intent scoring, and A/B tested lead capture.

Talk to us→

Where OKF Fits: The Four-Protocol Map

The agent stack is settling into layers, and OKF slots into a gap the other standards left open:

The framing that stuck from early analysis: MCP is the socket, OKF is the content that flows through it. And llms.txt, which we tested across 12 sites for 90 days, is a pointer telling agents where to look; OKF is the thing they'd find when they get there. None of these compete. A SaaS product could plausibly ship all four, which is roughly what the agentic engine optimization conversation has been circling since agents became the web's majority traffic.

The Community Already Built This, Which Is the Point

Here's the thing about the developer reaction: almost nobody was surprised, and that turned out to be the most bullish signal in the whole story. The busiest thread came from Claude users who recognized the spec instantly as the CLAUDE.md and memory-folder pattern they'd been running for months:

The consensus there was, in the moderator bot's own words, a resounding "duh, but also, neat." Dozens of builders had independently converged on markdown plus frontmatter, mostly via Obsidian vaults, which proves the shape is right. What none of them had was interoperability: everyone's tags and links were bespoke, so no tool could walk anyone else's knowledge pile. A shared spec fixes exactly that, and fixing only that is why the spec can stay small.

The skeptics have receipts too, to be fair. The top reply on the original thread pointed at A2A, Google's agent-to-agent protocol that has yet to see wide use, and called OKF more spaghetti thrown at the wall. Personal-knowledge-management folks bristled at Google formalizing a community convention inside its own GitHub namespace, and Hacker News veterans compared it to the Semantic Web formats that resurface every decade. Fair warning though: that same skepticism greeted sitemaps and schema.org, and both became table stakes.

RANKCONTROL

We'll show you exactly where your brand stands in AI search.

No commitment. No credit card. See how ChatGPT, Perplexity, Claude, and Gemini talk about your brand today.

Get your free report→

The Honest AI Search Angle

So should a SaaS site publish one? The sober read from the technical SEO community is that OKF today sits exactly where llms.txt sits: a cheap markdown overlay with no demonstrated ranking impact, no lock-in, and a real chance of mattering if any AI engine that counts adopts it. Low cost, no downside, speculative upside. One practitioner in the original announcement thread reported already running it across multiple repos with measurable context-fidelity improvements for their own agents, which is the near-term value: your OWN agents and your customers' agents read you better, whatever the search engines do.

The unresolved problem, raised in nearly every thread, is documentation rot. A knowledge bundle that drifts out of date doesn't fail loudly; it quietly feeds agents stale facts about your pricing and features. The format was never the hard part. Maintenance is. That's worth remembering because it mirrors what we see in AI citation tracking constantly: the sites that lose visibility are rarely the ones that never optimized, they're the ones that optimized once and stopped checking.

Publishing an OKF Bundle This Week

The whole exercise takes an afternoon for a typical SaaS product:

1. Map your concepts. One markdown file each for features, API endpoints, pricing tiers, and integration guides.
2. Add frontmatter. At minimum type: Feature (or Endpoint, Metric, Playbook), plus title, description, the canonical URL as resource, and a timestamp.
3. Write an index.md at the bundle root listing every concept, with okf_version: "0.1" in its frontmatter.
4. Cross-link the files with relative markdown links so agents can walk the graph.
5. Host it as a public git repo or a static folder. The yoursite.com/okf/ path is a community convention worth following, but know it's convention, not spec.
6. Put a refresh date in your calendar. Stale bundles are worse than no bundles.

Total time: four to six hours for the first pass, then an hour a month to keep it honest. Or the content engine generates and maintains agent-legible pages on your domain as part of its normal publishing cycle, and our tracking flags when engines and agents stop reading them. Either way, the marginal cost of showing up early to a standard is low; being findable when agents come shopping is the entire game this spec is quietly preparing for.

RANKCONTROL

Know exactly what AI says about your competitors.

RankControl's Recon Agent monitors competitor citations across ChatGPT, Perplexity, Claude, and Gemini. See where they show up and you don't.

See how it works→

The last Google standard that arrived this quietly was schema.org's early markup, and the sites that adopted it before rich results existed spent years collecting the dividend. OKF might die like A2A or compound like schema. Six hours and a folder of markdown is a cheap ticket to find out.