Free “Markdown for Agents” (Accept: text/markdown) & Content-Signal Checker

Test in 1 click whether your website or Cloudflare edge serves clean Markdown when AI agents send Accept: text/markdown, measure exact token savings vs. raw HTML, and generate Content-Signal policy headers.

Live HTTP Content Negotiation Result for sitecube.com

Full AI Authority Report (76/100) →
✓ Accept: text/markdown Active ✓ Vary: Accept Cache Header Set ✓ Content-Signal Policy (HTTP Header) ✓ /llms.txt Fallback Active
Fetch Mode HTTP Header Sent Payload Size AI Tokens Token Savings
Standard Browser HTML Accept: text/html 65.4 KB 16,742 Baseline
Markdown for Agents Accept: text/markdown 3.0 KB 756 -95.5%
Static /llms.txt Summary GET /llms.txt 11.0 KB 2,828 -83.1%
✓ Active Content-Signal Policy (HTTP Header): search=yes, ai-input=yes, ai-train=yes (Search: yes · AI RAG Input: yes · Model Training: yes)
Live Preview of Accept: text/markdown Response from sitecube.com
# Sitecube — Free AI Domain Authority Checker & Website AI Visibility Audit

> Check if ChatGPT, Perplexity, Claude, and Google AI can find and recommend your website. Get your free AI Domain Authority score (1–100) and a plain-English checklist of what to fix.

- **Canonical URL:** https://sitecube.com/
- **Submit a Website:** https://sitecube.com/submit
- **AI-Ready Directory:** https://sitecube.com/directory
- **Streamable HTTP MCP Server:** h

1-Click Content-Signal & Markdown Negotiation Config Builder

Cloudflare · Apache .htaccess · Nginx

Frequently Asked Questions

Technical Reference

What is HTTP Accept: text/markdown ("Markdown for Agents")?

Markdown for Agents uses standard HTTP content negotiation: when an AI coding agent or crawler requests a URL with the header Accept: text/markdown, an edge network (such as Cloudflare) or origin server returns clean Markdown instead of bloated HTML—typically cutting token payloads by 80% to 99%.

What does the Content-Signal HTTP header control?

Content-Signal lets publishers declare machine-readable AI permissions across three directives: search (search result indexing), ai-input (real-time RAG/answer grounding), and ai-train (foundation model pre-training)—for example: Content-Signal: search=yes, ai-input=yes, ai-train=no.