Formats

Geordy generates 8 file types. Here's what each one does and when to use it.

Start with three: Schema JSON + Markdown + llms.txt. Add the rest when you're ready to deploy them.

llms.txt

.txtHomepage only

Plain-text directive file for large language models. Tells AI systems what your site is, what matters, and how to navigate it.

When: Always. This is the first file AI systems look for.
ai.yourdomain.com/llms.txt

Markdown

.mdPer page

Clean, readable version of your page content stripped of layout, scripts, and styling. Pure meaning.

When: Every page you want AI to understand clearly.
ai.yourdomain.com/about/team.md

Schema JSON

.schema.jsonPer page

Structured data describing what the page represents — product, article, organization, FAQ, etc. Uses JSON-LD vocabulary.

When: Every page. This is the most impactful format for AI comprehension.
ai.yourdomain.com/about/team.schema.json

YAML

.yamlPer page

Lightweight key-value structured data. Same meaning as Schema JSON in a more compact syntax.

When: When you want a human-readable alternative to JSON.
ai.yourdomain.com/about/team.yaml

OG.json

.og.jsonPer page

Open Graph metadata exported as a JSON file. Title, description, image, type — the same data social platforms use.

When: When you want AI to access your social/share metadata programmatically.
ai.yourdomain.com/about/team.og.json

RSS (.xml)

.xmlPer page

RSS feed entry for the page. Useful for content that updates — blog posts, products, news.

When: Pages that publish updates. Not needed for static pages.
ai.yourdomain.com/about/team.xml

manifest.json

.manifest.jsonPer page

App-style manifest metadata for the page. Name, description, icons, theme.

When: Nice-to-have. Lower priority than Schema JSON and Markdown.
ai.yourdomain.com/about/team.manifest.json

humans.txt

.txtHomepage only

Human-readable credits file. Who built the site, what tools were used, acknowledgements.

When: Optional. A small courtesy for transparency.
ai.yourdomain.com/humans.txt

How URLs map to files

Two files live only at the root: /llms.txt and /humans.txt. Everything else mirrors your site's URL paths.

Homepage

/index.md
/index.schema.json
/index.yaml
/index.og.json
/index.xml
/index.manifest.json

/pricing

/pricing.md
/pricing.schema.json
/pricing.yaml
/pricing.og.json
/pricing.xml
/pricing.manifest.json
Back to SetupCredits and usage