01Fail
Markdown content negotiation
+8 pts if fixed
Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.
See full details
02Fail
/llms.txt
+6 pts if fixed
Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
See full details
03Fail
Explicit AI bot rules
+5 pts if fixed
Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
See full details

Hand-off prompt for your coding agent6 issues

# Agent-readiness remediation brief

Site: https://klyochat.com/
Platform: nextjs (99% confidence)
AIScan score: 26/100 — Level 1 (Discoverable)
Rubric: v2026-06-08.1

## Failing checks (sorted by weight)
- **[C1] Markdown content negotiation** — FAIL
  - Evidence: Accept: text/markdown → 200 (text/html; charset=utf-8)
  - Fix: Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.
- **[C2] /llms.txt** — FAIL
  - Evidence: HTTP 404
  - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- **[B2] Explicit AI bot rules** — FAIL
  - Evidence: 0 known AI agent(s) addressed in robots.txt
  - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- **[P1] API Catalog (RFC 9727)** — FAIL
  - Evidence: 404 at /.well-known/api-catalog
  - Fix: Publish /.well-known/api-catalog linking to your OpenAPI descriptions.
- **[P4] OAuth discovery metadata** — FAIL
  - Evidence: auth-server: 404, protected-resource: 404
  - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
- **[D3] Link header for discovery** — FAIL
  - Evidence: no Link header or <link> tag
  - Fix: Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.

## General guidance
- Static-first: `robots.txt`, `llms.txt`, `/.well-known/*` JSON cards.
- Markdown negotiation: serve `text/markdown` when requested via `Accept` header or `?format=md`.
- Bot access: explicit allow/deny per AI user-agent (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, Bytespider, Amazonbot, CCBot, meta-externalagent, cohere-ai, Diffbot).
- Capabilities: publish an MCP server card and (optionally) an Agent Skills manifest even if the runtime isn't live — discovery first.
- Re-scan at aiscan.site after deploying.

Discoverability

Can agents find your pages? robots, sitemaps, llms.txt.

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · D3
What we found
no Link header or <link> tag
How to fix it
Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"
Option B — Claude Code skill (CLAUDE.md)
Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
Endpoint: https://aiscan.site/api/mcp
Tools: scan_website, get_fixes, get_grade
Call get_fixes with your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.
Re-scan at https://aiscan.site to verify after applying fixes.
Add a Link response header
Set this header on your homepage and/or root document. Most CDNs (Cloudflare, Vercel, Netlify) support response-header rules.
Example
Link: </.well-known/api-catalog>; rel="api-catalog"
Verify
After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.
Fix in ChatGPT Fix in Claude

Content

Can agents read your content cleanly? Markdown, structured data.

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · C1
What we found
Accept: text/markdown → 200 (text/html; charset=utf-8)
How to fix it
Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"
Option B — Claude Code skill (CLAUDE.md)
Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
Endpoint: https://aiscan.site/api/mcp
Tools: scan_website, get_fixes, get_grade
Call get_fixes with your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.
Re-scan at https://aiscan.site to verify after applying fixes.
Serve text/markdown on Accept negotiation
When a client sends Accept: text/markdown, return a markdown rendering of the same content. The simplest path is to publish parallel .md files (e.g. /about → /about.md) and rewrite based on the Accept header.
Test it
curl -H "Accept: text/markdown" https://yoursite.com/
Verify
After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.
Fix in ChatGPT Fix in Claude
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · C2
What we found
HTTP 404
How to fix it
Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"
Option B — Claude Code skill (CLAUDE.md)
Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
Endpoint: https://aiscan.site/api/mcp
Tools: scan_website, get_fixes, get_grade
Call get_fixes with your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.
Re-scan at https://aiscan.site to verify after applying fixes.
Create /llms.txt at the site root
Follows the llmstxt.org spec: a single H1, optional blockquote summary, then ## sections of markdown links.
Template
# Example Co > One-line summary of what this site / product does. A short paragraph explaining the audience, what's here, and how to navigate it. ## Docs - [Getting started](/docs/quickstart): install, first call in 5 min - [API reference](/docs/api): all endpoints, params, examples ## Pages - [Pricing](/pricing): plans and limits - [Changelog](/changelog): recent releases ## Optional - [Brand assets](/press): logos and screenshots
Verify
After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.
Fix in ChatGPT Fix in Claude

Bot Access

Are AI crawlers explicitly allowed or blocked?

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · B2
What we found
0 known AI agent(s) addressed in robots.txt
How to fix it
Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"
Option B — Claude Code skill (CLAUDE.md)
Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
Endpoint: https://aiscan.site/api/mcp
Tools: scan_website, get_fixes, get_grade
Call get_fixes with your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.
Re-scan at https://aiscan.site to verify after applying fixes.
Add explicit User-agent blocks
Don't rely on User-agent: * alone. Address each major AI crawler so your policy is unambiguous.
Recommended block
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
Verify
After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.
Fix in ChatGPT Fix in Claude

