Weak AI visibility with 2 of 22 criteria passing. Biggest gap: llms.txt file.
Verdict
tesora.ai has foundational crawl access in place (HTTPS is enabled, robots.txt and sitemap.xml both return 200, and the sitemap contains 11 URLs), but overall AEO readiness is very low with an overall score of 7. The site is missing nearly all machine-readable trust and extraction signals: no JSON-LD schema blocks, no canonical tag, no llms.txt, no ai.txt, and no RSS/Atom feed. Content structure is also too thin for AI retrieval, with 0 H1 tags, 0 question headings, 0 direct-answer patterns, and no list/table formats. The strongest existing asset is a live FAQ page and a discoverable sitemap, but both need markup and freshness signals to become citation-ready.
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.
Most AI crawlers don't run JavaScript. If your content loads after page render -behind accordions, SPAs, or API calls -you're invisible. We've seen entire FAQ sections vanish from AI's perspective because of one accordion widget.
Want us to improve your score?
We build citation-ready content that AI engines choose as the answer.