Skip to content
A

aquahotplus.nl

Compare
Scan history Scanned 2026-08-29 19:14 UTC
39/100 Current
29/100 Compare
30/100 Comparing
32/100 Compare
Changes since selected scan Not comparable because methodology information is unavailable

Result summary

Measured stable-core coverage

39/100

Methodology grade

D

Methodology 2026-08-29

28 core checkpoints assessed

Find
3/7 passed
Read
7/20 passed
Act
1/1 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://aquahotplus.nl",
  "logo": "https://aquahotplus.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 XML Sitemap +4 overall pts

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

# Add to /robots.txt:
Sitemap: https://aquahotplus.nl/sitemap.xml
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://aquahotplus.nl",
  "logo": "https://aquahotplus.nl/logo.png",
  "sameAs": [
    "https://twitter.com/yourcompany",
    "https://linkedin.com/company/yourcompany"
  ]
}
</script>
Sources
Failed Server-side rendered content +4 overall pts

No meaningful visible text found in <body>. Page may require JavaScript to render.

Server-side rendered content
HIGH

Fetch-only crawlers and non-rendered retrieval cannot depend on client-side JavaScript. Browser agents may combine the rendered DOM, accessibility tree, and screenshots. Meaningful server-rendered HTML keeps core content available across both access modes.

Render meaningful content in the initial HTML with server-side rendering (SSR) or static site generation (SSG). This supports fetch-only crawlers and non-rendered retrieval while giving browser agents a reliable DOM and accessibility tree. See web.dev/articles/ai-agent-site-ux for current agent-friendly guidance.

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
Failed 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
Failed Semantic HTML elements +4 overall pts

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

Semantic HTML elements
HIGH

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: article or section, header, nav, main, footer. 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 Soft-404 hygiene +3 overall pts

A randomized unknown path (aquahotplus.nl/isagentready-missing-9BKq3Nxw1Wqqwv53) returned HTTP 200 with the same content as the home page instead of a 404 (soft 404).

Soft-404 hygiene
HIGH

Agents and crawlers rely on a real 404 or 410 status to know a resource is missing. A 200 with the app shell (soft 404) makes them believe every probed path exists, pollutes indexes, and hides broken links from monitoring.

Return a real HTTP 404 (or 410) status for paths that do not exist, never a 200 with the app shell. Give the 404 body a short pointer to your sitemap, llms.txt or docs index, and verify with `curl -sI yourdomain.com/some-missing-path` (the status line must read 404). 

# Phoenix: let unmatched routes reach a real 404 instead of a catch-all redirect
# Express:
app.use((req, res) => {
  res.status(404).type("text/markdown").send("# Not found\n\nSee /sitemap.xml and /llms.txt");
});
# Nginx: never rewrite unknown paths to index.html for non-SPA routes
try_files $uri $uri/ =404;
Sources
Failed 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 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 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.

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

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

<!-- Option 3: Linked author -->
<a rel="author" href="https://aquahotplus.nl/team/jane-smith">Jane Smith</a>
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
Failed Document title +2 overall pts

No <title> element found in the document.

Document title
HIGH

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.

Add a <title> element inside <head> with a descriptive, unique title. AI agents use this as the primary page identifier. See developer.mozilla.org/en-US/docs/Web/HTML/Element/title for documentation. 

<head>
  <title>AI Agent Readiness Scanner - IsAgentReady.com</title>
</head>
Sources
Failed Accessible landmarks & ARIA +2 overall pts

No landmark regions or ARIA attributes found.

Accessible landmarks & ARIA
HIGH

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.

No page landmarks found. Use semantic HTML elements: <header>, <nav>, <main>, <footer>. These automatically create ARIA landmarks for assistive technology and AI agents. 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
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 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
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
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% · 4 failed, 1 partial · 5 bonus opportunities

53/100
Security & Trust

Weight 15% · 1 failed checkpoint

93/100
Content & Semantics

Weight 20% · 6 failed checkpoints

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