Skip to content
N

natuurhuisje.nl

Scan history Scanned 2026-08-29 16:18 UTC
Changes since selected scan Not comparable because methodology information is unavailable

Result summary

Measured stable-core coverage

52/100

Methodology grade

C

Methodology 2026-08-29

40 core checkpoints assessed

Find
3/7 passed
Read
14/24 passed
Act
2/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 OpenAPI / API documentation +15 overall pts

No OpenAPI or Swagger documentation found.

OpenAPI / API documentation
HIGH

OpenAPI specifications let AI agents understand and call your API programmatically. AI coding assistants and agent frameworks use OpenAPI to generate correct API calls automatically.

Create an OpenAPI 3.x specification and serve it at /openapi.json or /.well-known/openapi to enable AI agents to discover and use your API.

openapi.json json
{
  "openapi": "3.1.0",
  "info": {
    "title": "My API",
    "version": "1.0.0"
  },
  "paths": {
    "/api/search": {
      "get": {
        "summary": "Search items",
        "parameters": [
          {"name": "q", "in": "query", "schema": {"type": "string"}}
        ]
      }
    }
  }
}
Failed XML Sitemap +4 overall pts

No valid XML sitemap found. Checked: natuurhuisje.nl/sitemap.xml, natuurhuisje.nl/sitemap_index.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.

Create an XML sitemap and reference it in robots.txt with a Sitemap: directive.

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://natuurhuisje.nl/</loc>
    <lastmod>2025-01-15</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://natuurhuisje.nl/about</loc>
    <lastmod>2025-01-10</lastmod>
  </url>
</urlset>

# Add to /robots.txt:
Sitemap: https://natuurhuisje.nl/sitemap.xml
Failed High-value schema types +4 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>
Failed Content freshness signals +3 overall pts

No content freshness signals found. AI systems cannot determine when this content was last updated.

Content freshness signals
HIGH

AI systems prefer recent content, and several engines surface newer pages more often. Clear date signals (dateModified, article:modified_time) help AI determine your content's recency.

Add content date signals so AI systems can assess freshness. Use dateModified in JSON-LD, <meta property="article:modified_time">, or at minimum ensure your server sends a Last-Modified header.

JSON-LD html
<!-- Option 1: JSON-LD (preferred) -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title",
  "datePublished": "2026-01-15T09:00:00Z",
  "dateModified": "2026-02-28T14:30:00Z"
}
</script>

<!-- Option 2: Open Graph meta tags -->
<meta property="article:published_time" content="2026-01-15T09:00:00Z">
<meta property="article:modified_time" content="2026-02-28T14:30:00Z">

<!-- Option 3: HTML time element -->
<time datetime="2026-02-28T14:30:00Z">Updated February 28, 2026</time>

<!-- Server-level: Ensure Last-Modified header is sent -->
# Nginx: add_header Last-Modified $date_gmt;
# Apache: FileETag MTime (default)
Failed Link response headers +3 overall pts

No Link response header found on the root page. Agents must parse HTML to discover related resources.

Link response headers
HIGH

Link response headers (RFC 8288) tell agents about machine-readable resources at request time. Cloudflare's isitagentready.com and other scanners explicitly look for `api-catalog`, `service-desc`, `service-doc`, and `sitemap` rels to enable agent discovery without parsing HTML.

Add an RFC 8288 Link response header advertising your OpenAPI document, API catalog, and sitemap so agents can discover them at request time.

Server config plain
# Nginx
add_header Link '</.well-known/api-catalog>; rel="api-catalog", </openapi.json>; rel="service-desc", </sitemap.xml>; rel="sitemap"' always;

# Phoenix / Plug
plug :put_link_headers

defp put_link_headers(conn, _opts) do
  put_resp_header(
    conn,
    "link",
    "</.well-known/api-catalog>; rel=\"api-catalog\", " <>
      "</openapi.json>; rel=\"service-desc\", " <>
      "</sitemap.xml>; rel=\"sitemap\""
  )
end

# Test: curl -I https://natuurhuisje.nl/ | grep -i '^link:'
Failed Content-Security-Policy +2 overall pts

Content-Security-Policy header is not set.

Content-Security-Policy
HIGH

Content-Security-Policy prevents XSS and injection attacks. For AI agents that interact with your site, CSP ensures the page content hasn't been tampered with by malicious scripts.

Add a Content-Security-Policy header with directives like default-src, script-src, and style-src.

Server config plain
# Nginx
add_header Content-Security-Policy "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'" always;

# Apache (.htaccess)
Header always set Content-Security-Policy "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'"
Failed Entity linking (@id) +2 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": "natuurhuisje.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://natuurhuisje.nl/#organization",
      "name": "Your Company",
      "url": "https://natuurhuisje.nl"
    },
    {
      "@type": "WebSite",
      "@id": "https://natuurhuisje.nl/#website",
      "name": "Your Site",
      "url": "https://natuurhuisje.nl",
      "publisher": { "@id": "https://natuurhuisje.nl/#organization" }
    }
  ]
}
</script>
Failed Author attribution +2 overall pts

