rafifolio-jet.vercel.app — F/100 agent-readiness

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
robots.txt present & sane
+6 pts if fixed
Serve a non-blocking /robots.txt that references your Sitemap.
See full details
03Fail
/llms.txt
+6 pts if fixed
Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
See full details

Hand-off prompt for your coding agent7 issues

# Agent-readiness remediation brief

Site: https://rafifolio-jet.vercel.app/
Platform: unknown (0% confidence)
AIScan score: 0/100 — Level 0 (Invisible)
Rubric: v2026-06-08.1

## Failing checks (sorted by weight)
- **[C1] Markdown content negotiation** — FAIL
  - Evidence: no response
  - Fix: Serve text/markdown when the client sends Accept: text/markdown, or expose /path/index.md.
- **[D1] robots.txt present & sane** — FAIL
  - Evidence: HTTP 404
  - Fix: Serve a non-blocking /robots.txt that references your Sitemap.
- **[C2] /llms.txt** — FAIL
  - Evidence: no response
  - 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.
- **[D2] XML sitemap** — FAIL
  - Evidence: no /sitemap.xml or /sitemap_index.xml resolved
  - Fix: Publish /sitemap.xml and reference it in robots.txt.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — FAIL
  - Evidence: h1: 0, title: false, meta description: false, JSON-LD: false
  - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[D3] Link header for discovery** — FAIL
  - Evidence: no Link response header
  - Fix: Add a Link header with rel="api-catalog" or rel="describedby".

## 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 · D1
What we found
HTTP 404
How to fix it
Serve a non-blocking /robots.txt that references your Sitemap.
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.Create /robots.txt
Place this file at the site root so it's served at `https://yoursite.com/robots.txt`.
3.Recommended contents
User-agent: * Allow: / Sitemap: https://example.com/sitemap.xml # Content Signals (Cloudflare proposal) Content-Signal: search=yes, ai-train=no, ai-input=yes # Explicit AI agent rules User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
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
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · D2
What we found
no /sitemap.xml or /sitemap_index.xml resolved
How to fix it
Publish /sitemap.xml and reference it in robots.txt.
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.Generate a sitemap
Most frameworks have a built-in sitemap generator (Next.js: `app/sitemap.ts`, TanStack: a route at `/sitemap.xml`). Publish all public URLs.
3.Reference it in robots.txt
Sitemap: https://yoursite.com/sitemap.xml
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
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.Add a Link response header
Set this header on your homepage and/or root document. Most CDNs (Cloudflare, Vercel, Netlify) support response-header rules.
3.Example
Link: </.well-known/api-catalog>; rel="api-catalog"
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

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
no response
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.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.
3.Test it
curl -H "Accept: text/markdown" https://yoursite.com/
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
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
no response
How to fix it
Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
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.Create /llms.txt at the site root
Follows the llmstxt.org spec: a single H1, optional blockquote summary, then `##` sections of markdown links.
3.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
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
Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · C3
What we found
h1: 0, title: false, meta description: false, JSON-LD: false
How to fix it
Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
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.Single H1
Each page should have exactly one `<h1>` describing the page topic.
3.Title + meta description
Set a unique `<title>` (≤60 chars) and `<meta name="description">` (≤160 chars) per page.
4.Add JSON-LD
Embed schema.org structured data so agents can extract entities reliably.
<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Organization", "name": "Example Co", "url": "https://example.com", "logo": "https://example.com/logo.png" } </script>
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?

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.
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.Add explicit User-agent blocks
Don't rely on `User-agent: *` alone. Address each major AI crawler so your policy is unambiguous.
3.Recommended block
User-agent: GPTBot Allow: / User-agent: ClaudeBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot-Extended Allow: /
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 rafifolio-jet.vercel.app on AIScan.site.

HTML

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

Markdown

[![AIScan.site Grade F — 0/100](https://aiscan.site/api/public/badge.svg?score=0&grade=F&host=rafifolio-jet.vercel.app)](https://aiscan.site/?u=https%3A%2F%2Frafifolio-jet.vercel.app%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.

Custom / Unknown

Quick Wins

Markdown content negotiation

robots.txt present & sane

/llms.txt

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

Embed your AIScan badge

Track this over time

Scan your own site

Custom / Unknown

Quick Wins

Markdown content negotiation

robots.txt present & sane

/llms.txt

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

Share as a social image

Embed your AIScan badge

Track this over time

Scan your own site