OKF export

Turn a saved crawl into a portable OKF knowledge pack for an agent or another tool. The export keeps its sources, generation details, validation profile and size limits explicit.

Install and run the export

Install the CLI once, then run seo start to connect your site and Google data. After setup you can run this export yourself or ask your agent to run it.

Runafter install

Install the SEO CLI globally.

npm i -g seo

Run setup after installation.

seo start

Build a limited site knowledge pack from a saved crawl.

seo okf export --project example

What the export contains

Export crawl evidence as a limited OKF v0.2 bundle with source details, generation metadata, and linked artifacts that an agent can inspect locally.

Best for: An agent needs a local, reviewable site map with source citations.
Needs: Saved or fresh crawl report
You get: Export crawl evidence as a limited OKF v0.2 bundle with source details, generation metadata, and linked artifacts that an agent can inspect locally.
Use next: Validate an OKF knowledge pack

Every report follows the same rules for missing data and outside estimates.See how report data works.

What you need before you run it

The report uses the information below. Optional sources are only used when you ask for them.

Saved or fresh crawl report

Provides page URLs, metadata, internal links, extracted concepts, and crawl caveats.

Concept and file limits

Bounds the manifest and optional inline Markdown files for the agent context available.

Use a different report for these jobs

These jobs need a different report or a manual review.

You need to check an edited or generated OKF file set for broken structure and references.

Run OKF validation on the exact Markdown files. Use the generic OKF profile for external bundles or the stricter SEO export profile for files built here.

OKF validator

You need to prove that every statement in the knowledge pack is current and correct.

No automated report can verify the truth of every extracted statement. Use this build to retain source-page references, then have a person compare important claims with the current live pages and the intended site meaning.

Needs more evidence

Use the export with an agent or in code

The command above is enough for most work. These options let an agent, script or application run the same export with explicit input and structured output.

Use the report catalog when an agent, script or CI job needs predictable JSON instead of the normal terminal output. Check the current input first, then run the export with the validated parameters.

Check the current input before the agent or script runs the export.

seo reports describe okf-build --json

Once the input is valid, run the export through the report catalog.

seo reports run okf-build --params '{"reportId":"crawl_example_20260710","maxConcepts":25,"includeFiles":true,"title":"Example site knowledge"}' --json

An MCP agent follows the same two-step flow. It inspects the current schema, fills the required fields and only then runs the export.

Ask the MCP server for the current export input.

{
  "id": "okf-build"
}

Run the export after the agent has checked and filled the input.

{
  "id": "okf-build",
  "params": {
    "reportId": "crawl_example_20260710",
    "maxConcepts": 25,
    "includeFiles": true,
    "title": "Example site knowledge"
  }
}

Install the package in a Node 22 project when your application needs to run the export directly. The result includes the same evidence, warnings and limits returned through the CLI and MCP server.

Add the SEO package to your project.

npm install seo

Run the export from your TypeScript application.

import { executeReport } from 'seo/mcp'

const result = await executeReport(
  'okf-build',
  {
  "reportId": "crawl_example_20260710",
  "maxConcepts": 25,
  "includeFiles": true,
  "title": "Example site knowledge"
},
)

console.log(result)

What to do next

Validate the exported pack before another tool or agent uses it. Start from the manifest, confirm the linked artifacts are present and rebuild the pack when the source crawl changes.

01Validate the generated files.
02Rebuild after meaningful information architecture changes.

Validate an Open Knowledge Format pack for paths, sources, trust signals, lifecycle, freshness, and Markdown references before an agent uses it.