Crawler and robots access
Evaluates robots.txt for AI search, AI training, classic search, and common crawler user agents at the exact submitted path.
Technical AEO readiness
Audit whether a public page is technically ready for Answer Engine Optimization. The report focuses on crawlability, indexability, structured data, page clarity, AI-readable discovery files, and limitations.
Real checks
These pages use the same live scanner as the homepage. The difference is the focused report shown after the scan, not a separate static keyword page.
Evaluates robots.txt for AI search, AI training, classic search, and common crawler user agents at the exact submitted path.
Checks HTTP status, redirects, meta robots, X-Robots-Tag, canonical URL, title, H1, and readable static HTML.
Checks sitemap.xml, llms.txt, llms-full.txt, JSON-LD structured data, and whether the page exposes enough readable content.
Methodology
The scanner is intentionally conservative: public URLs only, no login bypassing, bounded fetches, no saved reports by default, and no promise of AI ranking or citation.
The AEO score is based on public technical signals, not live model prompts or AI answer rankings.
Every recommendation is tied to a visible status, header, meta tag, robots.txt rule, missing file, or extracted content signal.
The scanner uses timeouts, response-size limits, redirect limits, private-network blocking, and lightweight rate limiting.
Tool matrix
Use the matrix to move from a focused issue to the broader AI crawler and readiness report.
Limitations
Clear boundaries make the report more useful: it diagnoses technical readiness, not guaranteed visibility.
This is not an AI ranking guarantee or a citation tracker.
The score does not measure brand authority, backlinks, topical expertise, or live AI answer inclusion.
The scanner does not log in, bypass WAF rules, fetch private URLs, or crawl an entire website.
FAQ
Short answers for searchers, site owners, and technical SEO teams comparing AI readiness tools.
An AEO checker audits technical signals that can help answer engines discover, understand, and cite a page. This tool focuses on public readiness signals rather than speculative AI ranking claims.
It checks robots.txt, AI bot access, HTTP status, redirects, canonical URL, meta robots, X-Robots-Tag, title, H1, readable HTML, JSON-LD, sitemap.xml, llms.txt, and llms-full.txt.
No. Passing means no major technical readiness blockers were found. AI visibility also depends on authority, relevance, freshness, user intent, and each AI platform's selection systems.
Yes for a first technical proof report. It highlights implementation fixes that a client or developer can act on before moving into paid proof, prompt tracking, or competitor analysis.