Skip to content
N

nluug.nl

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

Result summary

Measured stable-core coverage

64/100

Methodology grade

C

Methodology 2026-08-29

33 core checkpoints assessed

Find
4/7 passed
Read
13/23 passed
Act
3/3 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 +6 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. This gives agents an unambiguous, machine-readable description of your page and makes it eligible for rich results in search.

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 +6 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 Endpoint check timed out +5 overall pts

Request timed out - the site may be blocking automated access.

Failed Organization / WebSite schema +5 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 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://nluug.nl/ | grep -i '^link:'
Sources
Failed Author attribution +3 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://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
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
Failed Question-based headings +1 overall pts

None of the 5 H2 headings use question format. AI systems often treat a question H2 as a prompt and cite the answer beneath it.

Question-based headings
HIGH

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 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
Partial Trust anchor pages +1 overall pts

Verified contact, privacy; missing or thin: about.

Trust anchor pages
MEDIUM

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

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
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, 1 partial · 5 bonus opportunities

71/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% · 4 failed, 1 partial

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