Answer engine optimization audit
See what AI crawlers can actually reach
AEOprobe checks crawler access and page understanding: documented search-crawler blocks, invalid schema, weak page structure, missing canonicals, sitemap issues and web-quality problems. It does not guarantee AI visibility or citations.
No signup required.
Direct answer
An answer engine optimization audit can test public technical eligibility: whether documented search crawlers are allowed, pages are indexable, structured data parses, and canonical signals are coherent. These checks are useful diagnostics, but no site-side audit can prove that an AI product will select or cite a page.
11 categories, scored and traceable
Each category gets its own score, and every score traces back to findings you can inspect. Findings outside these categories, such as llms.txt and agentic browsing checks, are reported without changing the score.
Crawler access
Documented AI crawlers tested against your live robots.txt, with search, user-fetch, and training roles kept separate.
Structured data
JSON-LD and schema.org markup parsed and checked for the fields machines expect. Valid markup aids interpretation; it does not guarantee citation.
Content structure
Heading hierarchy, answer-first copy, and extractable summaries. Heuristics for readability, not a prediction of selection.
AI readiness
Site-side heuristics for source context and extractable content, such as who publishes the page. Not a measurement of AI visibility.
Meta tags
Titles, descriptions, canonical links, and robots directives such as noindex that decide how each page is indexed and presented.
Technical SEO
Status codes, broken internal links, redirects, and validation errors that stop crawlers from reaching or reading a page.
Performance
Response times, compression, and delivery, as web-quality checks for visitors and crawlers.
Open Graph
Share-preview tags that give each page a consistent title, description, and image wherever it is shared.
Sitemap
Whether your sitemap exists, parses, and lists the canonical URLs crawlers should discover.
Accessibility
Semantic HTML, alt text, and language declarations that also make pages easier to parse.
Security
HTTPS enforcement and security headers, checked as web-quality fundamentals.
20 AI crawlers, by role
The audit tests 20 documented AI crawlers against your live robots.txt and groups them by what they do, because blocking a training crawler is not the same decision as blocking a search crawler.
AI search
OAI-SearchBot, Claude-SearchBot, PerplexityBot
Access can affect whether public pages are available to a vendor’s search product.
User fetch
ChatGPT-User, Claude-User, Perplexity-User
Fetches a page in response to a user action. Treated separately from unattended crawling.
Training
GPTBot, ClaudeBot, Google-Extended
Policies about model development, not ordinary web search indexing.
Findings with evidence
Every finding names the pages it affects and what the audit observed, ranked by severity, so you fix confirmed blockers first and can check the evidence yourself.
- critical
OAI-SearchBot is blocked by a blanket rule
robots.txt User-agent: * Disallow: /
- high
No JSON-LD on product pages
/pricing /features /integrations
After the free audit
Save a site in your account to run a site audit. Watch and Pro add a visual check. You can track to-dos and return to your saved findings.
Recheck a page after you publish a fix. The cost is shown before you confirm.
A free account shows 5 findings for each site. A paid plan shows them all. Free includes 25 credits a month. Watch includes 100 and Pro includes 500. See plans and credit packs for prices, limits and availability.
You can also use AEOprobe from Claude Code or Codex. After your agent reports a fix, the recheck runs by itself within your weekly credit limit.
Connect your coding agent
Set up Claude Code or CodexWhat a job costs
Page captures require an active Watch or Pro plan.
- Site audit20 credits
- Page capture1 credit
- Page recheck1 credit
When to use this audit
Run an AEO audit before buying AI visibility monitoring, before launching a content sprint, and after any robots.txt, schema, template, or canonical change. Monitoring can tell you whether your brand appears in AI answers; a technical audit checks public access, indexability, markup, and page-structure conditions without predicting selection.
The fastest workflow is to audit the site, fix confirmed crawler and indexing blockers first, improve useful source content, then use a monitoring platform if you need to measure actual appearances in AI answers.
Related AEO resources
AI crawler access checker
Paste robots.txt and see which AI crawlers are allowed, blocked, or missing from your rules.
Read moreJSON-LD schema validator
Validate JSON-LD syntax and selected fields for common schema.org types.
Read moreBest AEO tools 2026
Compare diagnostic audit tools with monitoring and enterprise AEO platforms.
Read moreCommon questions
Is the audit really free?
Yes. The audit runs on a URL you enter, needs no signup, and returns a scored report with findings and evidence.
Does the audit tell me whether AI products cite my site?
No. AEOprobe checks public technical conditions such as crawler access, indexability, markup, and page structure. AI answer checks, on Watch and Pro, sample a few AI answers separately, and no audit or check can guarantee that an AI product will select or cite a page.
What does a finding include?
Each finding has a severity, the pages or paths it affects, and what the audit observed, so you can verify it yourself before changing anything.
Where can I follow the audit?
You can watch progress on the audit page and share the finished report.
Check what AI crawlers can actually reach
Run a free audit to find public crawler, indexing, markup, and page-structure issues.
Run free audit