klantenvertellen.nl

Item: klantenvertellen.nl
Rating: 63

Compare

Scan history

Scanned 2026-08-29 12:08 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-08-29 12:08 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 2026-08-29

Measured stable-core coverage

63/100

Methodology grade

40 core checkpoints assessed

Passed

Partial

Failed

Skipped

Strongest category

Content & Semantics

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.

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

HIGH

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

JSON-LD html

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

Sources

XML Sitemap +5 overall pts

Sitemap found at klantenvertellen.nl/sitemap_index.xml, but bounded integrity checks failed: invalid_xml.

XML Sitemap

HIGH

Sitemaps help AI crawlers discover all your pages efficiently. Without one, crawlers may miss important content or waste time discovering your site structure.

Keep sitemap URLs same-origin, use valid lastmod values, and ensure sampled pages return successful responses.

sitemap.xml html

<!-- /sitemap.xml -->
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://klantenvertellen.nl/</loc>
    <lastmod>2025-01-15</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://klantenvertellen.nl/about</loc>
    <lastmod>2025-01-10</lastmod>
  </url>
</urlset>

# Add to /robots.txt:
Sitemap: https://klantenvertellen.nl/sitemap.xml

Sources

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

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

Fix with AI Skills

$ /plugin marketplace add bartwaardenburg/isagentready-skills

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

WebMCP Declarative API: Failed

API Catalog (RFC 9727): Failed

Agent Skills index: Failed

x402 payments: Skipped

MPP (x-payment-info): Skipped

UCP (.well-known/ucp): Skipped

ACP (.well-known/acp.json): Skipped

AP2 (A2A payments capability): Skipped

OpenAPI actionability quality: Skipped

MCP server card quality: Skipped

Live OpenAPI verification: Skipped

Live MCP verification: Skipped

AI Catalog: Failed

API error responses: Skipped

API rate-limit headers: Skipped

Developer docs discoverability: Skipped

A2A Agent Card: Failed

MCP Discovery: Failed

OpenAPI / API documentation: Failed

agents.json: Failed

Declarative Form Quality: Skipped

Interactive Surface Coverage: Failed

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 73/100

robots.txt present: Passed

Content Signals (robots.txt): Failed

AGENTS.md agent guide: Failed

Agent content contracts: Failed

Soft-404 hygiene: Passed

DNS-AID agent records: Failed

AI crawler directives: Passed

XML Sitemap: Failed

llms.txt: Failed

Meta robots / X-Robots-Tag: Passed

Content freshness signals: Partial

Content negotiation (text/markdown): Failed

HTTP bot accessibility: Passed

Link response headers: Failed

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

HTTPS: Passed

Tool Definition Security: Skipped

Auto-submit Risk Assessment: Passed

OAuth Discovery: Failed

OAuth Protected Resource: Failed

Agent Auth Readiness: 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% Partial progress

1 partial score-impacting checkpoint

Core score 97/100

Server-side rendered content: Passed

Form field autocomplete: Passed

Keyboard navigability: Passed

Document title: Passed

Button accessible names: Passed

aria-hidden misuse: Passed

Dynamic widget state: Passed

Page token budget: Passed

Heading hierarchy: Passed

Semantic HTML elements: Passed

Accessible landmarks & ARIA: Passed

Image alt text: Passed

Language attribute: Passed

Descriptive link texts: Passed

Question-based headings: Partial

Form label coverage: Passed

AI Search Signals Weight 20% Needs attention

4 failed score-impacting checkpoints

Core score 47/100

JSON-LD present: Passed

Organization / WebSite schema: Passed

High-value schema types: Failed

Entity linking (@id): Failed

BreadcrumbList markup: Skipped

Schema validation: Passed

FAQPage schema: Skipped

Author attribution: Failed

Trust anchor pages: Failed

AI visitor test

We let an AI try common visitor tasks to show what works and where it gets stuck.

Experimental, does not affect the score

Can an AI understand this website?

Unavailable

This check is temporarily unavailable.

Can an AI find a useful action to take?

Unavailable

This check is temporarily unavailable.

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