Moderate AI visibility with 43 of 53 criteria passing. Biggest gap: llms.txt file.
Verdict
Moderate AEO readiness at 67/100 with significant gaps to address. Key strengths include Q&A Content Format, Clean, Crawlable HTML, and Comprehensive FAQ Section. Priority gaps: llms.txt File, Content Licensing & AI Permissions, and Speakable Schema.
How to Improve
robots.txt blocks Google-Extended - content is excluded from Google AI training and grounding
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.
Generate a comprehensive sitemap with lastmod dates for all important pages.
Optimize compression, cache headers, redirect chains, and HTML payload size for faster AI crawler access.
Minimize blocking scripts and stylesheets in <head> to improve content availability for AI crawlers.
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.
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.
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.
Show direct use, testing, implementation, or lived experience with concrete observations, examples, screenshots, and lessons learned.
Add Person schema for content authors with credentials, expertise, and sameAs links. Expert attribution strengthens E-E-A-T signals that AI engines use to evaluate source credibility.
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.
Add named attribution and outbound links to authoritative sources for factual claims in content pages. Claims with visible sources are what AI engines trust and quote; unsourced claims read as opinion.
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.
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.
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.