Core format · included on every plan
YAML
Page metadata, indentation-clean.
5 / 5GEO score
YAML · Geordyindex.yaml
Why it matters
YAML is the lingua franca of configuration in the AI/ML stack - model cards, prompt templates, agent definitions, OpenAPI specs, GitHub Actions, and Kubernetes all use it. LLMs generate and read it fluently, so publishing config and metadata in valid YAML lets agents and AI engines manipulate your system without an HTML scraper.
Geordy generates this format for every page on your site that warrants it - auto-detected by page type, served from your subdomain, and refreshed on the cadence below.
Sample outputindex.yaml
# AI Optimization Configuration
site:
name: "Geordy AI Platform"
domain: "geordy.ai"
category: "GEO / LLMO"
ai_targeting:
primary_systems:
- ChatGPT
- Claude
- PerplexityGet it right
How to make this format work for AI.
DoBest practices
- Always use 2-space indentation, never tabs - tabs are explicitly forbidden by the spec for indentation.
- Quote strings that look like booleans, numbers, or dates (`"yes"`, `"01:23"`, `"2026-05-12"`) to avoid implicit type coercion (the famous Norway problem: `NO` -> false).
- Use block style (`key:` newline + indent) for anything human-edited; reserve flow style (`{a: 1}`) for short inline values.
- Validate against a JSON Schema where possible (e.g. `yaml-language-server: $schema=...`) so editors and CI catch errors early.
AvoidCommon pitfalls
- Trusting `yaml.load()` in PyYAML on untrusted input - it can execute arbitrary Python; always use `yaml.safe_load()`.
- Unquoted version strings like `1.10` parsed as the float `1.1`, silently breaking downstream tooling.
- Mixed indentation across a single block (3 spaces here, 4 there) - most parsers fail with cryptic errors far from the actual line.
Where it shines
Use cases, scored for AI visibility.
Human-editable configuration filesGEO 5/5
Documentation frontmatterGEO 5/5
When readability is prioritizedGEO 4/5
Used in production by
Real sites already shipping YAML.
Working with it
Tools & resources for YAML.
The trade-offs
Strengths
- Human-readable syntax with minimal punctuation
- Widely supported across programming languages and platforms
- Eliminates bracket clutter through indentation-based structure
Limitations
- Indentation-sensitive (error-prone)
- Slower parsing than JSON
- Security concerns with unsafe loading
Spec sheet
Filename
index.yaml
Refresh cadence
weekly
Released
2001 · Clark Evans, Ingy döt Net, Oren Ben-Kiki
Read byChatGPTClaudePerplexityBuild toolsRAG pipelines
Other core formats