Is sp.asif.im AI agent ready? D · 40/100
Scan history · 2 public scans of sp.asif.im
6 failed · 2 partial out of 10 that apply to your site.
Fix automatically with AIScan
8 open checks (6 failing) can be handed to an AI agent: D2, D3, C1, C2, C3, E1, E3, E4. Pick one route — each returns the full, check-by-check instructions.
npx add-skill https://aiscan.site/aiscan-skill.jsonThen ask your agent: “Fix the failing AI readiness checks for https://sp.asif.im/”.
curl -o CLAUDE.md https://aiscan.site/CLAUDE.mdDrop it in your project root, then ask Claude Code to fix the failing AIScan checks.
https://aiscan.site/api/mcpTools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://sp.asif.im/" }.
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fsp.asif.im%2F'Returns every check with its complete fix guide.
Verify: Re-scan at https://aiscan.site after applying fixes, or run npx aiscan-cli https://sp.asif.im/. Individual checks that need a specific probe list it in their own guide.
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 publish /index.md.
- 02Fail+6 pts if fixed
/llms.txt
See full detailsPublish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
- 03Fail+4 pts if fixed
XML sitemap
See full detailsPublish /sitemap.xml and reference it in robots.txt.
# Agent-readiness remediation brief Site: https://sp.asif.im/ Platform: unknown (0% confidence) AIScan score: 40/100 — Level 2 (Readable) Rubric: v2026.08.2 ## Failing checks (sorted by weight) - **[C1] Markdown content negotiation** — FAIL - Evidence: Accept: text/markdown → 502 (text/plain; charset=UTF-8) - Fix: Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md. - **[C2] /llms.txt** — FAIL - Evidence: HTTP 502 - Fix: Publish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links. - **[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. - **[E1] Correct 404 handling** — PARTIAL - Evidence: GET /aiscan-404-probe-yr2nsl → HTTP 502, 16 bytes, text/plain - Fix: Return a real HTTP 404 (not 200) for missing pages, with a body that names the site and links to your homepage, sitemap, and search so an agent can recover. - **[E3] Heading hierarchy & server-rendered text** — FAIL - Evidence: 3 words of server-rendered text, 0 <h2>, 0 <h3> - Fix: Server-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship. - **[E4] HTTPS & canonical host** — PARTIAL - Evidence: final origin https://sp.asif.im · http:// upgrades to https · www.sp.asif.im serves its own copy (duplicate origin) · no HSTS header - Fix: Serve the site over HTTPS, 301-redirect http:// to https://, and redirect the www/apex variant to a single canonical host so agents don't index two copies of every URL. - **[D3] Link header for discovery** — FAIL - Evidence: no Link header or <link> tag - Fix: Add a Link response header or HTML <link rel="api-catalog"|"describedby"> tag. ## 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.
How this score is calculated
Every check earns points against a weight. We divide the points you earned by the points that actually apply to a site like yours — so checks that don't apply never drag you down.
Baseline every site should meet.
Strong signals most sites benefit from.
Emerging standards. Can only add points.
Not counted (7): B3, P1, P2, P3, P4, E2, E5 — either not applicable to this site profile or optional and not yet adopted. Expand any check to see the exact evidence we based it on.
Discoverability
52Can 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 · D2
What we foundno /sitemap.xml or /sitemap_index.xml resolved
Measured againstHow to fix itPublish /sitemap.xml and reference it in robots.txt.
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.Reference it in robots.txt
Sitemap: https://yoursite.com/sitemap.xml
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 header or <link> tag
Measured againstHow to fix itAdd a Link response header or HTML <link rel="api-catalog"|"describedby"> tag.
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"
Content
0Can 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 → 502 (text/plain; charset=UTF-8)
How to fix itServe text/markdown when the client sends Accept: text/markdown, or publish /index.md.
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/
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 foundHTTP 502
Measured againstHow to fix itPublish /llms.txt per llmstxt.org with an H1, summary, and ## sections of markdown links.
Generate it free
Use the AIScan llms.txt Generator to create a standards-shaped starting file from your site details, then publish it at
/llms.txt.Create /llms.txt at the site root
Follows the llmstxt.org spec: a single H1, optional blockquote summary, then
##sections of markdown links.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
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 foundh1: 0, title: false, meta description: false, JSON-LD: false
How to fix itEnsure a single <h1>, <title>, meta description, and schema.org JSON-LD.
Single H1
Each page should have exactly one
<h1>describing the page topic.Title + meta description
Set a unique
<title>(≤60 chars) and<meta name="description">(≤160 chars) per page.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>Your site is missing this right now, so AI agents can't use it. The fix below is what to change.
ID · E3
What we found3 words of server-rendered text, 0 <h2>, 0 <h3>
Measured againstHow to fix itServer-render your main copy and break it into a real heading outline (one h1, then descriptive h2/h3 sections). Agents that don't execute JavaScript only see the HTML you ship.
Server-render your main copy
Agents that don't execute JavaScript see only the HTML you ship. Aim for at least 150 words of real, server-rendered text on the homepage.
Use a real heading outline
One
<h1>for the page topic, then descriptive<h2>sections and<h3>sub-sections. Don't fake headings with styled<div>s.Verify what a crawler sees
curl -s https://yoursite.com/ | sed 's/<[^>]*>/ /g' | tr -s ' ' | head -c 800
Bot Access
100Are AI crawlers explicitly allowed or blocked?
Share as a social image
Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.
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.
Embed your AIScan badge
Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of sp.asif.im on AIScan.site.
<!-- AIScan.site agent-readiness badge --> <a href="https://aiscan.site/?u=https%3A%2F%2Fsp.asif.im%2F" target="_blank" rel="noopener" title="Agent-Readiness Grade D (40/100) — AIScan.site"> <img src="https://aiscan.site/api/public/badge.svg?score=40&grade=D&host=sp.asif.im" alt="AIScan.site Grade D — 40/100" width="240" height="64" loading="lazy" /> </a>
[](https://aiscan.site/?u=https%3A%2F%2Fsp.asif.im%2F)
Create a free account to track this site over time
- Save scan history
- See score trends
- Re-scan anytime
Dig deeper
sp.asif.im is built on Custom / Unknown. AI-agent readiness for custom and unrecognised stacks walks through the same checks on that platform.
This page always shows the most recent public scan for sp.asif.im.