Weak AI visibility with 0 of 10 criteria passing. Biggest gap: llms.txt file.
Verdict
purplebinder.com has basic technical foundations like HTTPS and a valid sitemap, but critical AEO gaps prevent strong AI discoverability. The site lacks llms.txt and FAQ infrastructure, and key pages expose weak crawl/index patterns including `noindex` meta directives and multiple broken nav destinations. Existing structured data is minimal (`WebSite` and `BlogPosting` only) and does not yet provide the rich entity and Q&A context AI engines prefer.
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.
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 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.