jmouders.nl

Item: jmouders.nl
Rating: 19

Compare

Scan history Scanned 2026-05-18 10:56 UTC

2026-08-29 11:59 UTC 25/100 Compare

2026-05-18 10:56 UTC 19/100 Current

2026-03-03 13:17 UTC 58/100 Compare

2026-03-01 15:32 UTC 62/100 Compare

Result summary

Measured coverage

19/100

Methodology grade

Methodology legacy

35 checkpoints assessed

Find: 0/6 passed
Read: 8/20 passed
Act: 1/9 passed

Bot protection context

This site uses Cloudflare bot protection. Our scanner received a challenge page instead of real content, so the scores below reflect what AI systems can access, not the actual site quality. Well-known brands may still appear in AI answers via training data and search indexes, but direct access by both crawlers and agents is blocked.

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.

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://jmouders.nl",
  "logo": "https://jmouders.nl/logo.png"
}
</script>

Sources

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

Heading hierarchy +4 overall pts

No headings found on the page.

Heading hierarchy

HIGH

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.

Add a clear <h1> heading and use sequential heading levels (h1 -> h2 -> h3). Proper heading hierarchy helps AI agents understand page structure and content importance. 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>

Sources

Semantic HTML elements +4 overall pts

No semantic HTML elements found (<header>, <nav>, <main>, <article>/<section>, <footer>).

Semantic HTML elements

HIGH

AI agents navigate pages using the accessibility tree, not visual layout. Semantic elements like <main>, <nav>, and <article> provide structural meaning that AI systems rely on to parse content.

Add missing semantic elements: header, nav, main, footer, article or section. 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>

Sources

robots.txt present +4 overall pts

robots.txt returned HTTP 403.

robots.txt present

HIGH

robots.txt is the universal standard for telling crawlers what they can access. AI crawlers like GPTBot, ClaudeBot and Googlebot-Extended check this file first before crawling your site.

Create a robots.txt file at the root of your website.

robots.txt plain

# /robots.txt
User-agent: *
Allow: /

# Allow AI crawlers explicitly
User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

Sitemap: https://jmouders.nl/sitemap.xml

Sources

XML Sitemap +4 overall pts

No valid XML sitemap found. Checked: jmouders.nl/sitemap.xml, jmouders.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://jmouders.nl/</loc>
    <lastmod>2025-01-15</lastmod>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>https://jmouders.nl/about</loc>
    <lastmod>2025-01-10</lastmod>
  </url>
</urlset>

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

Sources

llms.txt +4 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
# jmouders.nl

> jmouders.nl - your site description here.

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

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

Sources

Meta robots / X-Robots-Tag +4 overall pts

Page has noindex directive, preventing AI indexing. Directives found: noindex, nofollow.

Meta robots / X-Robots-Tag

HIGH

Meta robots tags and X-Robots-Tag headers control per-page indexing. Restrictive directives like noindex or noai prevent AI systems from using your content.

Remove the noindex directive to allow AI systems to index this page.

HTML html

<!-- Replace noindex with index to allow AI indexing -->
<meta name="robots" content="index, follow">

<!-- Or remove the meta tag entirely (default is index, follow) -->

Sources

Content negotiation (text/markdown) +4 overall pts

Server returned HTTP 403 for Accept: text/markdown request.

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://jmouders.nl/

Sources

HTTP bot accessibility +4 overall pts

Page returned HTTP 403 - the site blocks automated access. All content-based checks below are based on the error page, not the actual content.

HTTP bot accessibility

HIGH

AI crawlers and agents must be able to fetch your pages via HTTP. If bots are blocked, AI systems cannot index or interact with your content.

Allow legitimate bot traffic by configuring your WAF/CDN (Cloudflare, Akamai, etc.) to permit known AI user-agents. Blocking all bots prevents AI agents from accessing your content.

# Cloudflare WAF - allow known AI crawlers (managed rule skip)
# Dashboard → Security → WAF → Custom Rules → Create rule:
#   Field: User Agent | Operator: contains | Value: GPTBot
#   Then: Skip remaining rules

# Nginx - allow specific AI bot user-agents
map $http_user_agent $is_ai_bot {
  default         0;
  "~*GPTBot"      1;
  "~*ClaudeBot"   1;
  "~*Amazonbot"   1;
}
# Use $is_ai_bot in your rate-limiting or access rules

Sources

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://jmouders.nl",
  "logo": "https://jmouders.nl/logo.png",
  "sameAs": [
    "https://twitter.com/yourcompany",
    "https://linkedin.com/company/yourcompany"
  ]
}
</script>

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

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

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://jmouders.nl/agent",
  "version": "1.0.0",
  "capabilities": {
    "streaming": true,
    "pushNotifications": false
  },
  "supportedInterfaces": [
    {
      "url": "https://jmouders.nl/mcp",
      "transport": "http",
      "protocol": "MCP/2025-06-18",
      "protocolBinding": "MCP",
      "protocolVersion": "2025-06-18"
    }
  ],
  "preferredTransport": "MCP",
  "skills": [
    {"id": "support", "name": "Customer Support"}
  ]
}

