Moderate AI visibility with 30 of 53 criteria passing. Biggest gap: llms.txt file.
Verdict
Below-average AEO readiness at 52/100 - multiple areas need attention. Key strengths include Fact & Data Density, Duplicate Content Blocks, and Cross-Page Duplicate Content. Priority gaps: llms.txt File, Sitemap Completeness, and RSS/Atom Feed. HTTPS is not enabled, which caps several criteria scores and reduces AI crawler trust.
How to Improve
Generate a comprehensive sitemap with lastmod dates for all important pages.
Ensure clean, well-structured HTML with proper meta tags, HTTPS, and parseable content for AI crawlers.
1 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.
Add rel="canonical" tags to all pages to prevent duplicate content confusion.
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.
Trim oversized HTML, excessive DOM nodes, and large inline payloads that slow AI crawlers.
2273/2293 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 allAdd inline citations to external sources, "According to [Source]..." attribution phrases, and a Sources section at the end of key articles.
Ensure blog content consistently covers your core expertise areas rather than scattering across unrelated topics. AI engines build authority models - a site about "Medicare coverage" that also publishes about humidifiers and groceries dilutes its topical authority.
Add question-based headings (H2/H3) throughout your content. Use "What is...", "How does...", "Why should..." patterns that match how users query AI assistants.
Add Organization schema with consistent name, address, phone (NAP). Include sameAs links to social profiles and authoritative directories to strengthen entity recognition.
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.
Ensure every question-format heading (H2/H3) is followed by a direct answer paragraph. This pattern is ideal for AI engine snippet extraction.
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.
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.
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.