Website OKF template
Copy a starter file.
Open pageWebsite guide
Website to OKF guide
Website to OKF starts with URL mapping: choose important public pages, convert them into reviewed Markdown files, and skip private or thin pages instead of scraping everything.
Short answer
Start with high-value URLs, write one OKF file per stable page, and validate the folder before publishing.
What website content belongs in OKF
- Start with homepage, pricing, product, documentation, FAQ, about, contact, policy, and high-value guides.
- Skip duplicate, thin, outdated, or private pages until the source owner reviews them.
- Use canonical URLs as the
resourcefield. - Do not publish private customer records, internal-only support notes, secrets, or restricted legal text.
Create website OKF files step by step
- Create a local folder for the website bundle.
- Add index.md with scope, source owner, update date, and top links.
- Create one Markdown file per important URL.
- Write a short title, description, source URL, tags, and reviewed page summary.
- Validate files with the single-file validator.
- Validate links and duplicate resources with the folder validator.
URL to OKF file mapping
Website source
Concept type
OKF file pattern
Review note
Private fields to exclude
Homepage
Website Page
index.md or pages/home.md
Keep the site summary short and source-linked.
Analytics IDs and private admin links.
Product or feature page
Product Page
pages/product-name.md
Capture stable positioning, limits, and related docs.
Roadmap notes and unreleased pricing.
Help or FAQ page
Support Topic
support/topic-name.md
Preserve support boundaries and escalation notes.
Customer tickets and private account details.
Documentation page
Documentation Topic
docs/topic-name.md
Keep task steps and version notes clear.
Internal runbooks and credentials.
Policy page
Policy Page
policies/policy-name.md
Do not simplify legal or privacy language without owner review.
Attorney notes and non-public revisions.
Thin or duplicate URL
No file until reviewed
No file until merged
Merge into a stronger concept instead of creating thin OKF files.
Everything until the owner approves scope.
Write index and log files
- Use
index.mdto explain bundle scope, owner, source date, and top links. - Use a short change log when source pages materially change.
- Do not update timestamps when only generated draft text changed.
Validate the folder
- Check one file with the OKF Validator.
- Run the OKF Folder Validator for duplicate resources and relative links.
- Review source accuracy with the page owner before publishing.
Per-page OKF example
---
type: Website Page
title: Pricing Page
description: Summarizes pricing tiers, plan limits, refund notes, and upgrade paths.
resource: https://openknowledgeformat.online/sample/pricing/
tags: [website, pricing, product]
timestamp: 2026-06-21T00:00:00Z
---
# Purpose
Explain the stable facts, boundaries, owner notes, and related links for this concept.
# Links
- Validator: https://openknowledgeformat.online/okf-validator/
- Examples: https://openknowledgeformat.online/okf-examples/Evidence and limits
- Do not keyword-stuff OKF fields.
- Do not claim OKF guarantees AI search visibility.
- Keep descriptions factual and short.
- Use internal links only when they help users understand the concept boundary.
- Update timestamps when source pages materially change.
Visual background for website OKF
This video is included as visual background for website-to-OKF learning demand. It is not evidence that OKF guarantees AI search visibility or SEO gains.
Bad website OKF pattern
The weak pattern is one giant file that summarizes the whole site with no canonical resource for each page. That makes review, freshness, and retrieval weaker.
Generated drafts are still drafts
You can generate first drafts from a URL list, but generated OKF remains pending draft content until a source owner checks accuracy, page scope, links, and privacy boundaries.
FAQ
Common questions
Should every URL become an OKF file?
No. Start with stable pages that matter to users, support, search, or agents.
Can OKF replace a sitemap?
No. A sitemap lists URLs for crawlers. OKF adds reviewed knowledge files around selected URLs.
Can I use generated drafts?
Yes, but treat them as drafts until reviewed.
Can private pages go into public OKF?
No. Keep private, restricted, or customer-specific content out of public OKF bundles.
Related pages
Validate the website bundle
After drafting the first files, run both single-file and folder checks before publishing.
Open Folder Validator