New: one-click agent content preview for any URL
Paste a URL, see exactly what AI agents get vs. what they should get. The new Agent Preview tool shows the difference in seconds.
Just shipped: paste any URL into the new Agent Preview tool and see exactly what an AI agent gets when it visits that page. Side by side, no signup, takes about two seconds.
It fetches your page twice: once as a normal HTML request, once with the Accept: text/markdown header that agents send. If your site already supports content negotiation, you'll see your actual markdown response. If it doesn't, we generate an ideal version so you can see what agents should be getting.
HTML lands on the left, markdown on the right. The difference is usually pretty striking.
The signal ratio
We calculate a signal ratio for each version. A typical HTML page carries around 12% useful content. The rest is nav, scripts, cookie banners, tracking pixels, layout markup. The markdown version usually comes in above 90%.
The file size delta tells the same story from a different angle. A page that weighs 400KB as HTML might compress down to 15KB of clean markdown. That adds up fast when an agent is processing a bunch of pages in a single task.
This vs. the full audit
Agent Preview is a single-page tool: one URL, one comparison. It's built for quick checks, curiosity, or showing a teammate why content negotiation actually matters.
The audit tool is the full picture.
| Agent Preview | Audit | |
|---|---|---|
| Pages checked | 1 | Up to 10 |
| Speed | Instant | ~30 seconds |
| Output | Side-by-side preview | Scored dashboard |
| Checks run | Signal ratio, size delta, content negotiation | 7 checks with weighted scoring |
| Best for | Quick preview, sharing with teammates | Full site assessment, tracking readiness |
Think of Agent Preview as the hook. It shows you the problem fast. The audit tells you how to fix it across your whole site.
Copy and use the output
There's a copy button on the markdown panel. Grab it and use it however you want. Drop it into a prompt, compare it against your own markdown endpoint, use it as a reference for what your content negotiation response should look like.
Note
If your site already serves markdown via content negotiation, Agent Preview will detect that and show your actual response instead of a generated version. A quick way to verify your implementation works.
Give it a try at agentready.dev/agent-preview. If the result surprises you, run the full audit next. Happy to hear what you find.