No author attribution found. Agents and search engines cannot tell who stands behind this content or link it to a known author entity.

Author attribution
HIGH

Author attribution gives agents and search engines a clear, machine-readable signal of who stands behind the content and links it to a known entity. This supports trust and provenance (E-E-A-T) and lets systems attribute the content to its author.

Add author information using JSON-LD (preferred), <meta name="author">, or <a rel="author">. Clear authorship is a trust and provenance signal for agents and search engines.

JSON-LD html
<!-- Option 1: JSON-LD author in Article (preferred) -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title",
  "author": {
    "@type": "Person",
    "name": "Jane Smith",
    "url": "https://natuurhuisje.nl/team/jane-smith"
  }
}
</script>

<!-- Option 2: Meta tag -->
<meta name="author" content="Jane Smith">

<!-- Option 3: Linked author -->
<a rel="author" href="https://natuurhuisje.nl/team/jane-smith">Jane Smith</a>
Failed Trust anchor pages +2 overall pts

Verified none; missing or thin: about, contact, privacy.

Trust anchor pages
HIGH

Agents check about, contact and privacy pages to verify a business is legitimate and to answer contact questions before recommending it. Thin or missing trust pages read as an anonymous site.

Publish real /about, /contact and /privacy pages (or localized equivalents linked from the home page) with at least 500 characters of content each, and link them from the footer so agents and crawlers can find them.

Partial AI crawler directives +2 overall pts

No AI crawlers explicitly mentioned in robots.txt (implicit default allow applies).

AI crawler directives
MEDIUM

Major AI systems use dedicated crawlers (GPTBot, ClaudeBot, Amazonbot). Explicit directives signal whether you want your content included in AI training and search results.

Add a wildcard Allow: / or explicit AI user-agent directives to signal crawling intent.

robots.txt plain
# 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: /
Failed OAuth Discovery +1 overall pts

No OAuth/OIDC discovery document found at /.well-known/oauth-authorization-server or /.well-known/openid-configuration.

OAuth Discovery
HIGH

OAuth/OIDC discovery (RFC 8414, OpenID Connect Discovery 1.0) lets agents authenticate with your APIs without out-of-band setup. Cloudflare's isitagentready.com requires this for Level 4-5 readiness.

Publish an OAuth 2.0 Authorization Server Metadata document at /.well-known/oauth-authorization-server so agents can discover your auth endpoints.

# Serve OAuth 2.0 Authorization Server Metadata at:
# https://example.com/.well-known/oauth-authorization-server
{
  "issuer": "https://example.com",
  "authorization_endpoint": "https://example.com/oauth/authorize",
  "token_endpoint": "https://example.com/oauth/token",
  "response_types_supported": ["code"],
  "grant_types_supported": ["authorization_code", "refresh_token"]
}
Failed Agent Auth Readiness +1 overall pts

Agent auth readiness issues: missing PKCE S256 support, missing scoped permissions metadata, missing protected-resource metadata or WWW-Authenticate hint, missing valid auth.md, missing agent-safe OAuth grant declaration.

Agent Auth Readiness
HIGH

Agents need more than a login page. They need discoverable auth metadata, scoped permissions, PKCE support, and a concise walkthrough that explains how to obtain and use credentials safely.

Publish OAuth metadata with PKCE S256 and scopes, OAuth Protected Resource metadata, WWW-Authenticate hints on protected endpoints, and an /auth.md walkthrough for agents.

auth.md plain
# /auth.md
# Authentication for agents

Use OAuth 2.0 authorization code with PKCE S256. Request the narrowest scope for the task. Protected API endpoints return WWW-Authenticate with resource metadata.
Partial Schema validation +1 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.

Partial Form field autocomplete +0 overall pts

4/10 applicable form inputs have autocomplete attributes (6 missing).

Form field autocomplete
MEDIUM

The autocomplete attribute tells AI agents and browsers what type of data a field expects (email, name, address). This semantic hint helps AI agents fill forms accurately without guessing field purposes from visual context.

Add autocomplete attributes to form inputs so AI agents and browsers understand the expected data type. Use standard values like "email", "name", "tel", "street-address". See html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill for the full list.

<input type="email" name="email" autocomplete="email">
<input type="text" name="name" autocomplete="name">
<input type="tel" name="phone" autocomplete="tel">
<input type="text" name="address" autocomplete="street-address">
Partial Dynamic widget state +0 overall pts

Detected 36 dynamic widget(s), 3 ARIA state attribute(s), and 0 live region(s).

Dynamic widget state
MEDIUM

Agents operate interactive widgets through the accessibility tree. Expandable panels, tabs, menus, switches, dialogs, and async status areas need explicit state so agents can tell what is open, selected, checked, current, or updating.

Expose dynamic widget state with aria-expanded, aria-selected, aria-checked, aria-current, aria-pressed, aria-controls, and aria-live or role="status" for async updates.

<button aria-expanded="false" aria-controls="filters">Filters</button>
<section id="filters" hidden>...</section>
<div role="status" aria-live="polite"></div>
Partial Heading hierarchy +0 overall pts

Good hierarchy but some headings have empty text content.

