Moderate AI visibility with 13 of 22 criteria passing. Biggest gap: rss/atom feed.
Verdict
vespper.com shows a solid technical base for AEO but is only mid-readiness overall (score 51) because key extraction and governance signals are missing. Strong foundations include a live `llms.txt` (HTTP 200, 8,977 chars), valid sitemap coverage (39/39 URLs with `lastmod`), and active schema implementation (3 JSON-LD blocks including `Organization`, `FAQPage`, and `Person`). The biggest blockers are missing canonical tags, no RSS/Atom feed, no `ai.txt`, weak question-answer formatting (`question_headings_count: 0`), and low extractable structure (no tables, `<ol>`, or `<ul>`). With targeted fixes to content format, crawl directives, and metadata, the site can move from partially discoverable to consistently citable by AI engines.
Scoreboard
Top Opportunities
Improve Your Score
Guides for the criteria with the most room for improvement
Sitemaps tell crawlers what exists. RSS feeds tell them what changed. If you don't have one, your new content waits days -or weeks -to be discovered.
Your sitemap says 500 pages exist. Our crawl finds 700. Those 200 missing URLs? AI crawlers will never know they exist.
You published a great blog post in January. It's now February and nothing else has appeared. AI engines notice -and they're crawling less often because of it.
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.
Want us to improve your score?
We build citation-ready content that AI engines choose as the answer.