Capabilities

Can agents do things? APIs, auth, MCP, Agent Skills.

Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · P1
What we found
404 at /.well-known/api-catalog
How to fix it
Publish /.well-known/api-catalog linking to your OpenAPI descriptions.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"
Option B — Claude Code skill (CLAUDE.md)
Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
Endpoint: https://aiscan.site/api/mcp
Tools: scan_website, get_fixes, get_grade
Call get_fixes with your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.
Re-scan at https://aiscan.site to verify after applying fixes.
Publish an API catalog (RFC 9727)
# Add to your homepage HTTP response headers Link: </.well-known/api-catalog>; rel="api-catalog" # And serve a JSON document at /.well-known/api-catalog: { "links": [ { "href": "/openapi.json", "rel": "service-desc", "type": "application/openapi+json" } ] }
Verify
After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.
Fix in ChatGPT Fix in Claude
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · P4
What we found
auth-server: 404, protected-resource: 404
How to fix it
Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
⚡ Fix automatically with AIScan
Option A — Agent Skill (any agent runtime)
Install the AIScan skill in one command:
```
npx add-skill https://aiscan.site/aiscan-skill.json
```
Or download it directly: https://aiscan.site/aiscan-skill.json
Then ask your agent: "Fix the failing AI readiness checks for <your-url>"
Option B — Claude Code skill (CLAUDE.md)
Download CLAUDE.md from https://aiscan.site/CLAUDE.md and place it in your project root.
Ask Claude Code: "Fix the failing AIScan checks for <your-url>" — it reads the skill, calls our API, and applies the fix.
Option C — MCP (Claude Desktop, Cursor, or any MCP client)
Endpoint: https://aiscan.site/api/mcp
Tools: scan_website, get_fixes, get_grade
Call get_fixes with your URL for machine-readable fix instructions.
Option D — REST API
```
GET https://aiscan.site/api/public/scan?url=YOUR_URL
```
Returns the full report with all checks and fix details.
Re-scan at https://aiscan.site to verify after applying fixes.
Publish OAuth discovery metadata
If your API supports OAuth, serve RFC 8414 metadata at /.well-known/oauth-authorization-server and/or RFC 9728 at /.well-known/oauth-protected-resource.
Verify
After deploying, re-scan at https://aiscan.site. You can also test with curl -I or curl directly.
Fix in ChatGPT Fix in Claude

Showcase your grade

Embed your AIScan badge

Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of klyochat.com on AIScan.site.

HTML

<!-- AIScan.site agent-readiness badge -->
<a href="https://aiscan.site/?u=https%3A%2F%2Fklyochat.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade F (26/100) — AIScan.site">
  <img src="https://aiscan.site/api/public/badge.svg?score=26&grade=F&host=klyochat.com" alt="AIScan.site Grade F — 26/100" width="240" height="64" loading="lazy" />
</a>

Markdown

[![AIScan.site Grade F — 26/100](https://aiscan.site/api/public/badge.svg?score=26&grade=F&host=klyochat.com)](https://aiscan.site/?u=https%3A%2F%2Fklyochat.com%2F)

Create a free account to track this site over time

Save scan history
See score trends
Re-scan anytime

Free · No signup · ~20 seconds

Scan your own site

Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.

Re-test this site Scan your site

Or browse the community feed to see what others have scanned.

klyochat.com

Quick Wins

Markdown content negotiation

/llms.txt

Explicit AI bot rules

robots.txt present & sane

XML sitemap

Link header for discovery

⚡ Fix automatically with AIScan

Add a Link response header

Example

Verify

Markdown content negotiation

⚡ Fix automatically with AIScan

Serve text/markdown on Accept negotiation

Test it

Verify

/llms.txt

⚡ Fix automatically with AIScan

Create /llms.txt at the site root

Template

Verify

Structured HTML (title, meta, JSON-LD, single H1)

Content Signals in robots.txt

Explicit AI bot rules

⚡ Fix automatically with AIScan

Add explicit User-agent blocks

Recommended block

Verify

Web Bot Auth key directory

API Catalog (RFC 9727)

⚡ Fix automatically with AIScan

Publish an API catalog (RFC 9727)

Verify

MCP Server Card

Agent Skills index

OAuth discovery metadata

⚡ Fix automatically with AIScan

Publish OAuth discovery metadata

Verify

Share as a social image

Embed your AIScan badge

Create a free account to track this site over time

Scan your own site