Geordy takes a page from your site and produces extra machine-readable versions of it — so AI systems can understand what the page means without guessing.
Your site looks the same to visitors. You're just adding a clean, structured layer for machines.
What you get (the practical output)
Not advice. Not a report. You get files you can actually use:
The shortest path to value
10-15 minutes. One page. One win.
1. Pick one page
Choose your homepage, a top landing page, pricing, or your best product/category page. Drop that URL into Geordy and generate the formats.
Why: You want one clean win before scaling.
2. Enable the right formats
Start with Schema JSON, Markdown, and llms.txt (homepage only). Add OG.json, YAML, RSS, manifest, and humans.txt when ready.
Rule: Enable what you'll actually deploy.
3. Put files somewhere accessible
You have two options — either works:
Option A — use Geordy's URL (no DNS setup needed)
Your files are already live at Geordy's address the moment they're generated. You can reference them directly:
files.geordy.ai/yourdomain.com/llms.txt. No configuration required. Good for getting started quickly, or for sites where adding a subdomain isn't practical.Option B — your own subdomain (recommended)
Pick a subdomain (e.g.
ai.yourdomain.com). Add one DNS A record pointing to:178.156.151.211This keeps files under your own domain, which is better for brand trust and SEO signals.
4. Verify it works
Open
ai.yourdomain.com/llms.txtin your browser. If it loads, you're done.5. Add reference tags
Add
<link rel="alternate">tags in your <head> pointing to the files on your subdomain.Homepage (8 files)
<link rel="alternate" href="https://ai.yourdomain.com/llms.txt" /><link rel="alternate" href="https://ai.yourdomain.com/humans.txt" /><link rel="alternate" href="https://ai.yourdomain.com/index.md" /><link rel="alternate" href="https://ai.yourdomain.com/index.schema.json" /><!-- + index.yaml, index.og.json, index.xml, index.manifest.json -->Inner pages (6 files, no llms.txt/humans.txt)
<link rel="alternate" href="https://ai.yourdomain.com/about.md" /><link rel="alternate" href="https://ai.yourdomain.com/about.schema.json" /><!-- + about.yaml, about.og.json, about.xml, about.manifest.json -->The slug matches the page path. /about → about.md, /pricing → pricing.md
Files that exist but aren't referenced are like a great book left in a drawer.
Post-deployment verification
Three checks to confirm everything is working:
ai.yourdomain.com/llms.txt in browser. If the file loads, DNS is configured correctly.llms.txt or your subdomain. The link tags should appear in the <head>.How URLs map
Two files live only on the homepage: /llms.txt and /humans.txt. Everything else mirrors your site paths.
Homepage
/index.schema.json
/index.yaml
/index.og.json
/index.xml
/index.manifest.json
Inner page: /about/team
/about/team.schema.json
/about/team.yaml
/about/team.og.json
/about/team.xml
/about/team.manifest.json
Scaling up
- Do the Top 5 rollout. Homepage, pricing, top category, top product, about/credibility page. This gives AI a complete picture fast.
- Use sitemap import. Once the pipeline works, import your XML sitemap and process in batches. Prioritize money pages first.
- Add dynamic link tags to your sitewide head. Instead of hardcoding tags per page, add a single template to your global
<head>that builds file URLs from the current page path automatically.Dynamic pattern
<link rel="alternate" href="https://ai.{domain}/{slug}.md" />Where
{slug}= current page path (or "index" for homepage)Benefits: Tags auto-generate for every page. New pages are covered automatically. No manual updates needed.
- Keep auto-updates on for pages that change. Products, categories, frequently edited marketing pages. Pause auto-updates if you manually edit a format and want to lock it.
- When something looks off, fix the source page first. If a generated format feels wrong, the original page is usually unclear to machines. Fix the page, regenerate.