Skip to content
E

elegance.nl

Compare
SCAN HISTORY
64/100 Compare
48/100 Compare
55/100 Compare
58/100 Compare
Changes since selected scan Not comparable because methodology information is unavailable

Result summary

Readiness profiles

Methodology legacy

Measured coverage

48/100

Methodology grade

C

50 checkpoints assessed

20

Passed

6

Partial

24

Failed

0

Skipped

Strongest category

Content & Semantics

Weakest category

Agent Protocols

Action plan

Priority actions Highest-impact implementation details
3 prioritized actions

Prioritized by exact impact on the overall stable-core score.

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 llms.txt +3 overall pts

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

llms.txt
HIGH

llms.txt provides a curated entry point for AI agents — coding assistants, browsing agents, and task automation tools that fetch specific pages to complete tasks. Unlike crawlers that scrape everything, agents benefit from a structured overview of your most important pages.

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

llms.txt plain 
# /llms.txt
# elegance.nl

> elegance.nl - your site description here.

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

## Optional
- [Blog](https://elegance.nl/blog)
- [Changelog](https://elegance.nl/changelog)
Sources
Failed Content negotiation (text/markdown) +3 overall pts

Server returned HTML (content-type: text/html; charset=utf-8) when Accept: text/markdown was requested. No content negotiation support detected.

Content negotiation (text/markdown)
HIGH

AI agents fetch pages programmatically and benefit from machine-readable formats. Serving Markdown via Accept: text/markdown allows agents to consume structured content without HTML parsing overhead — saving up to 80% of tokens while preserving headings, links, and emphasis.

Serve Markdown when AI agents request it via `Accept: text/markdown`. Add a `Vary: Accept` header so CDN caches serve format-appropriate responses. 

# Express.js middleware
app.get('*', (req, res, next) => {
  if (req.accepts('text/markdown')) {
    res.set('Content-Type', 'text/markdown')
    res.set('Vary', 'Accept')
    return res.sendFile(markdownPath(req.path))
  }
  next()
})

# Phoenix / Plug
case get_req_header(conn, "accept") do
  [accept | _] when accept =~ "text/markdown" ->
    conn
    |> put_resp_content_type("text/markdown")
    |> put_resp_header("vary", "Accept")
    |> send_resp(200, markdown_for(conn.request_path))
    |> halt()
  _ -> conn
end

# Test: curl -H "Accept: text/markdown" https://elegance.nl/
Sources
Fix with AI Skills
$ /plugin marketplace add bartwaardenburg/isagentready-skills

Detailed results

Agent Protocols Weight 15% Needs attention

9 failed checkpoints

0/100
AI Content Discovery Weight 30% Needs attention

4 failed, 2 partial

54/100
Security & Trust Weight 15% Needs attention

6 failed checkpoints

33/100
Content & Semantics Weight 20% Needs attention

2 failed, 4 partial

74/100
AI Search Signals Weight 20% Needs attention

3 failed checkpoints

58/100
AI Training Exposure Supplemental

Does not affect the readiness score

1 of 3 AI training protection mechanisms active.

Common Crawl presence Unknown

Could not determine the latest Common Crawl index.

Training crawler blocking Partial

4 of 8 training crawlers blocked: Amazonbot, Applebot-Extended, ClaudeBot, GPTBot. Still allowed: Bytespider, CCBot, Google-Extended, meta-externalagent.

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.

Developer Tools

Scan and fix from your editor

Install our MCP server to scan any website from your terminal. Pair it with AI agent skills to fix failing checks automatically.

  • Scan any website directly from your terminal
  • Fix failing checks with AI agent skills
  • Re-scan to verify improvements
SCAN
claude mcp add isagentready-mcp -- npx -y isagentready-mcp
FIX
/plugin marketplace add bartwaardenburg/isagentready-skills
MCP Server AI 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.