Moderate AI visibility with 38 of 53 criteria passing. Biggest gap: llms.txt file.
Verdict
Below-average AEO readiness at 57/100 - multiple areas need attention. Key strengths include Clean, Crawlable HTML, Sitemap Completeness, and RSS/Atom Feed. Priority gaps: llms.txt File, Answer Capsule Pattern, and Owned Data Density.
How to Improve
Add a machine-readable llms.txt file at your domain root that describes your site, services, and key pages for AI engines.
Create a comprehensive llms-full.txt with detailed page descriptions, content summaries, and topic taxonomy.
Update robots.txt to explicitly allow AI crawlers and include sitemap directive.
Implement hreflang tags and lang attributes so AI engines serve the correct language version when answering queries.
Minimize blocking scripts and stylesheets in <head> to improve content availability for AI crawlers.
134/157 images lack explicit width/height - the most common cause of layout shift (CLS)
Optimize compression, cache headers, redirect chains, and HTML payload size for faster AI crawler access.
Top Opportunities10
View allPublish original research, statistics, case studies, or proprietary data that AI engines can cite. Unique data points make your content a primary source rather than a derivative one.
Expand articles to 1000+ words with structured H2/H3 sections, comparison tables, and expert analysis. Thin content (under 300 words) is rarely cited by AI engines. Deep, well-structured articles demonstrate expertise.
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.
Write concise, standalone answer paragraphs (2-3 sentences) immediately after question headings. These "snippet-ready" paragraphs are ideal for AI engine citations.
Include "our analysis", "our data", "our testing" phrases backed by original research or proprietary data. 52.2% of AI-cited posts contain owned data signals.
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 inline citations to external sources, "According to [Source]..." attribution phrases, and a Sources section at the end of key articles.
Add question-based headings (H2/H3) throughout your content. Use "What is...", "How does...", "Why should..." patterns that match how users query AI assistants.
Show direct use, testing, implementation, or lived experience with concrete observations, examples, screenshots, and lessons learned.
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.