Weak AI visibility with 4 of 22 criteria passing. Biggest gap: llms.txt file.
Verdict
freyavoice.ai has a usable technical foundation for crawling (HTTPS enabled, substantial indexable text at 10,743 characters, and clean title/meta basics), but it is not AEO-ready in its current state. Core machine-readable discovery assets are missing: /llms.txt returns 404, /sitemap.xml returns 404, no JSON-LD schema is present (schema_block_count: 0), and no canonical tag is detected. Content is also hard for AI systems to extract efficiently, with only one question-style heading, no FAQ endpoint (/faq is 404), and no list/table structures. The result is low visibility and citation potential despite having meaningful on-page copy and some quantitative claims.
Scoreboard
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.