Sources

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 strongly prefer recent content. ChatGPT gives 3.2× more citations to content updated within 30 days. 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. Content updated within 3 months averages 67% more AI citations.

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)

Sources

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://jmouders.nl/ | grep -i '^link:'

Sources

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

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

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

<!-- Option 3: Linked author -->
<a rel="author" href="https://jmouders.nl/team/jane-smith">Jane Smith</a>

Sources

OpenAPI / API documentation +3 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

Server-side rendered content +2 overall pts

Limited visible text (41 chars) but <noscript> fallback present.

Server-side rendered content

MEDIUM

Neither AI crawlers nor AI agents execute JavaScript. They parse raw HTML to understand page content. Without server-side rendering, your content is invisible to both training crawlers and task-completing agents.

Implement server-side rendering (SSR) or static site generation (SSG) so AI agents can read your content without executing JavaScript. See web.dev/articles/rendering-on-the-web for a comparison of rendering strategies.

page.js plain

// Next.js - use getServerSideProps for SSR
export async function getServerSideProps() {
  const data = await fetchData();
  return { props: { data } };
}

// Or use generateStaticParams for SSG (App Router)
export async function generateStaticParams() {
  return [{ slug: "about" }, { slug: "contact" }];
}

Sources

Accessible landmarks & ARIA +1 overall pts

1 landmark regions via semantic HTML (main). No additional ARIA attributes found.

Accessible landmarks & ARIA

MEDIUM

ARIA landmarks help AI agents identify page regions (navigation, main content, footer). This is the same API used by screen readers and is increasingly used by AI browsing agents.

Use semantic HTML elements to define page regions: <header>, <nav>, <main>, <footer>. These provide implicit ARIA landmarks without needing explicit role attributes. See w3.org/WAI/ARIA/apg/patterns/landmarks for the W3C landmarks pattern.

HTML html

<!-- Semantic elements provide implicit ARIA landmarks -->
<header><!-- banner landmark -->
  <nav aria-label="Primary"><!-- navigation landmark -->
    <a href="/" aria-current="page">Home</a>
  </nav>
</header>
<main><!-- main landmark -->
  <article>...</article>
</main>
<footer><!-- contentinfo landmark --></footer>

Sources

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

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

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

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://jmouders.nl/mcp"},
  "capabilities": {"tools": {"listChanged": false}}
}

Sources

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://jmouders.nl/agents/support",
      "protocol": "a2a"
    }
  ]
}

Sources

Fix with AI Skills

$ /plugin marketplace add bartwaardenburg/isagentready-skills

Detailed results

Agent Protocols

Weight 15% · 8 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

AI Content Discovery

Weight 30% · 8 failed checkpoints

0/100

robots.txt present: Failed

AI crawler directives: Skipped

XML Sitemap: Failed

llms.txt: Failed

Meta robots / X-Robots-Tag: Failed

Content freshness signals: Failed

Content negotiation (text/markdown): Failed

HTTP bot accessibility: Failed

Link response headers: Failed

Security & Trust

Weight 15% · 1 failed checkpoint

73/100

HTTPS: Passed

HSTS header: Failed

Content-Security-Policy: Passed

X-Content-Type-Options: Passed

Frame protection: Passed

CORS configuration: Passed

Referrer-Policy: Passed

Content & Semantics

Weight 20% · 2 failed, 2 partial

40/100

Server-side rendered content: Partial

Document title: Passed

aria-hidden misuse: Passed

Heading hierarchy: Failed

Semantic HTML elements: Failed

Accessible landmarks & ARIA: Partial

Language attribute: Passed

AI Search Signals

Weight 20% · 5 failed checkpoints

0/100

JSON-LD present: Failed

Organization / WebSite schema: Failed

High-value schema types: Failed

FAQPage schema: Failed

Author attribution: Failed

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 robots.txt found. Training crawlers can freely 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


            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

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

Audit more pages with a site audit

Result summary

Action plan

JSON-LD present

High-value schema types

Heading hierarchy

Semantic HTML elements

robots.txt present

XML Sitemap

llms.txt

Meta robots / X-Robots-Tag

Content negotiation (text/markdown)

HTTP bot accessibility

Organization / WebSite schema

HSTS header

WebMCP Declarative API

A2A Agent Card

Content freshness signals

Link response headers

FAQPage schema

Author attribution

OpenAPI / API documentation

Server-side rendered content

Accessible landmarks & ARIA

API Catalog (RFC 9727)

Agent Skills index

WebMCP manifest

MCP Discovery

agents.json

Detailed results

Next steps

Get your detailed report

Anonymous analytics