Moderate AI visibility with 38 of 53 criteria passing. Biggest gap: llms.txt file.
Verdict
Below-average AEO readiness at 60/100 - multiple areas need attention. Key strengths include Clean, Crawlable HTML, Internal Linking Structure, and Fact & Data Density. Priority gaps: llms.txt File, RSS/Atom Feed, and Content Licensing & AI Permissions.
How to Improve
2 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.
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.
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.
Top Opportunities10
View allWrite concise, standalone answer paragraphs (2-3 sentences) immediately after question headings. These "snippet-ready" paragraphs are ideal for AI engine citations.
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.
Show direct use, testing, implementation, or lived experience with concrete observations, examples, screenshots, and lessons learned.
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.
Add question-based headings (H2/H3) throughout your content. Use "What is...", "How does...", "Why should..." patterns that match how users query AI assistants.
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.
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.