Skip to content
N

nluug.nl

Compare
Scan history Scanned 2026-05-18 10:55 UTC
64/100 Compare
49/100 Current
56/100 Compare
57/100 Compare

Result summary

Measured coverage

49/100

Methodology grade

C

Methodology legacy

42 checkpoints assessed

Find
5/8 passed
Read
11/23 passed
Act
3/11 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
HIGH

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

JSON-LD html 
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://nluug.nl",
  "logo": "https://nluug.nl/logo.png"
}
</script>
Sources
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
HIGH

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

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
Failed Organization / WebSite schema +4 overall pts

No Organization or WebSite schema type found in JSON-LD.

Organization / WebSite schema
HIGH

Organization and WebSite schemas establish your brand identity in the knowledge graph. AI systems use these to attribute content, display rich results, and build entity relationships.

Add a JSON-LD block with @type "Organization" or "WebSite" including at least "name" and "url" properties.

JSON-LD html 
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://nluug.nl",
  "logo": "https://nluug.nl/logo.png",
  "sameAs": [
    "https://twitter.com/yourcompany",
    "https://linkedin.com/company/yourcompany"
  ]
}
</script>
Sources
Failed 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
# nluug.nl

> nluug.nl - your site description here.

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

## Optional
- [Blog](https://nluug.nl/blog)
- [Changelog](https://nluug.nl/changelog)
Sources
Failed Content negotiation (text/markdown) +3 overall pts

Server returned HTML (content-type: text/html) when Accept: text/markdown was requested. No content negotiation support detected.

Content negotiation (text/markdown)
HIGH

AI agents fetch pages programmatically and benefit from machine-readable formats. Serving Markdown via Accept: text/markdown allows agents to consume structured content without HTML parsing overhead — saving up to 80% of tokens while preserving headings, links, and emphasis.

Serve Markdown when AI agents request it via `Accept: text/markdown`. Add a `Vary: Accept` header so CDN caches serve format-appropriate responses. 

# Express.js middleware
app.get('*', (req, res, next) => {
  if (req.accepts('text/markdown')) {
    res.set('Content-Type', 'text/markdown')
    res.set('Vary', 'Accept')
    return res.sendFile(markdownPath(req.path))
  }
  next()
})

# Phoenix / Plug
case get_req_header(conn, "accept") do
  [accept | _] when accept =~ "text/markdown" ->
    conn
    |> put_resp_content_type("text/markdown")
    |> put_resp_header("vary", "Accept")
    |> send_resp(200, markdown_for(conn.request_path))
    |> halt()
  _ -> conn
end

# Test: curl -H "Accept: text/markdown" https://nluug.nl/
Sources
Failed 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
Failed A2A Agent Card +3 overall pts

No A2A Agent Card found at /.well-known/agent-card.json or /.well-known/agent.json.

A2A Agent Card
HIGH

Google's Agent-to-Agent (A2A) protocol enables autonomous agent-to-agent communication. An Agent Card at /.well-known/agent-card.json (new) or /.well-known/agent.json (legacy) advertises your agent's capabilities to other AI systems.

Create an A2A Agent Card at /.well-known/agent-card.json with required fields: name, description, url, version, capabilities, supportedInterfaces.

.well-known/agent.json json 
{
  "name": "My Agent",
  "description": "An AI assistant for customer support",
  "url": "https://nluug.nl/agent",
  "version": "1.0.0",
  "capabilities": {
    "streaming": true,
    "pushNotifications": false
  },
  "supportedInterfaces": [
    {
      "url": "https://nluug.nl/mcp",
      "transport": "http",
      "protocol": "MCP/2025-06-18",
      "protocolBinding": "MCP",
      "protocolVersion": "2025-06-18"
    }
  ],
  "preferredTransport": "MCP",
  "skills": [
    {"id": "support", "name": "Customer Support"}
  ]
}
Sources
Failed FAQPage schema +3 overall pts

No FAQPage schema found. Sites with FAQPage schema are 8× more likely to be cited by ChatGPT.

FAQPage schema
HIGH

FAQPage schema is one of the strongest structured data signals for AI citation. Research shows websites with FAQPage schema are 8× more likely to appear in ChatGPT search results compared to those without it.

Add FAQPage structured data with Question/Answer pairs covering common queries about your product or service. Pages with FAQPage schema are 8× more likely to be cited by ChatGPT, making this one of the highest-ROI structured data investments for AI visibility.

JSON-LD html 
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is AI agent readiness?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "AI agent readiness measures how well a website can be discovered, understood, and interacted with by AI systems."
      }
    },
    {
      "@type": "Question",
      "name": "How do I improve my AI readiness score?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Add structured data, ensure clean semantic HTML, allow AI crawlers in robots.txt, and implement agent protocols."
      }
    }
  ]
}
</script>
Sources
Failed Author attribution +3 overall pts

