Weak AI visibility with 4 of 22 criteria passing. Biggest gap: llms.txt file.
Verdict
usehaven.ai currently has low AEO readiness with an overall score of 23/100, driven by major discoverability and machine-readability gaps. Ten of 22 criteria scored 0, including llms.txt, structured data, sitemap, RSS/Atom, canonical tags, FAQ coverage, and schema depth. The technical base is partially solid (9/10 for clean crawlable HTML with HTTPS and correct H1 usage), but AI extractability remains weak with 0 internal links, no JSON-LD blocks, and no freshness metadata. In its current state, the site can be crawled, but it is not well-structured for AI systems to interpret, trust, and cite.
Scoreboard
Fix It With AI
Copy-paste these prompts into Claude Code or Cursor to fix each criterion.
These prompts are designed for projects where you have direct access to the codebase (Next.js, React, static HTML, WordPress, etc.). If your site runs on a hosted platform like Webflow, switch to the "Webflow" tab for platform-specific instructions. Using a different hosted platform? Contact us for custom guidance.
Top Opportunities
Improve Your Score
Guides for the criteria with the most room for improvement
Tidio has a 251-line llms.txt. Crisp has zero. The score gap: +29 points. This single file tells AI assistants exactly what your site does -and without it, they're guessing.
Tidio runs 4 JSON-LD schema types. Crisp runs zero. That's not a coincidence -it's the difference between a 63 and a 34. Structured data is the machine-readable layer AI trusts most.
Our site runs 87 FAQ items across 9 categories with FAQPage schema on every one. That's not excessive -it's how we hit 88/100. Each Q&A pair is a citation opportunity AI can extract in seconds.
No date on your page? AI engines treat it like a rumor -undated and deprioritized. Here's how we audit whether your timestamps are actually machine-readable.
Want us to improve your score?
We build citation-ready content that AI engines choose as the answer.