Skip to content
O

oogtv.nl

Compare
Scan history Scanned 2026-08-29 13:04 UTC
58/100 Current
49/100 Comparing
55/100 Compare
58/100 Compare
Changes since selected scan Not comparable because methodology information is unavailable

Result summary

Measured stable-core coverage

58/100

Methodology grade

C

Methodology 2026-08-29

36 core checkpoints assessed

Find
3/7 passed
Read
12/24 passed
Act
3/5 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 XML Sitemap +6 overall pts

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

# Add to /robots.txt:
Sitemap: https://oogtv.nl/sitemap.xml
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 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
Failed HSTS header +5 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 Content-Security-Policy +4 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 Link response headers +4 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://oogtv.nl/ | grep -i '^link:'
Sources
Failed Entity linking (@id) +3 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 Trust anchor pages +3 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.

Sources
Partial AI crawler directives +3 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 Referrer-Policy +3 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 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 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 a dateModified property to your JSON-LD structured data or an article:modified_time meta tag, so AI systems can read when the content was last updated.

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
Failed Form field autocomplete +2 overall pts

0/1 applicable form inputs have autocomplete attributes (1 missing).

Form field autocomplete
HIGH

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">
Sources
Partial Author attribution +2 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 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 JSON-LD author attribution with @type "Person" including name and url. Structured data is parsed more reliably by agents and search engines than link-based attribution.

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
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
Partial Semantic HTML elements +1 overall pts

Found 3/5 semantic elements: article/section, nav, 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: 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
Partial Image alt text +1 overall pts

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

1/31 H2 headings use question format ("Bouwstof #28: Het groenblauwe hart voor Stadshavens, waar komt dat?"). 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>
Sources
Failed Button accessible names +1 overall pts

1/4 buttons have accessible names (3 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>
Sources
Fix with AI Skills
$ /plugin marketplace add bartwaardenburg/isagentready-skills

Detailed results

Agent Protocols

Weight 15% · No applicable checkpoints · 5 bonus opportunities

Not assessed
AI Content Discovery

Weight 30% · 2 failed, 2 partial · 5 bonus opportunities

63/100
Security & Trust

Weight 15% · 5 failed checkpoints

27/100
Content & Semantics

Weight 20% · 2 failed, 3 partial

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

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.

Add this badge to your README Show the latest ranked grade and link readers to this report
AI readiness badge for oogtv.nl

The badge shows the grade from the latest ranked scan. Caches refresh it within an hour.

Markdown plain 
[![AI-ready](https://isagentready.com/badge/oogtv.nl.svg)](https://isagentready.com/en/scan/oogtv.nl)
HTML html 
<a href="https://isagentready.com/en/scan/oogtv.nl"><img src="https://isagentready.com/badge/oogtv.nl.svg" alt="AI-ready"></a>

Audit more pages with a site audit