GEO / Agent Readiness

Markdown content negotiation

Also known as Accept: text/markdown · Markdown variant

Serving a clean Markdown representation of a page when a client requests it via the Accept: text/markdown header.

What it is

Content negotiation is the HTTP mechanism where a server returns different representations of the same URL based on request headers, chiefly Accept. Markdown content negotiation means that when a client sends Accept: text/markdown, the server responds with a token-efficient Markdown version of the page instead of full HTML. The HTML variant should advertise the alternative with a Vary: Accept header.

Why it matters

LLMs and AI agents parse Markdown far more reliably than markup-heavy HTML laden with navigation, ads, and scripts, and Markdown costs fewer tokens to ingest. Offering a Markdown variant gives answer engines a clean, unambiguous version of your content, improving the accuracy of summaries and citations.

How to verify

Run curl -s -H 'Accept: text/markdown' https://example.com/page and confirm the body is Markdown (not HTML) with a Content-Type: text/markdown response header. Compare against a normal curl without the header to verify the server actually branches on Accept, and check for a Vary: Accept header so caches behave correctly.

How to fix

Add server or edge logic that inspects the Accept header and returns a stored or generated Markdown rendering of the page with Content-Type: text/markdown and Vary: Accept. Alternatively expose a parallel .md URL (for example /page.md) linked from the HTML so agents can fetch the clean text deterministically.

In the checklist

This concept maps to a check in the GEO Score checklist.

Use the checklist

Related terms

Official references

External, opens in a new tab.

Put this into practice.

Work through every check by hand and turn it into a shareable GEO Score report — or scan your site automatically in seconds.