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
    - Perplexity
Get 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
Written forChatGPTClaudePerplexityBuild toolsRAG pipelines

Written for these readers. Which of them actually request it is measured, not assumed: see how we measure.

Documented support
Observed requests

Share of eligible sites where each crawler requested this file at least once, over the 90 days to 15 November 2026.

YAML: observed requests by crawler
CrawlerEvidenceSites with a request
OAI-SearchBotEmerging patternabout 50%
ChatGPT-UserEmerging patternabout 50%
GPTBotEmerging patternabout 50%
PerplexityBotEmerging patternabout 50%
Meta-ExternalAgentEmerging patternabout 50%
AmazonbotEmerging patternabout 50%
Claude-SearchBotEmerging patternabout 30%
ClaudeBotEmerging patternabout 20%
Perplexity-UserEmerging patternabout 20%
bingbotEmerging patternabout 20%
ApplebotEmerging patternabout 20%
BytespiderEmerging patternabout 20%
YouBotEmerging patternabout 20%
GooglebotEmerging patternabout 10%
Claude-UserEmerging pattern0%
Claude-WebEmerging pattern0%
anthropic-aiEmerging pattern0%
Google-CloudVertexBotEmerging pattern0%
Meta-ExternalFetcherEmerging pattern0%
FacebookBotEmerging pattern0%
CCBotEmerging pattern0%
DuckAssistBotEmerging pattern0%
MistralAI-UserEmerging pattern0%
cohere-aiEmerging pattern0%
DiffbotEmerging pattern0%
TimpibotEmerging pattern0%
PetalBotEmerging pattern0%

Figures are rounded and cover only sites that served the file for the whole window and were reached by crawlers at least once in it; sites with no crawler requests at all are left out. Requests are to Geordy-served files, identified by user agent; a request is not evidence of use or citation. Pairs with too few independent sites are not shown. See how we measure.

Other core formats

Generate every format at once.

Geordy emits 8 formats on every plan and 16 on Growth, auto-selected per page type and live on Geordy the moment they are written.

YAML (.yaml) format - spec, examples and AI readers | Geordy