Moderate AI visibility with 38 of 53 criteria passing. Biggest gap: content licensing & ai permissions.
Verdict
Moderate AEO readiness at 62/100 with significant gaps to address. Key strengths include llms.txt File, Schema.org Structured Data, and Q&A Content Format. Priority gaps: Content Licensing & AI Permissions, Speakable Schema, and Owned Data Density.
How to Improve
Update robots.txt to explicitly allow AI crawlers and include sitemap directive.
Trim oversized HTML, excessive DOM nodes, and large inline payloads that slow AI crawlers.
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.
Minimize blocking scripts and stylesheets in <head> to improve content availability for AI crawlers.
169/169 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.
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.
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.
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 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.
Rewrite multi-clause sentences into single-claim statements under 20 words. Pages with Flesch-Kincaid grade 16 outperform grade 19 in citation rates.
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.
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.