Result summary
Measured coverage
29/100
Methodology grade
D
Methodology legacy
37 checkpoints assessed
- Find
- 3/8 passed
- Read
- 6/20 passed
- Act
- 1/9 passed
Readiness profiles Filter the detailed results by purpose
Select a profile to filter the detailed results.
Action plan
Priority actions Prioritized by exact impact on the overall stable-core score.
Failed
JSON-LD present
+5 overall pts
No valid JSON-LD blocks with schema.org @context found.
JSON-LD present
HIGHJSON-LD is the preferred format for structured data by Google and AI search engines. It tells AI systems exactly what your page is about using a standardized vocabulary.
Add at least one <script type="application/ld+json"> block with "@context": "schema.org" describing your organization or page content. Schema markup provides a 73% higher selection rate in Google AI Overviews.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Your Company",
"url": "https://aquahotplus.nl",
"logo": "https://aquahotplus.nl/logo.png"
}
</script>
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 are used by AI search engines like Perplexity and ChatGPT to generate citations and structured answers.
Add JSON-LD markup for content-appropriate types like Article, Product, SoftwareApplication, FAQPage, LocalBusiness, Service, Event, or VideoObject to improve visibility in AI-powered search results.
<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
Server-side rendered content
+4 overall pts
No meaningful visible text found in <body>. Page may require JavaScript to render.
Server-side rendered content
HIGHNeither AI crawlers nor AI agents execute JavaScript. They parse raw HTML to understand page content. Without server-side rendering, your content is invisible to both training crawlers and task-completing agents.
Implement server-side rendering (SSR) or static site generation (SSG) so AI agents can read your content without executing JavaScript. See web.dev/articles/rendering-on-the-web for a comparison of rendering strategies.
// Next.js - use getServerSideProps for SSR
export async function getServerSideProps() {
const data = await fetchData();
return { props: { data } };
}
// Or use generateStaticParams for SSG (App Router)
export async function generateStaticParams() {
return [{ slug: "about" }, { slug: "contact" }];
}Detailed results
Agent Protocols
Weight 15% · 8 failed checkpoints
0/100
Weight 15% · 8 failed checkpoints
AI Content Discovery
Weight 30% · 6 failed, 1 partial
41/100
Weight 30% · 6 failed, 1 partial
Security & Trust
Weight 15% · 1 failed checkpoint
93/100
Weight 15% · 1 failed checkpoint
Content & Semantics
Weight 20% · 6 failed checkpoints
11/100
Weight 20% · 6 failed checkpoints
AI Search Signals
Weight 20% · 5 failed checkpoints
0/100
Weight 20% · 5 failed checkpoints
Supplemental evidence AI visitor test and training exposure. The score does not change.
AI Training Exposure
Does not affect the readiness score
Supplemental
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.
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.
Next steps
Scan and fix from your editor. Install the MCP server to scan, and AI skills to fix.
claude mcp add isagentready-mcp -- npx -y isagentready-mcp
codex mcp add isagentready-mcp -- npx -y isagentready-mcp
gemini mcp add isagentready-mcp -- npx -y isagentready-mcp
docker run -i --rm ghcr.io/bartwaardenburg/isagentready-mcp
/plugin marketplace add bartwaardenburg/isagentready-skills
git clone https://github.com/bartwaardenburg/isagentready-skills.git ~/.cursor/skills/isagentready-skills
git clone https://github.com/bartwaardenburg/isagentready-skills.git ~/.agents/skills/isagentready-skills
git clone https://github.com/bartwaardenburg/isagentready-skills.git ~/.codeium/windsurf/skills/isagentready-skills
git clone https://github.com/bartwaardenburg/isagentready-skills.git ~/.agents/skills/isagentready-skills
gemini skills install https://github.com/bartwaardenburg/isagentready-skills.git
git clone https://github.com/bartwaardenburg/isagentready-skills.git ~/.config/agents/skills/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