Weak AI visibility with 2 of 22 criteria passing. Biggest gap: llms.txt file.
Verdict
reticular.ai has a technically crawlable foundation (HTTPS enabled, substantial server-rendered text, and semantic elements like main/nav/header/footer/section), but overall AEO readiness is low at 18 because core machine-readable discovery assets are absent. The biggest blockers are missing llms.txt, robots.txt, sitemap.xml, canonical tags, FAQ surface, and any JSON-LD schema (schema_block_count: 0, schema_types_found: []). Content is readable for humans, yet weak for AI extraction due to zero question headings, zero direct-answer patterns, zero definition patterns, and no factual/statistical density. In short: strong baseline HTML hygiene, but missing the structural and policy signals AI engines rely on for citation and retrieval.
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.