Skip to content
O

oogtv.nl

Compare
Scan history Scanned 2026-03-03 13:17 UTC
58/100 Compare
49/100 Compare
55/100 Current
58/100 Compare

Result summary

Measured coverage

55/100

Methodology grade

C

Methodology legacy

37 checkpoints assessed

Find
4/6 passed
Read
9/22 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 llms.txt +5 overall pts

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

llms.txt
HIGH

llms.txt is a new standard that provides LLMs with a structured overview of your site — key pages, documentation links, and context — in a format optimized for AI consumption.

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

llms.txt plain 
# /llms.txt
# oogtv.nl

> oogtv.nl — your site description here.

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

## Optional
- [Blog](https://oogtv.nl/blog)
- [Changelog](https://oogtv.nl/changelog)
Sources
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 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 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
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.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.json advertises your agent's capabilities to other AI systems.

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

.well-known/agent.json json 
{
  "name": "My Agent",
  "description": "An AI assistant for customer support",
  "url": "https://oogtv.nl/agent",
  "capabilities": {
    "streaming": true,
    "pushNotifications": false
  },
  "skills": [
    {"id": "support", "name": "Customer Support"}
  ]
}
Sources
Failed Content-Security-Policy +3 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'"
Sources
Failed 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
Failed Interactive Surface Coverage +3 overall pts

0/2 interactive surfaces covered by WebMCP tool annotations (0%). Forms: 0/1, Search: 0/1, Actions: 0/0, Filters: 0/0.

Interactive Surface Coverage
HIGH

Higher coverage of interactive surfaces with WebMCP annotations means AI agents can perform more actions on your site without screen scraping or brittle heuristics.

Add tool-name and tool-description attributes to uncovered forms and interactive elements to increase agent coverage.

Sources
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": "oogtv.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://oogtv.nl/#organization",
      "name": "Your Company",
      "url": "https://oogtv.nl"
    },
    {
      "@type": "WebSite",
      "@id": "https://oogtv.nl/#website",
      "name": "Your Site",
      "url": "https://oogtv.nl",
      "publisher": { "@id": "https://oogtv.nl/#organization" }
    }
  ]
}
</script>
Sources
Failed FAQPage schema +2 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. This is 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 Referrer-Policy +2 overall pts

Referrer-Policy header is not set.

Referrer-Policy
HIGH

Referrer-Policy controls what URL information is shared when users navigate away from your site. A strict policy protects user privacy and prevents leaking sensitive URL parameters.

Add a Referrer-Policy header (e.g., strict-origin-when-cross-origin or no-referrer).

Server config plain 
# Nginx
add_header Referrer-Policy "strict-origin-when-cross-origin" always;

# Apache (.htaccess)
Header always set Referrer-Policy "strict-origin-when-cross-origin"
Sources
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: /
Sources
Partial Content freshness signals +2 overall pts

Only HTTP Last-Modified header found. This is a server-level signal — add content-level dates (dateModified in JSON-LD or article:modified_time meta tag) for stronger freshness signals.

Content freshness signals
MEDIUM

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 a dateModified property to your JSON-LD structured data or an article:modified_time meta tag. Content with explicit modification dates gets 3.2× 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
Partial Semantic HTML elements +2 overall pts

Found 3/5 semantic elements: nav, footer, article/section.

Semantic HTML elements
MEDIUM

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, main. 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
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.

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.

Create a MCP discovery document at /.well-known/mcp.json describing your MCP server capabilities. 

{
  "mcpServers": {
    "myService": {
      "url": "https://oogtv.nl/mcp",
      "name": "My MCP Server",
      "description": "Provides tools for data access"
    }
  }
}
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://oogtv.nl/agents/support",
      "protocol": "a2a"
    }
  ]
}
Sources
Partial Author attribution +1 overall pts

Author link (rel="author") found. For stronger E-E-A-T signals, add structured data with Person schema.

Author attribution
MEDIUM

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 JSON-LD author attribution with @type "Person" including name and url. Linked authorship provides basic attribution but structured data is more reliably parsed by AI systems.

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

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

<!-- Option 3: Linked author -->
<a rel="author" href="https://oogtv.nl/team/jane-smith">Jane Smith</a>
Sources
Partial Image alt text +1 overall pts

9/13 images have alt attributes (4 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
Partial Question-based headings +1 overall pts

1/31 H2 headings use question format ("Wat gebeurt er wanneer statushouders hun inburgeringsproces niet (op tijd) afronden?"). Adding more question-based H2s would improve AI citation rates.

Question-based headings
MEDIUM

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?". Question H2s double citation likelihood in ChatGPT. 

<!-- 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 X-Content-Type-Options +1 overall pts

X-Content-Type-Options header is not set.

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.

Add the header X-Content-Type-Options: nosniff to prevent MIME type sniffing.

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

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

No frame protection found (neither X-Frame-Options nor CSP frame-ancestors).

Frame protection
HIGH

Frame protection prevents your site from being embedded in malicious iframes (clickjacking). This protects users who interact with your site through AI-suggested links.

Add X-Frame-Options: DENY (or SAMEORIGIN) or use CSP frame-ancestors directive.

Server config plain 
# Nginx
add_header X-Frame-Options "DENY" always;
# Or via CSP:
add_header Content-Security-Policy "frame-ancestors 'none'" always;

# Apache (.htaccess)
Header always set X-Frame-Options "DENY"
# Or via CSP:
Header always set Content-Security-Policy "frame-ancestors 'none'"
Sources
Fix with AI Skills
$ /plugin marketplace add bartwaardenburg/isagentready-skills

Detailed results

Agent Protocols

Weight 15% · 7 failed checkpoints

0/100
AI Content Discovery

Weight 30% · 1 failed, 2 partial

75/100
Security & Trust

Weight 15% · 5 failed checkpoints

35/100
Content & Semantics

Weight 20% · 3 partial checkpoints

84/100
AI Search Signals

Weight 20% · 3 failed, 1 partial

53/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. This emerging standard lets you declare AI usage preferences for your content.

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