Weak AI visibility with 3 of 22 criteria passing. Biggest gap: llms.txt file.
Verdict
sciloop.dev has a technically crawlable base (HTTPS enabled, semantic elements like main/nav/footer/section, and accessible text content), but overall AEO readiness is very low at 16/100. Core machine-readable discovery assets are missing, including `llms.txt` (404), `robots.txt` (404), `sitemap.xml` (404), and any JSON-LD schema blocks (0 found). Content is also under-structured for AI extraction, with no FAQ page, no question headings, no lists/tables, and only 9 internal links on the homepage. The site has a usable foundation, but it currently lacks the trust, structure, and indexing signals AI engines rely on for citation.
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.
AI has a trust hierarchy for sources. At the top: proprietary data and first-hand expert analysis. At the bottom: rewritten Wikipedia articles. We've watched AI preferentially cite sites with original benchmarks -even over bigger competitors.
Want us to improve your score?
We build citation-ready content that AI engines choose as the answer.