Moderate AI visibility with 39 of 53 criteria passing. Biggest gap: llms.txt file.
Verdict
Moderate AEO readiness at 61/100 with significant gaps to address. Key strengths include Internal Linking Structure, Sitemap Completeness, and Direct Answer Paragraphs. Priority gaps: llms.txt File, Content Licensing & AI Permissions, and Speakable Schema.
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.
Ensure clean, well-structured HTML with proper meta tags, HTTPS, and parseable content for AI crawlers.
Implement hreflang tags and lang attributes so AI engines serve the correct language version when answering queries.
317/424 images lack explicit width/height - the most common cause of layout shift (CLS)
Minimize blocking scripts and stylesheets in <head> to improve content availability for AI crawlers.
Trim oversized HTML, excessive DOM nodes, and large inline payloads that slow AI crawlers.
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.
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.
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.
Add inline citations to external sources, "According to [Source]..." attribution phrases, and a Sources section at the end of key articles.
Show direct use, testing, implementation, or lived experience with concrete observations, examples, screenshots, and lessons learned.
Use HTML tables for comparison data and ordered/unordered lists for features, steps, and specifications. Structured data formats are directly extractable by AI engines for answers.
Add Organization schema with consistent name, address, phone (NAP). Include sameAs links to social profiles and authoritative directories to strengthen entity recognition.
Add question-based headings (H2/H3) throughout your content. Use "What is...", "How does...", "Why should..." patterns that match how users query AI assistants.
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.
Create an /ai.txt file specifying AI usage permissions and add license schema to your structured data. Clear licensing signals help AI engines understand how they can use your content.