# Why we serve Markdown to AI bots

Instead of publishing a symbolic llms.txt, we detect AI user agents at the edge and serve them a clean Markdown representation of every page on this site. It's a live running system, not a pledge. You can inspect it with one curl command.

## What this is.

A Cloudflare Pages Function runs on every request to winstondigitalmarketing.com. If the User-Agent header matches a known AI crawler. GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, and the rest. The middleware rewrites the response to serve a parallel `.md` file stored under `/content/`. Humans and standard search crawlers continue to receive the normal HTML.

## Why not llms.txt.

llms.txt is a pledge. There's no version history, no enforcement, no observability, and no mechanism to verify that any given bot honored it on any given request.

Edge middleware is different. It's a running system. We can log which agents hit which pages, tune the response per user-agent pattern, version the Markdown outputs alongside HTML, and verify behavior in a single terminal command.

## Inspect it yourself.

```
# What a human browser gets:
curl -s https://www.winstondigitalmarketing.com/ | head -20

# What an AI agent gets:
curl -sH "User-Agent: ClaudeBot/1.0" https://www.winstondigitalmarketing.com/ | head -20
```

The second request returns Markdown with `Content-Type: text/markdown` and an `X-Served-To: ai-agent` response header.

## The receipt.

Full implementation, commit history, and code in the [agent-ready infrastructure receipt](/our-work/agent-ready-infrastructure-for-winstondigitalmarketing-com/). Productized on the [Agentic Web Transformation](/services/ai-marketing/agentic-web/) service page.