Heading hierarchy
MEDIUM

AI agents use headings to build a content outline and determine topic hierarchy. A clear h1→h2→h3 structure helps AI systems extract and summarize your content accurately.

Ensure exactly one <h1> per page. Use sequential heading levels without skipping (h1 -> h2 -> h3, not h1 -> h3). All headings should contain meaningful text. See developer.mozilla.org/en-US/docs/Web/HTML/Element/Heading_Elements for heading element documentation.

HTML html
<h1>Page Title - One Per Page</h1>
  <h2>Main Section</h2>
    <h3>Subsection</h3>
    <h3>Subsection</h3>
  <h2>Another Section</h2>
    <h3>Subsection</h3>
Partial Question-based headings +0 overall pts

1/6 H2 headings use question format ("Jouw plek verhuren?"). Adding more question-based H2s would improve AI citation rates.

Question-based headings
MEDIUM

AI systems often treat an H2 as a prompt and the paragraph beneath it as the answer. A study of 3M ChatGPT responses found that, among citations tied to questions, 78.4% came from headings, and cited content was about twice as likely to contain a question mark (Kevin Indig / Growth Memo).

Rewrite H2 headings as questions your audience asks. For example, instead of "Domain Authority Metrics" use "How does domain authority affect AI citations?". A study of 3M ChatGPT responses found 78.4% of question-related citations came from headings (Kevin Indig / Growth Memo).

<!-- Instead of keyword-focused headings: -->
<h2>Domain Authority Metrics</h2>
<h2>SEO Best Practices</h2>

<!-- Use question-based headings: -->
<h2>How does domain authority affect AI citations?</h2>
<h2>What SEO practices improve AI visibility?</h2>
<h2>Why do AI systems prefer structured content?</h2>
Failed Button accessible names +0 overall pts

10/42 buttons have accessible names (32 missing).

Button accessible names
HIGH

AI agents invoke buttons by their accessible name in the accessibility tree. Without a discernible name, an AI agent cannot identify what a button does, making form submission and page interaction impossible.

Ensure all buttons have accessible names via text content, aria-label, aria-labelledby, or value attribute. AI agents cannot invoke unnamed buttons. See w3.org/WAI/WCAG22/Understanding/name-role-value.html for WCAG guidelines.

HTML html
<!-- Good: text content as name -->
<button>Submit form</button>

<!-- Good: aria-label for icon buttons -->
<button aria-label="Close dialog">
  <svg>...</svg>
</button>

<!-- Bad: empty button with no name -->
<button><img src="icon.svg"></button>
Partial Semantic HTML elements +0 overall pts

Found 4/5 semantic elements: article/section, header, main, footer.

Semantic HTML elements
MEDIUM

Browser agents may combine the DOM, accessibility tree, and screenshots. Semantic elements like <main>, <nav>, and <article> provide durable structural meaning across those representations.

Add missing semantic elements: nav. Semantic HTML helps AI agents identify page regions and navigate content structure. See developer.mozilla.org/en-US/docs/Glossary/Semantics#semantics_in_html for semantic HTML documentation.

HTML html
<body>
  <header>
    <nav><!-- primary navigation --></nav>
  </header>
  <main>
    <article>
      <h1>Page Title</h1>
      <section><!-- content section --></section>
    </article>
  </main>
  <footer><!-- site footer --></footer>
</body>
Partial Image alt text +0 overall pts

26/31 images have alt attributes (5 missing).

Image alt text
MEDIUM

Some browser agents can inspect screenshots, but image understanding varies by access mode. Descriptive alt text provides a durable machine-readable description of image content and context.

Add descriptive alt text to all images. Use alt="" for purely decorative images. Missing alt attributes prevent AI agents from understanding image content. See w3.org/WAI/WCAG22/Understanding/non-text-content.html for WCAG guidelines on non-text content.

HTML html
<!-- Descriptive alt text for meaningful images -->
<img src="chart.png" alt="Revenue growth chart showing 40% increase in Q4 2025">

<!-- Empty alt for purely decorative images -->
<img src="divider.svg" alt="">
Fix with AI Skills
$ /plugin marketplace add bartwaardenburg/isagentready-skills

Detailed results

Agent Protocols

Weight 15% · 1 failed checkpoint · 5 bonus opportunities

0/100
AI Content Discovery

Weight 30% · 3 failed, 1 partial · 6 bonus opportunities

58/100
Security & Trust

Weight 15% · 3 failed checkpoints · 1 bonus opportunity

63/100
Content & Semantics

Weight 20% · 1 failed, 7 partial

82/100
AI Search Signals

Weight 20% · 4 failed, 1 partial

42/100
Supplemental evidence AI visitor test and training exposure. The score does not change.
AI Training Exposure

Does not affect the readiness score

Supplemental

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.

Next steps

DEVELOPER TOOLS

Scan and fix from your editor. Install the MCP server to scan, and AI skills to fix.

SCAN
$ claude mcp add isagentready-mcp -- npx -y isagentready-mcp
FIX
$ /plugin marketplace add bartwaardenburg/isagentready-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

We'll use this address to send report updates.