Making agent-friendly pages with content negotiation
By Steven Van ·
Vercel now serves markdown to agents on its own docs, blog and changelog, and published a Next.js guide for sites to do the same.
Vercel has started serving markdown instead of HTML to agents that request it, using standard HTTP content negotiation rather than separate URLs. When a client sends an Accept: text/markdown header, the server returns clean structured text from the same address that serves HTML to a browser. Vercel has already updated its own blog, changelog and documentation pages to respond this way.
Vercel also published a guide showing how to add the same behaviour to a Next.js site:
- A rewrite rule in next.config.ts checks incoming requests for the markdown Accept header and routes matching ones to a dedicated markdown endpoint.
- A Route Handler returns the markdown version of each page.
- A markdown sitemap lists every page reachable this way, so an agent can keep searching if the first page doesn't have what it needs.
Vercel
The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.
View Vercel →