Moderate AI visibility with 43 of 53 criteria passing. Biggest gap: rss/atom feed.
Verdict
Moderate AEO readiness at 65/100 with significant gaps to address. Key strengths include llms.txt File, Q&A Content Format, and robots.txt for AI Crawlers. Priority gaps: RSS/Atom Feed, Content Licensing & AI Permissions, and Speakable Schema.
How to Improve
robots.txt blocks Google-Extended - content is excluded from Google AI training and grounding
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.
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.
270/453 images lack explicit width/height - the most common cause of layout shift (CLS)
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 allEnsure 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.
Publish 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.
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.
Add inline citations to external sources, "According to [Source]..." attribution phrases, and a Sources section at the end of key articles.
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.
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 Organization schema with consistent name, address, phone (NAP). Include sameAs links to social profiles and authoritative directories to strengthen entity recognition.
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.
Show direct use, testing, implementation, or lived experience with concrete observations, examples, screenshots, and lessons learned.
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.