debelegger.nl

Item: debelegger.nl
Rating: 41

Compare

Scan history

Scanned 2026-03-01 15:30 UTC

2026-08-29 15:45 UTC 31/100 Compare

2026-05-18 10:54 UTC 56/100 Compare

2026-03-03 13:45 UTC 60/100 Compare

2026-03-01 15:30 UTC 41/100 Compare

SCAN HISTORY Scanned 2026-03-01 15:30 UTC

2026-08-29 15:45 UTC 31/100 Compare

2026-05-18 10:54 UTC 56/100 Compare

2026-03-03 13:45 UTC 60/100 Compare

2026-03-01 15:30 UTC 41/100 Compare

Result summary

Readiness profiles

Methodology legacy

Measured coverage

41/100

Methodology grade

11 checkpoints assessed

Passed

Partial

Failed

Skipped

Strongest category

AI Content Discovery

Weakest category

AI Search Signals

Action plan

Priority actions Highest-impact implementation details

3 prioritized actions

Prioritized by exact impact on the overall stable-core score.

llms.txt +10 overall pts

No valid llms.txt found at /llms.txt.

llms.txt

HIGH

llms.txt is a new standard that provides LLMs with a structured overview of your site — key pages, documentation links, and context — in a format optimized for AI consumption.

Create an /llms.txt file with a markdown heading and relevant URLs to help LLMs understand your site.

llms.txt plain

# /llms.txt
# debelegger.nl

> debelegger.nl — your site description here.

## Docs
- [Getting Started](https://debelegger.nl/docs/getting-started)
- [API Reference](https://debelegger.nl/docs/api)

## Optional
- [Blog](https://debelegger.nl/blog)
- [Changelog](https://debelegger.nl/changelog)

Sources

Entity linking (@id) +5 overall pts

No JSON-LD entities use @id for entity linking.

Entity linking (@id)

HIGH

Entity linking via @id creates a connected graph of your content. AI systems can follow these references to build deeper understanding of relationships between your pages, organization, and content.

Add @id properties to your JSON-LD entities (e.g. "@id": "debelegger.nl/#organization") to enable cross-referencing between entities.

JSON-LD html

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://debelegger.nl/#organization",
      "name": "Your Company",
      "url": "https://debelegger.nl"
    },
    {
      "@type": "WebSite",
      "@id": "https://debelegger.nl/#website",
      "name": "Your Site",
      "url": "https://debelegger.nl",
      "publisher": { "@id": "https://debelegger.nl/#organization" }
    }
  ]
}
</script>

Sources

Schema validation +3 overall pts

Minor validation issues: WebSite missing required properties: name.

Schema validation

MEDIUM

Invalid structured data is ignored by search engines and AI systems. Validation errors mean your markup effort provides zero benefit — properly structured data is essential.

Fix the structural issues in your JSON-LD to ensure maximum compatibility with AI systems.

Sources

Fix with AI Skills

$ /plugin marketplace add bartwaardenburg/isagentready-skills

Detailed results

Agent Protocols Weight 15% Not assessed

No applicable checkpoints

0/100

AI Content Discovery Weight 30% Needs attention

1 failed checkpoint

83/100

robots.txt present: Passed

AI crawler directives: Passed

XML Sitemap: Passed

llms.txt: Failed

Meta robots / X-Robots-Tag: Passed

HTTP bot accessibility: Passed

Security & Trust Weight 15% Not assessed

No applicable checkpoints

0/100

Content & Semantics Weight 20% Not assessed

No applicable checkpoints

0/100

AI Search Signals Weight 20% Needs attention

1 failed, 1 partial

80/100

JSON-LD present: Passed

Organization / WebSite schema: Passed

High-value schema types: Passed

Entity linking (@id): Failed

Schema validation: Partial

AI Training Exposure Supplemental

Does not affect the readiness score

No AI training protections detected. Your content may be freely used for AI model training.

Common Crawl presence Unknown

Could not determine the latest Common Crawl index.

Training crawler blocking Not found

No training crawlers are blocked in robots.txt. All known AI training bots can access your content.

TDMRep declaration Not found

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 policy Not found

No ai.txt file found. This emerging standard lets you declare AI usage preferences for your content.

Developer Tools

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

SCAN

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

FIX

/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

MCP Server AI Skills

Request a detailed report Optional follow-up with a personalized PDF report

Free 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