AI Visibility
measured82/100
Frequently Cited · in Version Control
counts brand mentions in AI answers, not source citations
AEO Readiness
fundamentals30/100
Weak fundamentals
Avg Prompt Score
62
across 349 prompts
AI Share of Voice
64%
across 333 prompts
Critical Issues
4
critical + high
How AI Visibility breaks down
in Version Control
Composite = 60% coverage + 40% engine breadth, measured in the brand's strongest category. Position and citation depth join the score once the aggregation pipeline captures them. This is the measured Visibility score — separate from AEO Readiness, which scores fundamentals.
Cited rate · share of voice · engine consensus · sentiment, broken out by buyer-journey stage. Sentiment is the net positive−negative skew across engines that cited the brand at this stage.
github.io is primarily a hosting/namespace for GitHub Pages rather than a B2B SaaS product with a dedicated pricing/comparison surface, so AI engines have limited reason to cite it for “best software” evaluation queries. The highest-ROI fix is to ensure the specific GitHub Pages documentation pages you want cited have crawlable, structured Q&A (FAQPage) and clear “what it is / who it’s for” sections—because first-party evaluation-style content is what AI needs to answer conversion-stage questions.
Based on audit of github.io · Jun 9, 2026