klantenvertellen.nl

Item: klantenvertellen.nl
Rating: 55

Compare

Scan history

Scanned 2026-05-18 10:52 UTC

2026-08-29 12:08 UTC 63/100 Compare

2026-05-18 10:52 UTC 55/100 Compare

2026-03-03 13:14 UTC 64/100 Compare

2026-03-01 15:27 UTC 69/100 Compare

SCAN HISTORY Scanned 2026-05-18 10:52 UTC

2026-08-29 12:08 UTC 63/100 Compare

2026-05-18 10:52 UTC 55/100 Compare

2026-03-03 13:14 UTC 64/100 Compare

2026-03-01 15:27 UTC 69/100 Compare

Changes since selected scan Not comparable because methodology information is unavailable

Result summary

Readiness profiles

Methodology legacy

Measured coverage

55/100

Methodology grade

50 checkpoints assessed

Passed

Partial

Failed

Skipped

Strongest category

AI Search Signals

Weakest category

Agent Protocols

Action plan

Priority actions Highest-impact implementation details

3 prioritized actions

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

llms.txt +3 overall pts

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

llms.txt

HIGH

llms.txt provides a curated entry point for AI agents — coding assistants, browsing agents, and task automation tools that fetch specific pages to complete tasks. Unlike crawlers that scrape everything, agents benefit from a structured overview of your most important pages.

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

llms.txt plain

# /llms.txt
# klantenvertellen.nl

> klantenvertellen.nl - your site description here.

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

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

Sources

HSTS header +3 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

HIGH

HSTS 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.

Server config plain

# 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"

Sources

WebMCP Declarative API +3 overall pts

No WebMCP signals found.

WebMCP Declarative API

HIGH

WebMCP is the W3C proposal for exposing website functionality directly to AI agents. Declarative tool annotations on forms let agents perform actions (search, purchase, book) without screen scraping.

Implement WebMCP to let AI agents interact with your site. Declarative: add tool-name and tool-description attributes to <form> elements. Imperative: use navigator.modelContext.provideContext() to register tools.

<form tool-name="search" tool-description="Search products by keyword">
  <input type="text" name="query" tool-param-description="Search query">
  <button type="submit">Search</button>
</form>

Sources

Fix with AI Skills

$ /plugin marketplace add bartwaardenburg/isagentready-skills

Detailed results

Agent Protocols Weight 15% Needs attention

9 failed checkpoints

0/100

WebMCP Declarative API: Failed

API Catalog (RFC 9727): Failed

Agent Skills index: Failed

WebMCP manifest: Failed

A2A Agent Card: Failed

MCP Discovery: Failed

OpenAPI / API documentation: Failed

agents.json: Failed

Interactive Surface Coverage: Failed

AI Content Discovery Weight 30% Needs attention

3 failed, 1 partial

70/100

robots.txt present: Passed

Content Signals (robots.txt): Failed

AI crawler directives: Passed

XML Sitemap: Passed

llms.txt: Failed

Meta robots / X-Robots-Tag: Passed

Content freshness signals: Passed

Content negotiation (text/markdown): Partial

HTTP bot accessibility: Passed

Link response headers: Failed

Security & Trust Weight 15% Needs attention

7 failed, 1 partial

26/100

HTTPS: Passed

Auto-submit Risk Assessment: Passed

OAuth Discovery: Failed

OAuth Protected Resource: Failed

HSTS header: Failed

Content-Security-Policy: Failed

X-Content-Type-Options: Failed

Frame protection: Failed

CORS configuration: Partial

Referrer-Policy: Failed

Content & Semantics Weight 20% Needs attention

2 failed, 3 partial

73/100

Server-side rendered content: Passed

Form field autocomplete: Failed

Keyboard navigability: Passed

Document title: Passed

Button accessible names: Passed

aria-hidden misuse: Passed

Heading hierarchy: Partial

Semantic HTML elements: Partial

Accessible landmarks & ARIA: Passed

Image alt text: Partial

Language attribute: Passed

Descriptive link texts: Passed

Question-based headings: Failed

Form label coverage: Passed

AI Search Signals Weight 20% Needs attention

2 failed checkpoints

79/100

JSON-LD present: Passed

Organization / WebSite schema: Passed

High-value schema types: Passed

Entity linking (@id): Passed

Schema validation: Passed

FAQPage schema: Failed

Author attribution: Failed

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. ai.txt lets you declare AI usage preferences for your content.

Web Bot Auth Not found

No Web Bot Auth signature key directory found. Bots cannot prove their identity to origins via signed HTTP requests.

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