Open Knowledge Format (OKF) v0.1 — draft
Your Knowledge Layer is now an OKF bundle.
Your Knowledge Layer is now an OKF bundle — conformant with Google’s Open Knowledge Format (v0.1 draft). OKF is a format, not a platform: typed Markdown documents your existing llms.txt already points at. It works alongside your schema.org JSON-LD and llms.txt — nothing is replaced.
For the OKF frontmatter contract, see the Knowledge Layer reference.
Straight answers first
What OKF is — and what it isn’t.
The Open Knowledge Format is a draft specification published by Google Cloud in June 2026: knowledge as a bundle of Markdown files whose YAML frontmatter carries a required type. Before we tell you why we adopted it, here is what it does — and does not — do.
What it is
- A draft open format — v0.1, published by Google Cloud — for representing knowledge as a bundle of typed Markdown documents.
- A format, not a platform: plain files with typed YAML frontmatter that any tool can parse. No SDK, no lock-in.
- Forward-compatible AI-readiness: your Knowledge Layer conforms today, so your site is ready if consumers arrive.
What it isn’t
- Not a Search signal. Google says OKF has no effect on Search ranking — full stop.
- Not consumed by any public crawler today. OKF was designed for enterprise knowledge; Seogence applies it early.
- Not a Google endorsement — of Seogence, or of llms.txt. llms.txt is a community convention, not a Google standard.
- Not finished: it is a v0.1 draft, and we say so everywhere we mention it.
We think the honest version sells itself: OKF costs you nothing, changes nothing that works today, and types your content for whatever reads it next.
Bundle anatomy
One index, typed pages, one organization node.
The entry point stays llms.txt — the same per-domain index the Knowledge Layer has always served, now ending with a ## Knowledge bundle (OKF) section that links the bundle’s organization node. (OKF makes an index.md optional; llms.txt is our single discovery entry point.)
# yoursite.com
> Machine-readable markdown index for yoursite.com, served by Seogence. Each link returns the page as clean markdown for AI agents.
## Pages
- [https://yoursite.com/](https://seogence.com/KnowledgeLayer/yoursite.com/by-url?u=https%3A%2F%2Fyoursite.com%2F)
- [https://yoursite.com/product](https://seogence.com/KnowledgeLayer/yoursite.com/by-url?u=https%3A%2F%2Fyoursite.com%2Fproduct)
## Knowledge bundle (OKF)
Every page above carries typed YAML frontmatter conforming to Google's Open Knowledge Format (v0.1 draft).
- [Organization](https://seogence.com/KnowledgeLayer/yoursite.com/organization.md)Every page document carries OKF frontmatter on top of its existing keys. The type is mapped from the page’s schema.org @type — article, product, faq, service, event, person, organization, recipe, guide, or the default webpage — while schema_type preserves the raw value, resource names the live page URL, timestamp records the capture time, and tags mirrors keywords. Documents stored before the upgrade are brought up to this shape at serve time.
---
title: "Luxury Decor Bowl"
url: "https://yoursite.com/product"
description: "Handmade in Sweden."
author: "Acme Living"
site: "yoursite.com"
image: "https://yoursite.com/bowl.jpg"
published: 2026-05-12
type: product
okf_version: "0.1"
resource: "https://yoursite.com/product"
timestamp: 2026-06-28T09:14:03.000Z
schema_type: "Product"
keywords:
- "handmade bowl"
- "luxury decor"
tags:
- "handmade bowl"
- "luxury decor"
---
# Luxury Decor Bowl
Handmade luxury-decor bowls, finished by hand. Food-safe, one of a kind.The organization node — new with the bundle — is a typed document describing who is behind the site, built from your domain’s organization profile (with a hostname-only fallback, so the bundle shape is always stable).
---
type: organization
title: "Acme Living AB"
resource: "https://yoursite.com/"
okf_version: "0.1"
---
# Acme Living AB
- Website: [yoursite.com](https://yoursite.com/)
- Email: hello@yoursite.com
- Phone: +46 8 123 456
- Address: Storgatan 1, Stockholm, 111 51, SE
- Logo: https://yoursite.com/logo.png
## Official profiles
- https://www.linkedin.com/company/acme-living
- https://www.instagram.com/acmeliving
---
*Part of this site's [Knowledge Layer](llms.txt) — structured content by [Seogence](https://seogence.com).*Fetch it
Three requests, whole bundle.
The bundle is plain HTTP — the same Knowledge Layer routes, gated by the same per-domain toggle. Start at llms.txt and follow the links.
# The discovery entry point — one index for the whole bundle
curl "https://seogence.com/KnowledgeLayer/yoursite.com/llms.txt"# The bundle's typed organization node
curl "https://seogence.com/KnowledgeLayer/yoursite.com/organization.md"# Any page as OKF-typed Markdown, resolved by its live URL
curl "https://seogence.com/KnowledgeLayer/yoursite.com/by-url?u=https://yoursite.com/product" \
-H "Accept: text/markdown"How Seogence layers it
One embed. Three layers. Nothing replaced.
Working today
schema.org JSON-LD
Generated and injected into your pages — the structured data search engines and AI answer engines can read today.
The agent convention
llms.txt + Markdown
Clean Markdown at direct URLs with one discovery index — the convention agent builders already use. A community convention, not a Google standard.
Forward-compatible
OKF typed frontmatter
The same documents, typed per Google’s Open Knowledge Format (v0.1 draft), plus an organization node — ready if consumers arrive.
Each layer is additive. Enabling the OKF bundle changes no existing key, no existing URL, and no existing behavior of your site.
Questions
Common questions.
Is OKF a ranking factor in Google Search?
No. Google says OKF has no effect on Search ranking, and no public crawler consumes OKF bundles today. OKF was designed for enterprise knowledge; Seogence applies it early so your Knowledge Layer is ready if consumers arrive.
Do I need to change my site?
No. The typed keys are added inside the Knowledge Layer Seogence already serves — new documents are generated with them, and stored documents are upgraded at serve time. Your pages, your schema.org JSON-LD, and your llms.txt keep working exactly as before. Nothing is replaced.
Will the draft spec change?
Probably — that is what draft means. Minor versions are additive by design, we track the spec, and every document pins the version it conforms to in okf_version. The OKF keys were added the same way: additive, with every existing frontmatter key unchanged.
Is this the same thing as llms.txt?
No. llms.txt is the index — the single discovery entry point listing every document. OKF types the documents themselves: each one carries a required type plus resource, timestamp, and tags in its frontmatter. And to be precise about provenance: OKF is a Google Cloud draft format; llms.txt is a community convention that Google has not endorsed. Seogence uses the first to point at the second.
Try it
See your page as typed Markdown.
Enter any live page. Seogence analyzes it and shows the clean Markdown copy — with the structured data it would add — so you can see exactly what a typed bundle document would contain.