Weak AI visibility with 3 of 22 criteria passing. Biggest gap: llms.txt file.
Verdict
theopenbuilder.com has basic crawlability foundations in place (HTTPS enabled, one clear H1, substantial text content, and semantic nav/header/footer usage), but it is not AEO-ready in its current state. Critical machine-readable assets are missing, including `llms.txt` (404), `robots.txt` (404), `sitemap.xml` (404), JSON-LD schema (0 blocks), canonical tags, and RSS feed support. Content is also hard for AI systems to extract and cite because there are no question-format headings, no direct answer paragraphs, no FAQ page, and no visible structured evidence such as statistics, author schema, or source attributions. The current profile is a high-upside rebuild opportunity: foundational fixes can materially improve discovery, parsing, and citation likelihood.
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.