Changes since selected scan Not comparable because detailed evidence is unavailable
Result summary
Readiness profiles
Methodology 2026-08-29Measured stable-core coverage
62/100
Methodology grade
C
37 core checkpoints assessed
19
Passed
3
Partial
15
Failed
12
Skipped
Strongest category
AI Content Discovery
Weakest category
Security & Trust
Action plan
Priority actions
Highest-impact implementation details
3 prioritized actions
Prioritized by exact impact on the overall stable-core score.
Failed
High-value schema types
+5 overall pts
No high-value schema types found. We check for 17 recognized types including Article, Product, SoftwareApplication, FAQPage, LocalBusiness, VideoObject, and more.
High-value schema types
HIGHCertain schema types (Article, Product, FAQPage, etc.) trigger rich results in Google and Bing and give agents typed, unambiguous entities to extract instead of inferring from prose. Their effect on AI-search citations is indirect, via the search indexes that feed products like ChatGPT and Perplexity.
Add JSON-LD markup for content-appropriate types like Article, Product, SoftwareApplication, FAQPage, LocalBusiness, Service, Event, or VideoObject so agents and search engines can identify your content type and extract structured facts reliably.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
"name": "Your App Name",
"operatingSystem": "Web",
"applicationCategory": "BusinessApplication",
"offers": {
"@type": "Offer",
"price": "0",
"priceCurrency": "USD"
}
}
</script>
Failed
HSTS header
+4 overall pts
Strict-Transport-Security header is not set. Note: sites on the HSTS preload list may not send this header but are still protected via browser preloading.
HSTS header
HIGHHSTS prevents protocol downgrade attacks by telling browsers to always use HTTPS. AI agents that follow redirects benefit from HSTS as it eliminates insecure initial connections.
Add the Strict-Transport-Security header with max-age=31536000 (1 year) and includeSubDomains. If your site is on the HSTS preload list (hstspreload.org), the header is still recommended for first-visit protection.
# Nginx
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
# Apache (.htaccess)
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
Failed
Heading hierarchy
+3 overall pts
No <h1> heading found. 34 other headings present.
Heading hierarchy
HIGHAI agents use headings to build a content outline and determine topic hierarchy. A clear h1→h2→h3 structure helps AI systems extract and summarize your content accurately.
Add a clear <h1> heading and use sequential heading levels (h1 -> h2 -> h3). Proper heading hierarchy helps AI agents understand page structure and content importance. See developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements for heading element documentation.
<h1>Page Title - One Per Page</h1>
<h2>Main Section</h2>
<h3>Subsection</h3>
<h3>Subsection</h3>
<h2>Another Section</h2>
<h3>Subsection</h3>
Detailed results
Agent Protocols
Weight 15%
Not assessed
No score-impacting checkpoints
5 bonus opportunities and 2 informational findings; do not affect the core score
Core score
0/100
No score-impacting checkpoints
5 bonus opportunities and 2 informational findings; do not affect the core score
AI Content Discovery
Weight 30%
Needs attention
2 failed, 1 partial score-impacting checkpoints
6 bonus opportunities; do not affect the core score
Core score
75/100
2 failed, 1 partial score-impacting checkpoints
6 bonus opportunities; do not affect the core score
Security & Trust
Weight 15%
Needs attention
7 failed, 1 partial score-impacting checkpoints
1 bonus opportunity; does not affect the core score
Core score
18/100
7 failed, 1 partial score-impacting checkpoints
1 bonus opportunity; does not affect the core score
Content & Semantics
Weight 20%
Needs attention
4 failed, 1 partial score-impacting checkpoints
Core score
68/100
4 failed, 1 partial score-impacting checkpoints
AI Search Signals
Weight 20%
Needs attention
2 failed score-impacting checkpoints
Core score
68/100
2 failed score-impacting checkpoints
AI Training Exposure
Supplemental
Does not affect the readiness score
Does not affect the readiness score
No AI training protections detected. Your content may be freely used for AI model training.
Could not determine the latest Common Crawl index.
No training crawlers are blocked in robots.txt. All known AI training bots can access your content.
No TDMRep file found at /.well-known/tdmrep.json. The TDM Reservation Protocol (W3C) lets you declare whether you reserve text and data mining rights. See w3.org/community/reports/tdmrep/CG-FINAL-tdmrep-20240510 for the specification.
ai.txt returned HTML instead of plain text (Content-Type: text/html; charset=UTF-8). The file should be served as text/plain.
No Web Bot Auth signature key directory found. Bots cannot prove their identity to origins via signed HTTP requests.
Scan and fix from your editor
Install our MCP server to scan any website from your terminal. Pair it with AI agent skills to fix failing checks automatically.
- Scan any website directly from your terminal
- Fix failing checks with AI agent skills
- Re-scan to verify improvements
claude mcp add isagentready-mcp -- npx -y isagentready-mcp
/plugin marketplace add bartwaardenburg/isagentready-skills
Request a detailed report Optional follow-up with a personalized PDF report
Get your detailed report
Receive a personalized report with actionable insights for improving your website's AI agent readiness.
- Detailed score breakdown per category
- Prioritized improvement recommendations
- Step-by-step implementation guide