Crawler and robots access
Evaluates robots.txt for AI search, AI training, site-owner-requested, classic search, and common crawler user agents at the exact submitted path.
Technical AEO readiness
AEO Checker
Audit a page before publishing or revising answer-focused content. Find robots and indexing restrictions, inspect the initial HTML, and turn the evidence into a technical fix list. The score describes this checklist, not an answer engine’s ranking system.
Put the report to work
From a scan to a page update
Use this sequence for one page, then repeat it for another page type.
- Set the page’s job. Write the question the page should answer and the intended reader. Review the actual answer, supporting evidence, author or maintenance information, and date yourself; the scanner only sees technical signals.
- Fix access before formatting. Confirm a successful HTML response, intended robots policy, and indexability. If a noindex or restricted path is deliberate, keep it and choose a public page for search acquisition.
- Check what arrives without JavaScript. Compare the reported title, H1, canonical, and readable text with the page you expect. A short text count is a review prompt, not a word-count ranking rule.
- Review existing markup. Correct malformed JSON-LD, then use a dedicated schema validator for vocabulary and properties. Published structured data should match visible content. Missing JSON-LD or llms.txt alone is not a failure here.
- Retest the same URL. Copy the before/after reports, confirm the changed evidence, and use Search Console URL Inspection for Google indexing. Move to the visibility workflow for actual answer inclusion.
Google’s AI search features need no special AI text file or special schema. Its normal search requirements still apply. See Google’s guidance on AI features and our scope and scoring explanation.
Included checks
What you can check
Use the findings to decide which page or discovery-file changes to make first.
Indexability and metadata
Checks HTTP status, redirects, meta robots, X-Robots-Tag, canonical URL, title, H1, and readable static HTML.
Published markup and discovery
Parses JSON-LD syntax and document shape, discovers robots.txt sitemap declarations, and estimates readable HTML text. Optional llms files and absent JSON-LD do not reduce the score.
Methodology
How to read your report
Review the observed signals and check details before changing your site.
View check and scoring details
Readiness-only scoring
The checklist average is 100 for pass, 55 for warn, 35 for unknown, and 0 for fail, excluding unscored checks. It is a prioritization aid, not a model of Google or other platforms’ eligibility.
Evidence-backed issues
Every recommendation is tied to a visible status, header, meta tag, robots.txt rule, missing file, or extracted content signal.
Bounded public scan
The scanner checks public URLs only and limits long, oversized, or repeated requests so the report stays focused.
Related tools
Choose your next check
Check a specific bot policy or explore another part of your page’s search readiness.
AI Crawler CheckerRun the full crawler access scan for robots.txt, AI bots, headers, page signals, sitemap, and llms.txt.llms.txt CheckerValidate AI-readable discovery files and see how they align with sitemap and crawler policy.AEO CheckerCheck technical Answer Engine Optimization readiness from public page and discovery signals.AI Search Visibility CheckerReview whether a URL has the technical foundations AI search systems need before any ranking or prompt testing.MethodologyUnderstand the scoring model, limitations, bot list, and public-scan boundary.
Scope of the report
Scope of the report
- 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
Common questions
Short answers for searchers, site owners, and technical SEO teams comparing AI readiness tools.
What is an AEO checker?
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.
What does the technical AEO scan include?
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.
Does a passing AEO score mean my site will appear in ChatGPT or AI Overviews?
No. Passing only describes the checks completed here. It does not verify Google indexing, actual bot access through your firewall, content quality, or selection for an AI answer.
Is this useful for agencies?
Yes for a first technical proof report. It highlights clear technical fixes before a team moves into deeper visibility measurement.