AIScan.site
R
Detected framework · 99% confidence

Replit

https://a8n.pro/
C62 / 100
Grade C · Level 3GovernedFair — agents can find you, but a lot is left on the table.
Discoverability77
2/3 passing
Content50
1/3 passing
Bot Access75
1/3 passing
Capabilities56
2/4 passing
Score breakdown by dimension
Discoverability77
Content50
Bot Access75
Capabilities56
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
4 checks need fixing

3 failed · 1 partial out of 9 that apply to your site.

See top fixes

Quick Wins

Top 3 fixes ranked by score impact

  • 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 agent6 issues
# 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

77

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

21

  • 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.Add a Link response header

    Set this header on your homepage and/or root document. Most CDNs (Cloudflare, Vercel, Netlify) support response-header rules.

    2.Example
    Link: </.well-known/api-catalog>; rel="api-catalog"
    3.Verify

    After deploying, re-run this scan. You can also test with `curl -I` or `curl` directly.

    Fix in ChatGPT Fix in Claude

Content

50

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

111

  • 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 expose /path/index.md.

    1.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.

    2.Test it
    curl -H "Accept: text/markdown" https://yoursite.com/
    3.Verify

    After deploying, re-run this scan. You can also test with `curl -I` or `curl` directly.

    Fix in ChatGPT Fix in Claude

Bot Access

75

Are AI crawlers explicitly allowed or blocked?

11

Capabilities

56

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.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`.

    2.Verify

    After deploying, re-run this scan. You can also test with `curl -I` or `curl` directly.

    Fix in ChatGPT Fix in Claude
Share the result

Share as a social image

Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.

AIScan share card — a8n.pro graded C
Post on X Share on LinkedIn Share on Facebook

Tip: for X and LinkedIn, upload the downloaded PNG with your post so the card shows in the feed. Posts that include just the link will still preview AIScan.site.

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 a8n.pro on AIScan.site.

AIScan.site grade C
HTML
<!-- 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>
Markdown
[![AIScan.site Grade C — 62/100](https://aiscan.site/api/public/badge.svg?score=62&grade=C&host=a8n.pro)](https://aiscan.site/?u=https%3A%2F%2Fa8n.pro%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.

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