Content Checks

Agents don't render HTML the way a browser does. They strip it down, look for headings and meta, and try to extract clean prose. Help them by exposing content in formats they don't have to fight.

C1 — Markdown content negotiation (weight 8)

AIScan re-requests your homepage with Accept: text/markdown. If the server replies with atext/markdown content-type and the body looks like markdown (headings, lists, links), the check passes.

How to fix

Two approaches:

• Content negotiation — at the edge or in your framework, when Accept includes text/markdown, render the same page as Markdown instead of HTML.
• Sidecar URLs — also serve /path/index.md alongside /path. Easier for static sites.

C2 — /llms.txt (weight 6)

Per llmstxt.org, /llms.txt is a markdown file that gives agents a curated index of your site. AIScan checks that the file exists, returns 200, and contains an H1, at least one ## section, and markdown links.

How to fix

Drop a file at the root of your site that looks like:

# Acme Inc.

> A short summary of what Acme does — one or two sentences.

## Docs
- [Getting started](https://acme.com/docs/getting-started.md)
- [API reference](https://acme.com/docs/api.md)

## Examples
- [Example app](https://acme.com/examples/app.md)

C3 — Structured HTML (weight 4)

Four basic signals on your homepage: a single <h1>, a non-empty <title>, a <meta name="description">, and at least one application/ld+jsonblock. One point each.

How to fix

For JSON-LD, start with an Organization or WebSite schema sitewide, then add page-type-specific schemas (Article, Product, FAQPage) on the pages that match. Validators: schema.org validator.