AI search visibility report ยท 2026-06-10
How AI assistants see vocode.dev
vocode.dev has an AI visibility score of 40/100. The site passed 15 of 34 tests. Its strongest areas are Technical Accessibility and Citation & Source Quality. The areas to improve are Schema.org Markup and Authority & Trust Signals.
How ChatGPT, Claude and Perplexity read vocode.dev
Readability70/100
Result: average. 3 of 4 tests passed.
Good sentence length and clarity, though the technical nature of the content results in a lower Flesch Reading Ease score.
Schema.org Markup0/100
Result: weak. 0 of 5 tests passed.
Complete absence of JSON-LD structured data, which is a critical failure for LLM optimization.
Authority & Trust Signals8/100
Result: weak. 0 of 5 tests passed.
Lacks essential trust pages (Privacy/Terms) and structured author credentials, though contact email is present.
Citation & Source Quality74/100
Result: average. 3 of 4 tests passed.
High volume of inline citations via GitHub repository links, though lacks links to external authoritative academic or news sources.
Content Freshness30/100
Result: weak. 2 of 4 tests passed.
Visible update signals are present, but the lack of machine-readable publication dates hinders automated recency verification.
Content Structure57/100
Result: weak. 2 of 4 tests passed.
Multiple H1 tags and skipped heading levels create a fragmented structure for LLM parsing.
Entity Definition20/100
Result: weak. 1 of 4 tests passed.
No dedicated about page or Person schema for founders; entity is primarily defined through GitHub profile metadata.
Technical Accessibility100/100
Result: strong. 4 of 4 tests passed.
Excellent technical setup with AI crawler access, social meta tags, and JS-independent content.
How vocode.dev compares to its competitors
- Vapi (vapi.ai) โ score 68/100
- Retell AI (retellai.com) โ score 61/100
- Bland AI (bland.ai)
- ElevenLabs (elevenlabs.io) โ score 56/100