Google has introduced Open Knowledge Format (OKF), a new open specification designed to standardize the way content is packaged and shared with AI agents. Google Cloud Tech’s X post describes it as a “vendor-neutral” standard, built to be readable by both humans and machines without requiring new tools or software to implement.
What is Open Knowledge Format?
OKF v0.1 uses a directory of markdown files with YAML frontmatter to establish standardized conventions, making content more compatible between producers and AI agents. According to Google, a bundle of OKF documents is:
- “Just markdown:” every file is plain markdown that opens in any editor, renders on GitHub, and can be indexed by standard search tools
- “Just files:” a bundle ships as a tarball, lives in any git repo, and mounts on any filesystem
- “Just YAML frontmatter:” a short list of queryable fields covers type, title, description, resource, tags, and timestamp
Google has emphasized the simplicity of the format. There is no compression scheme, new runtime, or required SDK involved.
For now, the reference implementations and tooling center on Google Cloud, but the spec itself is open and vendor-neutral, published on GitHub under the Apache 2.0 license. OKF v0.1 will evolve as producers and consumers learn what knowledge representations agents actually need.
Why this matters for marketers
It’s still early. OKF is an internal knowledge format for AI agents, not a search ranking or web-publishing signal, and it isn’t tied to Google Search, YouTube, Maps, or other consumer products.
Google’s argument is that OKF can pull answers from otherwise incompatible sources. Its own examples are internal and technical: table definitions, metrics, and runbooks. For marketing teams, the parallels are internal too, like brand knowledge bases, reporting, sales enablement, and training.
OKF isn’t the only standard pointed at AI agents, and the differences are easy to confuse. An XML sitemap lists the pages on your site. An llms.txt file points crawlers toward your most useful content. OKF goes a step further and hands over the knowledge itself, packaged as files an agent reads directly. The difference that matters is direction: llms.txt and sitemaps face outward, toward the crawlers visiting your site, while OKF faces inward, toward an organization’s own agents.
For most marketers, none of this calls for action today. A published OKF bundle won’t move your rankings this week or next. Ensure your content is clean and well-structured, watch how the standard develops, and confirm that AI crawlers can already reach the content you publish. If agent-facing standards catch on the way sitemaps and schema did, that foundational work pays off.
How to prepare with Semrush
Site Audit flags whether your site is blocking AI crawlers and surfaces technical issues that can keep your content out of AI-generated answers, including a missing llms.txt file. It runs on every Semrush plan, so it’s a low-lift place to start.
To see how that work translates into visibility, the AI Visibility Toolkit tracks how often your brand gets cited across ChatGPT, Perplexity, Google AI Mode, and Gemini.
For enterprise teams, Semrush Enterprise AIO goes deeper, with AI visibility tracking across more LLMs and Crawler Profiles that simulate how bots like ChatGPT and Googlebot access and interpret your site.
