Weak AI visibility with 5 of 22 criteria passing. Biggest gap: llms.txt file.
Verdict
linum.ai has a crawlable HTTPS foundation, a valid robots.txt, sitemap, and an active feed endpoint, but overall AEO readiness is low due to major machine-readability gaps. The site currently returns 404 for both /llms.txt and /faq, has zero JSON-LD schema blocks, and lacks a canonical tag, leaving AI systems with weak entity and content signals. On-page extraction is also limited: no H1, no question headings, no direct-answer patterns, and no list/table structures for easy parsing. With an overall score of 14, the highest-leverage path is to add structured metadata and answer-first content architecture quickly.
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.
AI assistants are question-answering machines. When your content is already shaped as questions and answers, you're handing AI a pre-formatted citation. Sites that do this right get extracted -sites that don't get skipped.
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.
Want us to improve your score?
We build citation-ready content that AI engines choose as the answer.