01Fail
Markdown content negotiation
+8 pts if fixed
Serve text/markdown when the client sends Accept: text/markdown, or expose /path/index.md.
See full details
02Fail
OAuth discovery metadata
+4 pts if fixed
Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
See full details
03Fail
Link header for discovery
+3 pts if fixed
Add a Link header with rel="api-catalog" or rel="describedby".
See full details

Hand-off prompt for your coding agent5 issues

You are helping me raise my AIScan.site agent-readiness score.

Site: https://cardscan.site/
Platform: lovable (70% confidence)
AIScan score: 66/100 — Level 3 (Governed)
Rubric: v2026-06-08.1

Please implement the fixes below. Where a file already exists (e.g. `public/robots.txt`, `public/llms.txt`), edit it; otherwise create it. After each change, briefly explain what you did so I can verify in the next scan.

### Failing checks
- **[C1] Markdown content negotiation** — FAIL
  - Evidence: Accept: text/markdown → 200 (text/html)
  - Fix: Serve text/markdown when the client sends Accept: text/markdown, or expose /path/index.md.
- **[P2] MCP Server Card** — PARTIAL
  - Evidence: HTTP 200
  - Fix: Optional: publish /.well-known/mcp/server-card.json if you expose an MCP server.
- **[P4] OAuth discovery metadata** — FAIL
  - Evidence: auth-server: 200, protected-resource: 200
  - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
- **[D3] Link header for discovery** — FAIL
  - Evidence: no Link response header
  - Fix: Add a Link header with rel="api-catalog" or rel="describedby".
- **[B3] Web Bot Auth key directory** — PARTIAL
  - Evidence: HTTP 200
  - Fix: Optional: serve a JWKS-style key directory at /.well-known/http-message-signatures-directory.

### Constraints
- Do not change visible UI or copy.
- Keep changes additive and reversible.
- Prefer static files in `public/` over server routes when possible.
- For `llms.txt`, generate a real index of the site's most important pages.

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 response header
How to fix it
Add a Link header with rel="api-catalog" or rel="describedby".
1.⚡ Fix automatically with AIScan
The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - 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 C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like `robots.txt`, `llms.txt`, and `.well-known/*` belong in the `public/` folder — they're served from the site root automatically.
3.Add a Link response header
Set this header on your homepage and/or root document. Most CDNs (Cloudflare, Vercel, Netlify) support response-header rules.
4.Example
Link: </.well-known/api-catalog>; rel="api-catalog"
5.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)
How to fix it
Serve text/markdown when the client sends Accept: text/markdown, or expose /path/index.md.
1.⚡ Fix automatically with AIScan
The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - 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 C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like `robots.txt`, `llms.txt`, and `.well-known/*` belong in the `public/` folder — they're served from the site root automatically.
3.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.
4.Test it
curl -H "Accept: text/markdown" https://yoursite.com/
5.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?

Capabilities

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

211

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: 200, protected-resource: 200
How to fix it
Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
1.⚡ Fix automatically with AIScan
The fastest way to apply this fix is using AIScan's own agent tooling — it gives any AI coding assistant machine-readable instructions for this exact check. **Option A — Claude Code skill** 1. Download `CLAUDE.md` from https://aiscan.site/CLAUDE.md and drop it into your project root. 2. Ask Claude Code: *"Fix the failing AIScan check for <your-url>"* — it will read the skill, call our API, and apply the fix. **Option B — MCP (any MCP-compatible agent: Claude Desktop, Cursor, etc.)** - 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 C — REST API (any tool / script)** ``` GET https://aiscan.site/api/public/scan?url=YOUR_URL ``` Returns the full report including failing checks and fix details. Then re-scan at https://aiscan.site to verify.
2.This is a Lovable project
Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like `robots.txt`, `llms.txt`, and `.well-known/*` belong in the `public/` folder — they're served from the site root automatically.
3.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`.
4.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 cardscan.site on AIScan.site.

HTML

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

Markdown

[![AIScan.site Grade B — 66/100](https://aiscan.site/api/public/badge.svg?score=66&grade=B&host=cardscan.site)](https://aiscan.site/?u=https%3A%2F%2Fcardscan.site%2F)

Track this over time

Coming soon: save sites, schedule re-scans, get email when something material changes. Standards land weekly — your tracker shouldn't be one-shot.

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.

cardscan.site

Quick Wins

Markdown content negotiation

OAuth discovery metadata

Link header for discovery

Discoverability

robots.txt present & sane

XML sitemap

Link header for discovery

Content

Markdown content negotiation

/llms.txt

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

Bot Access

Content Signals in robots.txt

Explicit AI bot rules

Web Bot Auth key directory

Capabilities

API Catalog (RFC 9727)

MCP Server Card

Agent Skills index

OAuth discovery metadata

Embed your AIScan badge

Track this over time

Scan your own site

cardscan.site

Quick Wins

Markdown content negotiation

OAuth discovery metadata

Link header for discovery

robots.txt present & sane

XML sitemap

Link header for discovery

Markdown content negotiation

/llms.txt

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

Content Signals in robots.txt

Explicit AI bot rules

Web Bot Auth key directory

API Catalog (RFC 9727)

MCP Server Card

Agent Skills index

OAuth discovery metadata

Share as a social image

Embed your AIScan badge

Track this over time

Scan your own site