1. Entity Resolution (@id)
A stable @id on your Organization schema can help connect markup about the same entity. Check that the identity and factual claims match what visitors can see; markup alone does not establish authority.
ENGINEERING AS MARKETING · FREE B2B TOOL
AEO & Agent Readiness Analyzer.
Inspect structured data and crawler access signals on your website. Review Schema.org entity markup, robots.txt directives for search crawlers versus training crawlers, optional /llms.txt discovery, and direct-answer structure. These checks do not predict search rankings or AI citations.
QUICK PRESETS
Cendar Agent Readiness Score
100/ 100Agent-Ready
Audit evaluated across 5 deterministic AEO dimensions: Schema Entity Graph, AI Search Crawler Directives, LLMs.txt, Extraction Density, and Visible Schema Fidelity.
Detailed AEO Audit Breakdown
✓
Entity GraphPASS (100/100)
Canonical Entity Resolution (@id Graph)
Stable @id detected. The entity graph explicitly disambiguates the organization from isolated page nodes.
Actionable Fix: Preserve the single @id root across all brand pages so AI engines attribute all content to one entity.
✓
AI CrawlersPASS (100/100)
AI Crawler Accessibility
Answer engine bots have explicit or inherited permission to crawl public indexable documents.
Actionable Fix: Keep crawler directives audited whenever updating edge or firewall security configurations.
✓
LLMs.txtPASS (100/100)
Machine-Readable Context Layer (/llms.txt)
The site provides a standardized /llms.txt directory structuring core documentation and service offerings.
Actionable Fix: Derive /llms.txt automatically from sitemap and CMS sources at build time to prevent stale claims.
✓
Content DensityPASS (100/100)
Clean Document Structure & Direct Answers
Valid lang attribute, single clean H1 landmark, and concise meta description with > 30 characters.
Actionable Fix: Ensure the first 200 characters under the H1 directly answer the core user query without marketing fluff.
✓
Schema IntegrityPASS (100/100)
Visible Content and Schema Fidelity
No unverified ghost schema or hidden review assertions detected in JSON-LD.
Actionable Fix: Audit schema against visible text whenever copywriters update product features or pricing.
THE FOUR PILLARS
What makes a website ready for AI engines?
Clear, accessible source pages help people and retrieval systems interpret your content. Search indexing, answer selection, and model training are separate processes; a page-level check cannot verify their outcomes.
2. Search vs. Training Crawlers
Review robots.txt and edge rules for the specific search crawlers you want to reach. Training crawlers serve a different purpose; permitting either type does not guarantee indexing or inclusion in AI answers.
3. Optional Machine-Readable Context
An /llms.txt file can provide a concise map to useful pages for clients that choose to read it. It is optional, not a proven ranking factor or a guarantee of AI citations.
4. Schema-to-DOM Fidelity
Keep factual claims in JSON-LD, such as reviews or FAQ answers, consistent with visible page content. Validate markup and source pages separately; passing a markup check does not verify search eligibility.