alexdekroon.nl
Finalizing the report
Preparing the stored Is Agentic score
Essential—
Recommended—
Bonus signals—
alexdekroon.nl
Preparing the stored Is Agentic score
alexdekroon.nl
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Needs work
Weighted across 17 applicable checks
Strong
Weighted across 1 applicable check
Blocked
Weighted across 1 applicable check
Critical access gaps come first, followed by other applicable readiness gaps.
Keep the correct HTTP 404 status. The remaining requirement is a Markdown error body when agents request Accept: text/markdown. Include at least 20 characters explaining the error and a link to your docs, sitemap, or llms.txt. Verify with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/some-path-that-does-not-exist. Check both the final 404 status and the Markdown body with Content-Type: text/markdown. Checking the status alone does not verify the missing requirement.
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup.
Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/ and curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.
Add description to the LocalBusiness JSON-LD entity for full score.
Checks are grouped by relevance for Business sites.
814 chars with H1, but 2.3% content ratio is below the 5% target
How to pass
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup.
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh stubs, JavaScript-redirect stubs, or cross-domain hops across 6 checked pages
All 5 sampled pages are publicly readable (4 with substantive content)
Homepage https://alexdekroon.nl does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "accept-encoding")
How to pass
Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/ and curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
The nonexistent path https://alexdekroon.nl/__ora-404-probe-g6k7bere correctly returns HTTP 404. Partial credit: no Markdown error body was detected.
How to pass
Keep the correct HTTP 404 status. The remaining requirement is a Markdown error body when agents request Accept: text/markdown. Include at least 20 characters explaining the error and a link to your docs, sitemap, or llms.txt. Verify with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/some-path-that-does-not-exist. Check both the final 404 status and the Markdown body with Content-Type: text/markdown. Checking the status alone does not verify the missing requirement.
alexdekroon.nl ranks #1 for "Alex De Kroon Erdbau"
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://www.alexdekroon.nl/sitemap.xml with multiple sitemaps entries
JSON-LD LocalBusiness found - missing description on this entity
How to pass
Add description to the LocalBusiness JSON-LD entity for full score.
3/4 metadata signals present - missing: og:image
How to pass
Add all four signals to your homepage: <link rel="canonical">, <html lang="...">, <meta property="og:image">, and <meta property="og:type">. Agents use these for entity resolution and attribution.
Organization schema found but missing: contactPoint
How to pass
Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
No trust anchor pages found with sufficient content (About, Contact, Privacy)
How to pass
Publish real /about, /contact, and /privacy pages with at least 500 characters of content each. These are the pages AI agents check to verify your business is legitimate before recommending you.
All 6 measured pages fit an agent context budget (largest ~1K tokens)
Name search surfaced no pages on alexdekroon.nl, although developer resources exist on the site (MCP server) - weak search indexing or transient search noise
How to pass
Check whether your developer resources (API docs, OpenAPI spec, auth docs, developer portal, MCP server, SDK documentation) surface in name-based searches. If they do not, use predictable URLs, link them in llms.txt, and include your product name in page titles and headings. This result reflects one search sample.
MCP server referenced in llms.txt
Rich agent mode view at ?mode=agent with 5 agent signals and navigation links
Modular llms.txt files found for sections: docs, api, developers, guides, reference, ohne-machinist, mit-machinist, bergbau-tagebau, projekten, kontakt
100% of 11 sampled sitemap entries carry lastmod; newest is 258 day(s) old
Found the llms.txt at https://alexdekroon.nl/llms.txt.
The llms.txt is well-formatted: 50 lines with markdown links, 3,629 characters in total.
Some extended schema types found: LocalBusiness - add 2 more types, such as FAQPage, Service, or AggregateRating, for full coverage
How to pass
Add 2 more JSON-LD types that fit your page, such as FAQPage, Service, or AggregateRating.
1 of 3 probed llms.txt links could not be verified: https://www.alexdekroon.nl/_api/mcp (HTTP 401). This does not confirm that those pages are missing.
How to pass
Check the reported responses and retry links that could not be verified. Authentication, bot protection, rate limits, or temporary server errors can prevent verification. Correct any separately reported missing pages.
Code fences balanced across 1 markdown document
All 10 tools on product MCP have detailed descriptions (>= 20 chars)
7/10 tools on product MCP have parameter schemas
How to pass
Define inputSchema with typed properties and required arrays for each tool. Agents need schema info to construct valid tool calls without guessing.
product MCP exposes 10 tools - substantial tool surface
Onboarding signals described but not verified live: self-serve key generation, sandbox/test environment
How to pass
Offer a free tier or trial, self-serve API key generation, and a sandbox environment. Agents can't fill out 'contact sales' forms.
MCP server connected via Streamable HTTP - Site Visitor Assistant for site "Alex De Kroon" (https://www.alexdekroon.nl/_api/mcp) v1.0.0 (protocol 2025-11-25)
product MCP returns error for invalid tool call but missing structured code or message
How to pass
Return structured JSON-RPC errors (with code and message) when agents call invalid tools or pass bad arguments. Don't crash or return empty responses.
product MCP uses modern Streamable HTTP transport
NLWeb /ask endpoint exists but requires authentication (HTTP 403, via POST)
product MCP: 5/10 tools have behavioral annotations (readOnlyHint/destructiveHint)
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
20 native controls, 3 non-native div-soup affordances (87% native).
20/20 interactive elements have a computable accessible name (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
UCP discovery profile at https://alexdekroon.nl/.well-known/ucp; version 2026-04-08; capabilities: dev.ucp.shopping.cart, dev.ucp.shopping.catalog.lookup, dev.ucp.shopping.checkout, dev.ucp.shopping.fulfillment
What does alexdekroon.nl do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does alexdekroon.nl do and who is it for? Explain it back to me.
6 steps1 reasoning step
Agent successfully assembled a working summary of Alex de Kroon's business model, services, and positioning from the sparse homepage. The site is navigable but minimally detailed—all core facts were accessible from the root page, though the Projects section failed; the agent had to work around missing pricing, team info, and portfolio details rather than finding them published.