Weak AI visibility with 5 of 22 criteria passing. Biggest gap: llms.txt file.
Verdict
dalus.io has a technically crawlable foundation (HTTPS enabled, semantic elements like main/nav/footer/section, and 74,448 characters of accessible homepage text), but it is not AEO-ready in its current state. Core machine-readable signals are missing: /llms.txt (404), /robots.txt (404), /sitemap.xml (404), canonical tags, and homepage JSON-LD (schema_block_count: 0). Content depth exists (15 quantitative data points, case studies, and a blog section), yet extraction-focused formatting is weak with zero question headings, zero definition patterns, and no direct Q&A blocks. The site can improve quickly by adding governance files, structured data, and answer-first content patterns that AI engines can reliably parse and cite.
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.