Moderate AI visibility with 37 of 53 criteria passing. Biggest gap: content licensing & ai permissions.
Verdict
Below-average AEO readiness at 59/100 - multiple areas need attention. Key strengths include llms.txt File, Internal Linking Structure, and Sitemap Completeness. Priority gaps: Content Licensing & AI Permissions, Speakable Schema, and Query-Answer Alignment.
How to Improve
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.
Trim oversized HTML, excessive DOM nodes, and large inline payloads that slow 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.
Optimize compression, cache headers, redirect chains, and HTML payload size for faster AI crawler access.
317/1057 images lack explicit width/height
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.
Ensure every question-format heading (H2/H3) is followed by a direct answer paragraph. This pattern is ideal for AI engine snippet extraction.
Sections within pages contain identical or near-identical text. LLMs may flag this as low-quality or thin content, reducing citation authority. Rewrite duplicate blocks with unique angles.
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.
The same paragraphs appear on multiple pages. AI engines may only index one version and ignore the rest. Rewrite shared content so each page offers a unique perspective.
Add question-based headings (H2/H3) throughout your content. Use "What is...", "How does...", "Why should..." patterns that match how users query AI assistants.
Show direct use, testing, implementation, or lived experience with concrete observations, examples, screenshots, and lessons learned.
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.