Moderate AI visibility with 36 of 53 criteria passing. Biggest gap: llms.txt file.
Verdict
Moderate AEO readiness at 63/100 with significant gaps to address. Key strengths include Internal Linking Structure, Direct Answer Paragraphs, and Fact & Data Density. Priority gaps: llms.txt File, RSS/Atom Feed, and Content Licensing & AI Permissions.
How to Improve
Update robots.txt to explicitly allow AI crawlers and include sitemap directive.
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.
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.
Trim oversized HTML, excessive DOM nodes, and large inline payloads that slow AI crawlers.
545/626 images lack explicit width/height - the most common cause of layout shift (CLS)
Ensure clean, well-structured HTML with proper meta tags, HTTPS, and parseable content for AI crawlers.
Generate a comprehensive sitemap with lastmod dates for all important pages.
Optimize compression, cache headers, redirect chains, and HTML payload size for faster AI crawler access.
Top Opportunities10
View allWrite 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.
Add question-based headings (H2/H3) throughout your content. Use "What is...", "How does...", "Why should..." patterns that match how users query AI assistants.
Ensure every question-format heading (H2/H3) is followed by a direct answer paragraph. This pattern is ideal for AI engine snippet extraction.
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.
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.
Include dateModified schema, visible last-updated dates, and time elements on content pages. Fresh content signals help AI engines prioritize your pages over stale alternatives.
Add inline citations to external sources, "According to [Source]..." attribution phrases, and a Sources section at the end of key articles.
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.