Moderate AI visibility with 34 of 53 criteria passing. Biggest gap: llms.txt file.
Verdict
Below-average AEO readiness at 56/100 - multiple areas need attention. Key strengths include Sitemap Completeness, Direct Answer Paragraphs, and Fact & Data Density. Priority gaps: llms.txt File, RSS/Atom Feed, and Speakable Schema.
How to Improve
8 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.
Minimize blocking scripts and stylesheets in <head> to improve content availability for AI crawlers.
Implement hreflang tags and lang attributes so AI engines serve the correct language version when answering queries.
Ensure clean, well-structured HTML with proper meta tags, HTTPS, and parseable content for AI crawlers.
Trim oversized HTML, excessive DOM nodes, and large inline payloads that slow AI crawlers.
787/970 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.
Add inline citations to external sources, "According to [Source]..." attribution phrases, and a Sources section at the end of key articles.
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.
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.
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.
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.
Show direct use, testing, implementation, or lived experience with concrete observations, examples, screenshots, and lessons learned.
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.