1 failed out of 7 that apply to your site.
Quick Wins
Top 1 fixes ranked by score impact
- 01Fail+3 pts if fixed
Link header for discovery
See full detailsAdd a Link header with rel="api-catalog" or rel="describedby".
# Agent-readiness remediation brief Site: https://airankapp.com/ Platform: unknown (0% confidence) AIScan score: 93/100 — Level 5 (Agent-Native) Rubric: v2026-06-08.1 ## Failing checks (sorted by weight) - **[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
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".
1.⚡ Fix automatically with AIScanThe 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 headerSet this header on your homepage and/or root document. Most CDNs (Cloudflare, Vercel, Netlify) support response-header rules.
3.ExampleLink: </.well-known/api-catalog>; rel="api-catalog"
4.VerifyAfter deploying, re-scan at https://aiscan.site. You can also test with `curl -I` or `curl` directly.
Content
100Can agents read your content cleanly? Markdown, structured data.
Bot Access
100Are AI crawlers explicitly allowed or blocked?
Capabilities
100Can agents do things? APIs, auth, MCP, Agent Skills.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of airankapp.com on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fairankapp.com%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade A+ (93/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=93&grade=A%2B&host=airankapp.com" alt="AIScan.site Grade A+ — 93/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fairankapp.com%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.
Scan your own site
Get a plain-English agent-readiness report you can hand straight to ChatGPT or Claude.
Scan your site