Enterprise format · Growth plan

Steno

Compact representation for repeated terms.

3 / 5GEO score
STENO · Geordycontent.steno
Why it matters

A Steno dictionary is structurally a JSON map from outline to phrase. Borrowed from stenography and reframed for publishing, it lets you declare every acronym, internal codename, and bot user-agent you mention on the site and bind each to a single canonical expansion. LLMs and crawlers reading the file get an unambiguous lookup table for your vocabulary instead of guessing whether "GPTBot" and "GPT/PWBOT" are the same thing.

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 outputcontent.steno
{
  "GEO": "Generative Engine Optimization",
  "LLMO": "Large Language Model Optimization",
  "GPT/PWBOT": "GPTBot",
  "KHRAUD/PWBOT": "ClaudeBot",
  "PER/PLEBGT/PWBOT": "PerplexityBot",
  "TKPWRAO/TKEU": "Geordy",
  "SREPBL/PWEUGT": "AI visibility"
}
Get it right

How to make this format work for AI.

DoBest practices
  • Keep the file as plain JSON (the Plover-native shape) so any parser can read it without a custom loader.
  • Map every brand-specific shorthand, product code, acronym, and bot user-agent to its full, human-readable form.
  • Treat the dictionary as the source of truth - link to it from your llms.txt so AI engines find it during ingestion.
  • Version the file alongside the rest of your structured-data outputs; entries are cheap to add, expensive to drift.
AvoidCommon pitfalls
  • Letting the dictionary drift from the spelling used in your prose and schema - AI engines reconcile across signals and a mismatch flags noise.
  • Treating it as a thesaurus instead of a glossary - one outline should map to one canonical phrase, not a list of synonyms.
  • Inventing outlines that aren't real Plover strokes - the file still parses as JSON, but you lose round-trip compatibility with steno tooling.
Where it shines

Use cases, scored for AI visibility.

Brand and product glossaryGEO 4/5
Acronym / abbreviation expansionGEO 4/5
Bot user-agent normalizationGEO 3/5
Used in production by

Real sites already shipping Steno.

Working with it

Tools & resources for Steno.

The trade-offs
Strengths
  • Plain JSON the same shape as a Plover dictionary - easy to author and version-control
  • Every shorthand or abbreviation maps to one canonical phrase
  • Acts as a brand glossary AI engines can read deterministically
Spec sheet
Filename
content.steno
Refresh cadence
weekly
Released
2010 · Open Steno Project (Plover)
Written forChatGPTClaudePerplexity

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

Documented support
Observed requests

Not measured yet. Geordy will publish which crawlers request this file once enough independent sites are covered. See how we measure.

Other enterprise 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.

Steno (.steno) format - spec, examples and AI readers | Geordy