Weak AI visibility with 17 of 53 criteria passing. Biggest gap: llms.txt file.
Verdict
Critical AEO gaps at 43/100 - raketracker.at is largely invisible to AI engines. Key strengths include Topic Coherence, Duplicate Content Blocks, and Page Speed: Load Blockers. Priority gaps: llms.txt File, Schema.org Structured Data, and Semantic HTML5 & Accessibility. 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.
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.
No viewport meta tag on the homepage - pages will not render responsively on mobile devices
Optimize compression, cache headers, redirect chains, and HTML payload size for faster AI crawler access.
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.
Expand 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.
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.
Add inline citations to external sources, "According to [Source]..." attribution phrases, and a Sources section at the end of key articles.
Add question-based headings (H2/H3) throughout your content. Use "What is...", "How does...", "Why should..." patterns that match how users query AI assistants.
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.
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.
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.
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.