Moderate AI visibility with 34 of 53 criteria passing. Biggest gap: llms.txt file.
Verdict
Below-average AEO readiness at 60/100 - multiple areas need attention. Key strengths include Content Freshness Signals, RSS/Atom Feed, and Table & List Extractability. Priority gaps: llms.txt File, Content Licensing & AI Permissions, and Speakable Schema.
How to Improve
3 sampled page(s) carry a noindex directive
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.
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.
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.
Optimize compression, cache headers, redirect chains, and HTML payload size for faster AI crawler access.
Trim oversized HTML, excessive DOM nodes, and large inline payloads that slow AI crawlers.
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.
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.
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.
Create a dedicated FAQ page with FAQPage schema markup. Cover common questions about your products, services, and industry to become a direct answer source for AI engines.
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.
Add Organization schema with consistent name, address, phone (NAP). Include sameAs links to social profiles and authoritative directories to strengthen entity recognition.
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.
Establish a regular content publishing cadence with dated entries in your sitemap. Consistent publishing signals to AI engines that your site is an active, current information source.