Why we think this is Replit (3 signals)
- · asset reference: replit.com / repl.co / replit.dev
- · bare 'replit' mention in HTML
- · Replit dev banner / deploy badge
3 failed · 1 partial out of 9 that apply to your site.
Quick Wins
Top 3 fixes ranked by score impact
- 01Fail+8 pts if fixed
Markdown content negotiation
See full detailsServe text/markdown when the client sends Accept: text/markdown, or expose /path/index.md.
- 02Fail+4 pts if fixed
OAuth discovery metadata
See full detailsPublish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
- 03Fail+3 pts if fixed
Link header for discovery
See full detailsAdd a Link header with rel="api-catalog" or rel="describedby".
# Task: raise AIScan agent-readiness score Site: https://a8n.pro/ Platform: replit (99% confidence) AIScan score: 62/100 — Level 3 (Governed) Rubric: v2026-06-08.1 Implement the fixes below in this repository. Make atomic commits per check id. After all edits, run the build to confirm nothing breaks. ## Failing checks - **[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 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. - **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL - Evidence: h1: 0, title: true, meta description: true, JSON-LD: true - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD. - **[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. ## Notes - Treat `public/` (or framework equivalent) as the source for `robots.txt`, `llms.txt`, and `.well-known/` files. - For Markdown content negotiation, respond to `Accept: text/markdown` and `?format=md` on canonical content URLs. - For MCP / Agent Skills, drop card files under `.well-known/` even if the server isn't live yet — discovery matters first.
Discoverability
77Can 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 foundno Link response header
How to fix itAdd a Link header with rel="api-catalog" or rel="describedby".
⚡ 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.mdfrom 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_fixeswith 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.
This is a Replit project
Static files (
robots.txt,llms.txt,.well-known/*) go in thepublic/folder. Edit them in the Replit IDE, or ask Replit AI / Agent to apply the fixes for you.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 -Iorcurldirectly.- Download
Content
50Can 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 foundAccept: text/markdown → 200 (text/html; charset=UTF-8)
How to fix itServe text/markdown when the client sends Accept: text/markdown, or expose /path/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.mdfrom 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_fixeswith 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.
This is a Replit project
Static files (
robots.txt,llms.txt,.well-known/*) go in thepublic/folder. Edit them in the Replit IDE, or ask Replit AI / Agent to apply the fixes for you.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.mdfiles (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 -Iorcurldirectly.- Download
Bot Access
75Are AI crawlers explicitly allowed or blocked?
Capabilities
56Can 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 · P4
What we foundauth-server: 200, protected-resource: 200
How to fix itPublish 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.mdfrom 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_fixeswith 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.
This is a Replit project
Static files (
robots.txt,llms.txt,.well-known/*) go in thepublic/folder. Edit them in the Replit IDE, or ask Replit AI / Agent to apply the fixes for you.Publish OAuth discovery metadata
If your API supports OAuth, serve RFC 8414 metadata at
/.well-known/oauth-authorization-serverand/or RFC 9728 at/.well-known/oauth-protected-resource.Verify
After deploying, re-scan at https://aiscan.site. You can also test with
curl -Iorcurldirectly.- Download
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of a8n.pro on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fa8n.pro%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade C (62/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=62&grade=C&host=a8n.pro" alt="AIScan.site Grade C — 62/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fa8n.pro%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Automate your AI-readiness
Plug AIScan into your agent stack or chat with it on the go.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.