Changes since selected scan Not comparable because methodology information is unavailable
Result summary
Readiness profiles
Methodology 2026-08-29Measured stable-core coverage
64/100
Methodology grade
C
40 core checkpoints assessed
21
Passed
8
Partial
11
Failed
9
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"
Partial
AI crawler directives
+3 overall pts
Mixed AI crawler policies. Disallowed: GPTBot, ClaudeBot, Amazonbot, PerplexityBot, Applebot-Extended. Not mentioned (8): Google-Extended, ChatGPT-User, Claude-User, Bytespider, CCBot, meta-externalagent, Claude-SearchBot, OAI-SearchBot.
AI crawler directives
MEDIUMMajor AI systems use dedicated crawlers (GPTBot, ClaudeBot, Amazonbot). Explicit directives signal whether you want your content included in AI training and search results.
5 AI crawlers are blocked. Consider allowing them to improve AI discoverability.
# Add to your /robots.txt - explicit Allow for AI crawlers
User-agent: GPTBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: Google-Extended
Allow: /
User-agent: Amazonbot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: PerplexityBot
Allow: /Detailed results
Agent Protocols
Weight 15%
Not assessed
No score-impacting checkpoints
5 bonus opportunities and 3 informational findings; do not affect the core score
Core score
0/100
No score-impacting checkpoints
5 bonus opportunities and 3 informational findings; do not affect the core score
AI Content Discovery
Weight 30%
Needs attention
1 failed, 2 partial score-impacting checkpoints
6 bonus opportunities; do not affect the core score
Core score
78/100
1 failed, 2 partial score-impacting checkpoints
6 bonus opportunities; do not affect the core score
Security & Trust
Weight 15%
Needs attention
6 failed score-impacting checkpoints
1 bonus opportunity; does not affect the core score
Core score
26/100
6 failed score-impacting checkpoints
1 bonus opportunity; does not affect the core score
Content & Semantics
Weight 20%
Needs attention
2 failed, 5 partial score-impacting checkpoints
Core score
73/100
2 failed, 5 partial score-impacting checkpoints
AI Search Signals
Weight 20%
Needs attention
2 failed, 1 partial score-impacting checkpoints
Core score
61/100
2 failed, 1 partial score-impacting checkpoints
AI visitor test
We let an AI try common visitor tasks to show what works and where it gets stuck.
Can an AI understand this website?
UnavailableThis check is temporarily unavailable.
Can an AI find a useful action to take?
UnavailableThis check is temporarily unavailable.
AI Training Exposure
Supplemental
Does not affect the readiness score
Does not affect the readiness score
1 of 3 AI training protection mechanisms active.
Could not determine the latest Common Crawl index.
4 of 8 training crawlers blocked: Amazonbot, Applebot-Extended, ClaudeBot, GPTBot. Still allowed: Bytespider, CCBot, Google-Extended, meta-externalagent.
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.
No ai.txt file found. ai.txt lets you declare AI usage preferences for your content.
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