No author attribution found. 96% of Google AI Overview citations come from sources with strong E-E-A-T signals including clear authorship.

Author attribution
HIGH

Author attribution is a key E-E-A-T signal. Google reports 96% of AI Overview citations come from sources with strong E-E-A-T, and expert-authored content is 3.2× more likely to be cited than generic staff-written content.

Add author information using JSON-LD (preferred), <meta name="author">, or <a rel="author">. Expert authorship is 3.2× more likely to earn AI citations.

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://nluug.nl/team/jane-smith"
  }
}
</script>

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

<!-- Option 3: Linked author -->
<a rel="author" href="https://nluug.nl/team/jane-smith">Jane Smith</a>
Sources
Failed OpenAPI / API documentation +2 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"}}
        ]
      }
    }
  }
}
Sources
Failed Content Signals (robots.txt) +2 overall pts

No Content-Signal directive found in robots.txt. AI crawlers cannot read your usage preferences.

Content Signals (robots.txt)
HIGH

Content Signals is a draft IETF standard (draft-romm-aipref-contentsignals) for declaring AI content usage preferences in robots.txt. Compliant crawlers respect signals like `ai-train=no` (do not train on this content) or `search=yes` (use for search). It is part of Cloudflare's agent web stack and gates Level 2 on their readiness scanner.

Add a `Content-Signal:` line to robots.txt declaring your AI training, search, and ai-input preferences.

robots.txt plain 
# Add to /robots.txt:
Content-Signal: ai-train=yes, search=yes, ai-input=yes
Sources
Failed Link response headers +2 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://nluug.nl/ | grep -i '^link:'
Sources
Partial AI crawler directives +1 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: /
Sources
Failed Question-based headings +1 overall pts

None of the 5 H2 headings use question format. Question-based H2 headings are 78.4% more likely to be cited by ChatGPT.

Question-based headings
HIGH

Question-based H2 headings dramatically improve AI citation likelihood. Research on 3M ChatGPT responses shows 78.4% of citations tied to questions came from H2 headings, and conversational Q&A format doubles overall citation rates.

Rewrite H2 headings as questions your audience asks. For example, instead of "Domain Authority Metrics" use "How does domain authority affect AI citations?". 78.4% of ChatGPT-cited pages use question-based H2 headings. 

<!-- 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>
Sources
Failed API Catalog (RFC 9727) +1 overall pts

No API Catalog found at /.well-known/api-catalog.

API Catalog (RFC 9727)
HIGH

API Catalog (RFC 9727 + RFC 9264 Linkset) gives agents a single discovery endpoint listing every API the site offers, with machine-readable links to OpenAPI specs (service-desc), human docs (service-doc), and health endpoints. Cloudflare's isitagentready.com scores this as part of Level 3 readiness.

Serve an RFC 9727 API Catalog at /.well-known/api-catalog with a linkset of service-desc, service-doc, and status links. 

{
  "linkset": [
    {
      "anchor": "https://example.com/api/v1",
      "service-desc": [
        {"href": "https://example.com/openapi.json", "type": "application/openapi+json"}
      ],
      "service-doc": [
        {"href": "https://example.com/docs", "type": "text/html"}
      ],
      "status": [
        {"href": "https://example.com/health", "type": "application/json"}
      ]
    }
  ]
}
Sources
Failed Agent Skills index +1 overall pts

No Agent Skills index found at /.well-known/agent-skills/index.json or /.well-known/skills/index.json.

Agent Skills index
HIGH

Agent Skills Discovery (cloudflare/agent-skills-discovery-rfc v0.2.0) lets sites publish a directory of agent-callable skills with SHA-256 verifiable SKILL.md content. Cloudflare's isitagentready.com checks this for Level 4-5 readiness.

Publish an Agent Skills index per cloudflare/agent-skills-discovery-rfc v0.2.0 with top-level "$schema" and each skill's name, type (skill-md or archive), description, url, and digest (sha256:{64-hex}). 

{
  "$schema": "https://raw.githubusercontent.com/cloudflare/agent-skills-discovery-rfc/main/schema/index.schema.json",
  "version": "0.2.0",
  "skills": [
    {
      "name": "search-products",
      "type": "skill-md",
      "description": "Search the product catalog",
      "url": "https://example.com/.well-known/agent-skills/search-products/SKILL.md",
      "digest": "sha256:abc123..."
    }
  ]
}
Sources
Failed WebMCP manifest +1 overall pts

No WebMCP manifest found at /.well-known/webmcp or /.well-known/webmcp.json.

WebMCP manifest
HIGH

