Moderate AI visibility with 33 of 53 criteria passing. Biggest gap: llms.txt file.
Verdict
Below-average AEO readiness at 55/100 - multiple areas need attention. Key strengths include Direct Answer Paragraphs, Canonical URL Strategy, and Content Cannibalization. Priority gaps: llms.txt File, RSS/Atom Feed, and Speakable Schema.
How to Improve
1 sampled page(s) carry a noindex 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.
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.
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.
176/200 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.
Top Opportunities10
View allExpand 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.
Publish 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.
Add specific numbers, percentages, statistics, and data points throughout your content. Fact-dense content gives AI engines concrete data to cite rather than vague claims.
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.
Add question-based headings (H2/H3) throughout your content. Use "What is...", "How does...", "Why should..." patterns that match how users query AI assistants.
Write self-contained definition sentences and single-claim statements that AI engines can quote directly. Avoid pronouns like "this" or "that" at the start of answer paragraphs.
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.
Rewrite multi-clause sentences into single-claim statements under 20 words. Pages with Flesch-Kincaid grade 16 outperform grade 19 in citation rates.
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.