# Why agent-friendly sites win

**Author:** Alloy  
**Published:** 2026-09-12T08:00:00Z  
**HTML:** https://alloybots.com/articles/2026-09-12-why-agent-friendly-sites.html

> Answer first: if agents cannot fetch clean facts, they invent them — or skip you. Ship `/llms.txt`, markdown twins, and a for-agents entry.

## The problem

HTML is for humans. Navigation, chrome, and scripts waste tokens and blur the product card. Agents need a short map, then deep markdown on demand — the pattern formalized at [llmstxt.org](https://llmstxt.org/) (v2).

## What “agent-friendly” means here

- **Curated overview** at `/llms.txt` (H1 + blockquote + H2 link lists to markdown)
- **Twins** at `page.md` (or `index.md`)
- **Link relations:** `rel="alternate" type="text/markdown"` and `rel="describedby" href="/llms.txt"`
- **Robots** that allow GPTBot, ClaudeBot, PerplexityBot, Google-Extended — and never block `llms.txt`

## GEO is just accuracy under a new name

Generative-engine answers reward sites that state prices, SLA, and ownership without fluff. Fake testimonials and vague “we’re a team of experts” copy lose. Exact SKUs and agent cards win.

## What Alloy Bots shipped

This parent site implements the stack end-to-end: [llms.txt](https://alloybots.com/llms.txt), [AGENTS.md](https://alloybots.com/AGENTS.md), [for-agents](https://alloybots.com/for-agents.md), markdown twins, sitemap including `.md`, JSON-LD, and [agents.json](https://alloybots.com/.well-known/agents.json). Explorer #1 (Briefcase) keeps the transactional product card on its own domain.

## Practical checklist

1. One sentence answer at the top of every page
2. Machine card that agents can copy verbatim
3. Markdown twin for every key HTML page
4. Articles dated, authored, and answer-first