A WebMCP manifest at /.well-known/webmcp.json enables pre-navigation discovery - AI agents can learn what tools your site offers before even loading the page.

Create a WebMCP manifest at /.well-known/webmcp.json with your tool definitions to enable pre-navigation agent discovery. Discovery is an active area of discussion in the WebMCP spec. 

{
  "spec": "webmcp/0.1",
  "tools": [
    {
      "name": "search",
      "description": "Search products",
      "url": "/search",
      "method": "GET",
      "parameters": [
        {"name": "q", "type": "string", "description": "Search query"}
      ]
    }
  ]
}
Sources
Failed MCP Discovery +1 overall pts

No MCP discovery document found at /.well-known/mcp.json, /.well-known/mcp/server-card.json, or /.well-known/mcp/server-cards.json.

MCP Discovery
HIGH

The Model Context Protocol (MCP) by Anthropic is the standard for connecting AI assistants to external tools and data. A discovery document lets AI systems find and connect to your MCP server. SEP-1649 (modelcontextprotocol PR 2127) defines the new server-card.json schema with serverInfo, transport, and capabilities fields.

Create an MCP server card at /.well-known/mcp/server-card.json following SEP-1649 (serverInfo.name, transport, capabilities). 

{
  "$schema": "https://modelcontextprotocol.io/schema/server-card.json",
  "name": "My Server",
  "serverInfo": {"name": "My Server", "version": "1.0.0"},
  "transport": {"type": "streamable-http", "endpoint": "https://nluug.nl/mcp"},
  "capabilities": {"tools": {"listChanged": false}}
}
Sources
Failed agents.json +1 overall pts

No agents.json found at /.well-known/agents.json or /agents.json.

agents.json
HIGH

agents.json provides a directory of AI agent endpoints on your site. It helps agent orchestration systems discover and connect to your available AI services.

Create an agents.json file at /.well-known/agents.json with your agent endpoint definitions.

agents.json json 
{
  "agents": [
    {
      "name": "Support Agent",
      "description": "Handles customer inquiries",
      "url": "https://nluug.nl/agents/support",
      "protocol": "a2a"
    }
  ]
}
Sources
Failed X-Content-Type-Options +1 overall pts

X-Content-Type-Options is set to 'nosniff, nosniff' instead of 'nosniff'.

X-Content-Type-Options
HIGH

This header prevents MIME type sniffing attacks. It ensures browsers and HTTP clients interpret your content exactly as intended, reducing the risk of content injection.

Set X-Content-Type-Options to 'nosniff'.

Server config plain 
# Nginx
add_header X-Content-Type-Options "nosniff" always;

# Apache (.htaccess)
Header always set X-Content-Type-Options "nosniff"
Sources
Failed Language attribute +1 overall pts

No lang attribute found on <html> tag.

Language attribute
HIGH

The lang attribute tells AI agents what language your content is in, enabling correct text processing, translation, and language-specific understanding.

Add a lang attribute to your <html> tag (e.g. <html lang="en">). This helps AI agents determine the content language. See developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/lang for the lang attribute documentation.

HTML html 
<html lang="en">
<!-- or for regional variants: -->
<html lang="en-US">
<html lang="nl-NL">
Sources
Partial Document title +1 overall pts

Page title is very short (5 chars): "NLUUG".

Document title
MEDIUM

AI agents use the <title> element as the primary label when citing, indexing, or summarizing a page. A missing, empty, or generic title makes your page unidentifiable in AI-generated responses and search results.

Write a unique, descriptive <title> that clearly identifies the page content (10-70 characters). AI agents use the title as the primary label when citing your page. See developer.mozilla.org/en-US/docs/Web/HTML/Element/title for documentation. 

<!-- Bad: generic or missing title -->
<title>Home</title>
<title>Untitled</title>

<!-- Good: descriptive, unique title -->
<title>AI Agent Readiness Scanner - IsAgentReady.com</title>
<title>How ChatGPT Selects Sources to Cite | Blog</title>
Sources
Partial Image alt text +0 overall pts

17/18 images have alt attributes (1 missing).

Image alt text
MEDIUM

AI agents cannot see images. Alt text is the only way for AI systems to understand image content, context, and relevance to the surrounding text.

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="">
Sources
Fix with AI Skills
$ /plugin marketplace add bartwaardenburg/isagentready-skills

Detailed results

Agent Protocols

Weight 15% · 8 failed checkpoints

0/100
AI Content Discovery

Weight 30% · 4 failed, 1 partial

59/100
Security & Trust

Weight 15% · 1 failed checkpoint

93/100
Content & Semantics

Weight 20% · 2 failed, 2 partial

86/100
AI Search Signals

Weight 20% · 5 failed checkpoints

0/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.

Audit more pages with a site audit