Weak AI visibility with 22 of 53 criteria passing. Biggest gap: llms.txt file.
Verdict
Critical AEO gaps at 45/100 - yart.com.au is largely invisible to AI engines. Key strengths include Content Cannibalization, Duplicate Content Blocks, and Cross-Page Duplicate Content. Priority gaps: llms.txt File, Schema.org Structured Data, and Comprehensive FAQ Section.
How to Improve
Generate a comprehensive sitemap with lastmod dates for all important pages.
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.
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.
48/73 images lack explicit width/height - the most common cause of layout shift (CLS)
Ensure clean, well-structured HTML with proper meta tags, HTTPS, and parseable content for AI crawlers.
Optimize compression, cache headers, redirect chains, and HTML payload size for faster AI crawler access.
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.
Write concise, standalone answer paragraphs (2-3 sentences) immediately after question headings. These "snippet-ready" paragraphs are ideal for AI engine citations.
Ensure every question-format heading (H2/H3) is followed by a direct answer paragraph. This pattern is ideal for AI engine snippet extraction.
Add question-based headings (H2/H3) throughout your content. Use "What is...", "How does...", "Why should..." patterns that match how users query AI assistants.
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 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.
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 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 specific numbers, percentages, statistics, and data points throughout your content. Fact-dense content gives AI engines concrete data to cite rather than vague claims.
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.