Agent-Readable Site Vet
Run a proxy's-eye audit of your site, styles stripped
- Problem
- When agents read the web in place of people, signals that only exist visually stop working. Developers don't know what their site looks like to a proxy or crawler, or which information is silently invisible to them.
- Solution
- Enter a URL: it renders the page, strips the stylesheet, and simulates common agent fetch paths, then shows a side-by-side of what humans see versus what machines actually read — flagging CSS/JS-hidden content, missing semantic markup, and layouts that block consumption.
- Users
- Indie developers with product and docs sites, content teams owning SEO and AI visibility
- MVP
- URL in, unstyled view out; highlight machine-visible vs invisible text blocks; check heading hierarchy, semantic tags, crawler-reachable links; an impact-ranked fix list; shareable report link
- Revenue
- Free one-off reports + subscription for bulk scanning and historical tracking; add a one-pager agent-readability consulting service
- Why now
- Agents and AI crawlers are becoming primary readers while most sites still optimize for human eyes; render-and-compare logic is simple enough to ship cheaply
Source discussions · 2
- Hacker NewsShow HN: Undersheet2↑ 0
- Hacker NewsShow HN: I had 100 tabs open, so I built Daysift with AI powered by Proton2↑ 0