Skip to main content

Platform

AEO Website Research-grade Content Content Factory About Audits Rankings Pricing

Resources

Knowledge Base Research FAQ
Audit
OverviewHow to ImproveScore BreakdownSite PagesGuides
onyx.app
WINTER 2024

onyx.app

Moderate AI visibility with 34 of 48 criteria passing. Biggest gap: rss/atom feed.

Developer Tools & InfrastructureDeveloper Platforms
65/100
10 since v1
D
Citation Avg
Answer Readiness
~40% weight
8/10
Content Structure
~25% weight
7/10
Trust & Authority
~15% weight
5/10
Technical Foundation
~10% weight
6/10
AI Discovery
~10% weight
8/10

Verdict

Moderate AEO readiness at 65/100 with significant gaps to address. Key strengths include llms.txt File, robots.txt for AI Crawlers, and Table & List Extractability. Priority gaps: RSS/Atom Feed, Content Licensing & AI Permissions, and Speakable Schema.

How to Improve

Current
65/100
Projected
84/100
35Total Fixes
7Quick Wins
~59hEst. Effort
Quick Wins
Build FAQ sections with schemaAdd ai.txt and content licensingAdd first-hand experience signalsAdd answer-first content placementClarify entity boundariesReduce extraction frictionImprove server response efficiency
Fix HTML structure and meta tags
medium|low
Add internationalization signals
critical|medium
Improve server response efficiency
high|low
Reduce document weight
medium|low
Reduce render-blocking resources
low|low
Create complete sitemap.xml
low|low

Top Opportunities10

Ensure blog content consistently covers your core expertise areas rather than scattering across unrelated topics. AI engines build authority models - a site about "Medicare coverage" that also publishes about humidifiers and groceries dilutes its topical authority.

Strengthen internal linking with descriptive anchor text between related pages. Add breadcrumb navigation and ensure every key page is reachable within 3 clicks from the homepage.

Add Organization schema with consistent name, address, phone (NAP). Include sameAs links to social profiles and authoritative directories to strengthen entity recognition.

Write 20-25 word self-contained answer sentences immediately after each H2 heading. 72.4% of AI-cited posts use this pattern - it gives engines a ready-made snippet to quote.

Create a dedicated FAQ page with FAQPage schema markup. Cover common questions about your products, services, and industry to become a direct answer source for AI engines.

Add question-based headings (H2/H3) throughout your content. Use "What is...", "How does...", "Why should..." patterns that match how users query AI assistants.

Place a concise 40-80 word answer block in the first 300 words of each page. Avoid throat-clearing openers like "In this article..." and lead with the answer.

Define the primary entity in the first 500 characters, use consistent terminology (same term 70%+), and add "unlike X" signals to help AI engines distinguish your topics.

Show direct use, testing, implementation, or lived experience with concrete observations, examples, screenshots, and lessons learned.

Ensure every question-format heading (H2/H3) is followed by a direct answer paragraph. This pattern is ideal for AI engine snippet extraction.

Fix It With AI37

Your competitors are already optimizing for AI

Every day without action is traffic your site loses to AI-ready competitors. We fix that.

Fix My Score

Site Pages

onyx.app/agents-actionsF27
AI Agents & Actions | Onyx AI
onyx.app/oss-friendsF38
OSS Friends | Onyx | Onyx AI
onyx.app/blogF33
Blog | Onyx AI
Changes since v1Last audited 76 days ago
55
65
+10
View full comparison →
Focus Content on Core TopicsImprove Internal Linking ArchitectureStrengthen Entity Authority (NAP)Add Answer Capsule PatternsBuild Comprehensive FAQ SectionRestructure Content as Q&AAdd Answer-First PlacementAdd Entity DisambiguationAdd First-Hand Experience SignalsImprove Question-Answer Alignment

Improve Your Score

Guides for the criteria with the most room for improvement

Related Questions

Browse all FAQs →

Want us to improve your score?

We build citation-ready content that AI engines choose as the answer.

Let's Talk